Large files take too long to save? What to check

You click Save, but the progress bar barely moves. This can happen with a full or slow drive, a weak USB connection, an app doing extra work, or a file still uploading to cloud storage.

Start by separating the save itself from any later upload or processing. The Storage Test can also help compare storage performance for large files and small writes, giving you a clue about whether the drive may be part of the problem.

Check where the delay happens

1. Note the file size, the app you are saving from, and the destination. Check whether you are saving to the computer, an external drive, a network folder, or a cloud-synced folder.
2. Open the Storage Test and run it in the browser. It measures storage performance for large files and small writes, and gives a score out of 100. Close other heavy apps first so they are less likely to affect the result.
3. Try saving a copy of a large, non-sensitive file to a different destination, such as the computer's internal drive instead of a USB drive. Do not overwrite the original. Compare the time and watch whether the app's save indicator finishes before any sync indicator does.
4. If you use an external drive, reconnect it directly to another computer port, without a hub or dock, and try the same copy again. Keep the file and destination the same so the comparison is useful.

Use a file that is large enough to make the delay noticeable, but leave plenty of free space on the destination. The point is to compare the same task under different conditions, not to fill a drive with test data.

What the result means

The Storage Test score is low and saves are slow on the internal drive

The computer's storage or the current browser environment may be limiting performance. A browser benchmark is not the same as saving through your editing app, but a low result is a reason to check free space, background activity, and drive condition. You can compare read and write behavior in How to interpret storage test read and write speeds.

The benchmark looks fine, but one app saves slowly

The drive may not be the main bottleneck. The app could be rendering, compressing, encrypting, or checking the file before it finishes saving. Try saving a simpler file from the same app, then save the original to a different local folder. If only one project or file type takes a long time, look at that app's export or save settings.

The internal drive is quick, but an external drive is slow

The external drive, cable, port, hub, or file system may be limiting speed. A drive that starts fast and then slows during a long write can also be running out of its fast write cache. Compare the drive on a direct port and with another cable, if you have one. Do not format it as a troubleshooting step, because formatting erases data.

The app says the save is done, but the cloud icon is still busy

The local copy may already be safe, while a sync service is still uploading it. Large files can take much longer to upload than to save locally, especially on a slow or busy connection. Check the sync service's status and verify the file is available on another device before assuming the save failed.

The save is slow only on a network folder

The delay may come from the network, the shared computer, or the storage device at the other end. Try a local save first. If the local copy is quick, troubleshoot the network connection or shared storage instead of replacing your computer's drive.

How to fix slow saves

1. Check the destination and sync status. Save a copy to a local folder and wait for the app to finish. If that is quick but a cloud or network copy is not, check the sync service or connection. Do not interrupt a transfer until you know which copy is complete.
2. Free space on the destination. A drive with very little free space can struggle to create temporary files while an app saves. On Windows 11, open Settings › System › Storage. On a Mac, open System Settings › General › Storage. Move or remove files only after checking that you have another copy of anything important.
3. Reconnect an external drive directly. Try a different USB port and, if available, a known-good cable. Avoid testing through a hub or dock at first. If the drive is still slow on another computer, the drive or its enclosure may be the cause.
4. Let background work finish. Cloud sync, backups, antivirus scans, and other large transfers can compete for disk access. Pause or wait for nonessential transfers, then try saving again. Avoid turning off security software just to speed up a save.
5. Check power settings on a laptop. Power-saving modes can reduce performance in some situations. On Windows 11, check Settings › System › Power & battery. On a Mac, check System Settings › Battery. Compare while plugged in, using the same file and destination.
6. Restart the app and computer. A stuck save operation or background process can keep storage busy. Save other open work first, restart, and repeat the comparison before changing more settings.

When the drive may be failing

Back up important files before running more tests if the drive disconnects, makes unusual clicking noises, reports errors, or becomes slower over time. A benchmark cannot confirm that a drive is healthy or predict when it will fail. If the same drive remains unusually slow on another computer, or files become unreadable, stop relying on it and contact the manufacturer or a repair professional. For USB flash drives, read about signs that a USB drive needs replacement.

Why the benchmark and save time can differ

The Storage Test runs in your browser and uses temporary data. It is useful for comparing storage behavior, but it does not reproduce every step in an editing app's save process or measure a cloud upload. Browser storage results can also vary between runs. For a fair comparison, use the same computer, browser, power state, and background workload each time. More on that limitation: why browser storage tests use temporary data.