Shading throughput for a large file conversion: tips

A large file conversion can take longer than expected, slow down partway through, or make your computer’s fans spin up. A graphics score may offer a clue, but it cannot tell you on its own how quickly a specific app will convert a file.

Use the Graphics Test to check shader performance, then compare that result with the conversion itself. The key is to find out whether graphics processing is likely to matter, or whether the processor, storage, or conversion settings are the bigger limit.

Check shading throughput before converting

1. Open the Graphics Test and run it while the computer is idle. Close games, video editors, and other demanding programs first.
2. Note the shading result and fill rate. The test runs a 1080p graphics workload and gives each result a score out of 100.
3. Run your conversion once with the same source file and settings you normally use. Note the file size, output format, time taken, and whether the app reports hardware acceleration.
4. If you change a setting, repeat the conversion with the same file and output options. Change one thing at a time so you can tell what helped.

Do not run the graphics test during the conversion. Both workloads compete for computer resources, so running them together can make the conversion slower and make the test score harder to compare.

What the result means

A low or inconsistent shading score

The browser’s graphics workload is slower than expected for this device or varies between runs. That can be a reason to check graphics acceleration, background activity, or heat. It does not prove that the conversion app is using the GPU, or that the GPU is the cause of the delay.

A steady shading score, but the conversion is slow

The graphics test is repeatable, but the conversion is taking a long time. The app may be using the processor rather than the GPU, or the selected file format may not support acceleration in that app. The time can also be limited by reading the source or writing the output.

The conversion slows down after several minutes

A steady slowdown can point to heat, a power-saving mode, or changing work in the app. It may also happen when the conversion has reached a different stage, such as writing a large output file. Compare the same section of the task before drawing a conclusion.

The output is fast, but the file is much larger

Throughput is not the only goal. A less compressed format or higher-quality setting can create a larger output that takes longer to save. Compare output size and quality as well as elapsed time.

How to improve a slow conversion

1. Check whether the app uses the GPU. Look in the conversion app’s preferences for a hardware acceleration or GPU option, if it offers one. The exact controls vary by app and file type. A browser graphics score cannot confirm that this option is active.
2. Plug in the computer and check its power mode. On Windows 11, open Settings › System › Power & battery and check Power mode. On macOS, open System Settings › Battery and check Low Power Mode. Power-saving settings can reduce performance, especially on a laptop running on battery.
3. Close other heavy tasks. Quit games, video playback, large downloads, and other editing or conversion jobs. Then test the conversion again. Avoid comparing a busy run with an idle run.
4. Check the graphics preference for the app. On Windows 11, open Settings › System › Display › Graphics, select the app, and check its options if more than one GPU is available. macOS usually manages graphics selection automatically, so check the conversion app’s own preferences instead.
5. Check processor and storage performance separately. If the app appears CPU-limited, use the Processor Test when the computer is idle. If reading or saving seems slow, try the Storage Test. These tests show performance in their own workloads, not a guaranteed conversion time.
6. Try a smaller test file. Convert a short section or a copy of a smaller file using the same settings. If the smaller job is also slow, the format, app settings, or available hardware acceleration may be the issue. If only the large job slows down, check available storage space and whether the device gets hot.

When the graphics result points to a bigger problem

If the Graphics Test score is low every time, close other graphics-heavy programs and restart the computer before testing again. On a laptop, use a hard, level surface so the vents are not blocked. Let the device cool between demanding tasks rather than running the test repeatedly while it is already hot.

On Windows 11, check for graphics driver updates from the computer or graphics hardware manufacturer. On a Mac, install available macOS updates through System Settings › General › Software Update. If the computer’s graphics performance is poor across several apps, or it has new crashes or visual glitches, contact the device maker or a repair shop instead of assuming a conversion setting will fix it.

Why the graphics score is only one clue

Shading throughput describes how quickly the graphics hardware handles a particular kind of visual calculation. A file conversion may not use that kind of work at all. Video encoding can use GPU acceleration when the app, format, and hardware support it, but some conversions rely mostly on the processor. Image conversions may be limited by decoding, resizing, or saving the output instead.

For a useful comparison, keep the same browser, test conditions, source file, and conversion settings. A Graphics Test score is not a direct conversion benchmark, and it cannot show the exact reason a file is taking longer. Treat it as one clue alongside the app’s own acceleration settings, the conversion time, and the amount of time spent reading or writing files.