Large-file write speed on a gaming PC: what it shows

A game takes a long time to install, a large capture file saves slowly, or you are comparing storage in a gaming desktop. The large-file write speed can help show how quickly storage handles sustained writes, but it does not explain every slow install or predict game performance on its own.

Use the Storage Test to check large-file and small-write performance in your browser. Then compare the result with what you are doing on the PC and check whether another part of the process is the bottleneck.

Test large-file write speed

1. Open the Storage Test on the gaming PC whose storage you want to check.
2. Pause game downloads, file copies, recording, and other work that is actively using storage. Close applications you do not need for the test.
3. Run the test and note the large-file write speed, along with the read speed and small-write result. The test also reports an overall score.
4. Run it two or three times under the same conditions. Record the results and whether the drive was idle, busy, or warm from recent use.
5. If you are investigating a problem, compare the results with a second run after restarting the PC and letting it sit idle. Do not compare results from different browsers or conditions as if they were identical.

A browser test measures storage that the browser can access. It is not the same as selecting a drive letter and testing that physical drive directly, so do not assume it isolates a particular game drive. The browser and operating system can also affect the result. For more on this limitation, see why browser storage tests use temporary data.

What the result means

Large-file writes are fast and repeatable

The browser-accessible storage path can write large blocks of test data quickly in those conditions. That is a useful sign for tasks such as copying large files or saving long recordings. It does not guarantee that a game will install equally quickly, because an installation may also depend on download speed, decompression, small file operations, and the speed of the source drive.

Large-file writes are slow, but small writes are normal

The storage path may handle small updates well while struggling with a sustained stream of data. Large-file writes matter more to tasks such as moving a big archive or saving a long capture than to every game load. Repeat the test when the PC is idle before blaming the drive.

Both large-file and small-write results are low

This points to a broader slowdown in the tested storage path, but it does not identify the cause. Background transfers, limited free space, a connection or controller issue, or the browser environment can all affect a result. Check the conditions first, then compare with another way of writing a large file if the problem persists.

Results change a lot between runs

Storage may be busy, the browser may be contending with other work, or the test conditions may have changed. A single high or low result is not a reliable baseline. Repeat the test after the PC is idle and look for a consistent pattern rather than focusing on one score.

The result is good, but game installs are still slow

Storage is not the only step in an install. A launcher must download data, verify it, and sometimes unpack or patch many files. If the download rate is low, check the network. If the download is fast but installation pauses while the processor is busy, unpacking or verification may be the limit. A fast large-file write result does not rule out either problem.

How to investigate a slow result

1. Stop other storage work. Pause downloads, cloud sync, backups, game updates, and file transfers, then run the test again. Several programs writing at once can reduce the available throughput.
2. Restart and retest. A restart clears many temporary workloads. After signing in, wait for updates and startup tasks to settle before running the test.
3. Check available space. Low free space can make some drives and applications behave poorly, though it does not prove that free space is the cause. On Windows 11, open Settings › System › Storage. On macOS, open System Settings › General › Storage.
4. Check which drive the game uses. Look at the game's install location in its launcher or the folder properties in your file manager. The browser test may not be measuring that same drive, so treat it as a general check, not a direct game-drive result.
5. Compare with an ordinary large-file task. If you have another drive, copy a large file between the two and note the sustained speed. Copying within one drive can give a misleading result because the drive must read and write at the same time.
6. Check for a repeated slowdown after use. If speeds fall after a large transfer and recover after the drive cools or sits idle, heat or a drive's temporary write cache may be involved. A short browser test cannot confirm either cause by itself.

What large-file write speed does not tell you

Large-file write speed measures throughput: how much data storage can write over time. It is not the same as response time for opening a small file, and it does not measure every part of game loading. Game performance also depends on reads, small and scattered file access, the processor, memory, and the game engine.

It also cannot confirm the drive's advertised capacity, identify a failing component, or prove that a particular SSD is healthy. Browser-based storage tests use temporary data and run within browser limits. Treat the result as one clue, then use repeatable tests and real-world tasks on the drive you are troubleshooting.