Measure browser storage read and write speed with a temporary 32 MB file that is deleted when the test finishes.
This measures the browser's private storage path. Operating-system caches can make short read results faster than sustained physical-disk performance.
The test creates 32 MiB of generated data and writes it in 4 MiB chunks to origin-private file storage. It then reads the temporary file back and requests deletion. Measured time is converted into apparent write and read throughput without opening, scanning or modifying personal folders.
A short browser-storage test is heavily influenced by memory caching, file-system buffering, quota implementation and browser overhead. It is useful for comparing the same storage path under similar conditions, but it is not the sustained raw speed a drive vendor advertises.
This covers the browser API and operating-system acceptance of the 32 MiB temporary file; buffered completion may precede a physical-media flush.
A recently written file can be served partly or entirely from cache, so an unusually high number is possible.
Caching, background I/O, storage pressure and power management can dominate such a short run. Compare several runs.
The origin-private file API is not available in every browser or browsing mode; this does not mean the physical disk is broken.
The test cannot identify the drive, access SMART health data, detect bad sectors, verify free-space integrity or reproduce a sustained native benchmark. Incognito and managed-browser policies may block or alter storage.
Read our complete testing methodology →It measures the browser's private storage path, which normally uses local storage but is also affected by browser caching, encryption and operating-system behavior.
No. A 32 MB temporary file is created inside private browser storage and removed in a cleanup step after reading.
The operating system or browser may serve part of the file from memory cache, so short browser tests can exceed sustained physical-drive speeds.
No. It creates its own temporary data in storage private to this website, reads that data and requests its deletion.
The workload is small and includes browser APIs, caching and file-system behavior. Manufacturer figures normally come from larger native benchmarks under controlled conditions.
No. Health checks need operating-system access to hardware information such as SMART data, which a normal web page cannot read.