Shading throughput for a video editing session

Your editing timeline stutters, effects take a while to preview, or playback slows when you add layers. A graphics test can help you check how quickly your computer handles a specific kind of GPU workload, but it cannot tell you by itself whether your editor will run smoothly.

Use the Graphics Test to measure shading throughput and fill rate at 1080p. Then compare runs under consistent conditions and check the other parts of your workflow that can also slow editing.

Test shading throughput

Open the Graphics Test on the computer you use for editing. Run it in a current desktop browser.
Connect a laptop to its charger, close unrelated apps, and let the computer sit idle for a minute. This gives you a useful baseline without a video call or background export competing for resources.
Run the test and note the shading result, fill-rate result, and score out of 100. The test draws a graphics workload in your browser at 1080p.
Run it again under the same conditions. If you want to see how other work affects browser graphics, repeat with your editor open but not exporting, then compare the results with your idle baseline.
Keep the browser window visible while the test runs. Avoid changing display resolution, power mode, or browser settings between comparison runs.

Record the computer, browser, power state, and whether the editor was open. The score is most useful for comparing the same computer with itself. It is not a universal grade for video editing, and results from different devices or browsers are not always directly comparable.

What the result means

Shading throughput is lower than expected

Shading throughput describes how quickly the graphics processor handles calculations used to draw pixels and visual effects. A low or inconsistent result can point to power-saving mode, competing work, browser graphics settings, or a graphics driver issue. It does not prove that the GPU is damaged.

Fill rate is low, but shading looks normal

Fill rate measures how quickly the test can draw pixels across the screen. A high-resolution display, multiple monitors, or heavy display effects can add work, but this result alone does not show that your editing timeline is limited by the screen. The test uses a 1080p workload and does not reproduce every editor effect.

The score changes a lot between runs

Background activity, heat, browser load, or a change in power mode may be affecting the result. Repeat the test after closing other work and letting the computer cool. If the score is steady at idle but falls with the editor open, the two programs may be competing for graphics resources.

The score is steady, but editing still stutters

The problem may be outside the graphics workload this test measures. Video decoding, effects, memory, CPU performance, storage speed, and the footage's resolution or codec can all affect playback. A browser graphics test does not measure export quality, hardware video encoding, or every capability of your editor's GPU.

How to improve editing performance

Connect the charger and select a performance power mode. A laptop may reduce graphics speed on battery. If you are comparing results, keep the power state the same each time.
Close apps that compete for resources. Pause large downloads, cloud backups, games, and other video work before testing or editing. Check again with your usual apps open if the slowdown only happens during multitasking.
Check the editor's graphics settings. Look in the editor's performance or playback preferences for GPU acceleration. The setting name and location depend on the app. If you change it, restart the editor and test the same clip again.
Choose the high-performance GPU on Windows when available. Open Settings › System › Display › Graphics, select the editing app, choose Options, and select High performance if that option appears. The setting may not be available on every computer.
Check power settings on a Mac laptop. Open System Settings › Battery and check whether Low Power Mode is enabled. Options vary by Mac model. Macs generally manage graphics selection automatically, so check the editor's own performance preferences too.
Reduce the preview workload. Lower the editor's playback resolution or use proxy files, which are smaller copies used for smoother editing. This changes preview work, not the quality of the original footage or final export.
Update or reinstall the graphics driver if the issue started recently. On Windows, check for updates from your computer or GPU maker, then restart. On a Mac, install available macOS updates through System Settings › General › Software Update.
Check the other likely bottlenecks. If only one project stutters, try a short, less demanding clip and temporarily disable heavy effects. If every project slows during export or saving, check CPU and storage behavior as well as graphics performance.

When to suspect a hardware problem

A low browser score alone is not enough to justify replacing a graphics card. Suspect a hardware fault if graphics errors appear in several apps, the computer crashes during ordinary work, or the same problem continues after a restart and driver or system updates. If the problem began after a repair or upgrade, ask the service provider to check the GPU and its connections. For a computer under warranty, document the test conditions and symptoms before contacting support.

Why the test is only one part of the diagnosis

Video editing uses several kinds of work. The GPU can draw previews and accelerate supported effects, while the CPU, memory, storage, and video codec affect other parts of playback and export. A codec is the method used to compress and decompress video. Some formats are easier for a particular computer to decode than others.

The Graphics Test measures browser-based shading and fill rate, not your editor's full performance. Use it as one repeatable clue alongside what you see in a real project. The test runs on your device, and its graphics workload is not a measurement of how quickly your editor can export a finished video.