Output
Temporary-file write and read throughput
Write and read a temporary test file in a folder you explicitly select. Requires the File System Access API.
Drive Speed Test · At a glance
Quick answer: Write and read a temporary test file in a folder you explicitly select. Requires the File System Access API. The test uses a bounded temporary file, so caches and connection mode can dominate.
The test loads when you open it. Device access is requested only after you choose to start.
Detailed guide
Temporary-file write and read throughput
Explicitly selected folder; 16 MiB test file
HTTPS; File System Access API
Runs on your device; no tool-result upload
A uniquely named temporary file is written, read and removed. Operating-system caching and USB connection mode can strongly affect measured speed.
The test uses a bounded temporary file, so caches and connection mode can dominate. It does not scan the entire device for faults.
Use a supported Chromium browser with directory access and enough free space. Check that you selected the external drive rather than a local folder.
Only supported Chromium-based browsers expose the required directory picker. Pick a folder with free space; do not disconnect the drive during a test.
It uses a uniquely named temporary test file and removes that file afterward. It does not intentionally overwrite existing files in the selected folder.
Choose a folder on the drive you want to test, then explicitly start the read/write test. The browser asks for folder access.
No. Open the interactive tool above in a modern browser. The instructions and explanations are available even with JavaScript disabled; running a test needs JavaScript.
Power settings, background tasks, browser scheduling, operating-system input processing and device settings affect measurements. Compare repeated attempts with identical settings rather than the single highest score.