Azure file upload test
Compare file uploads
Choose a non-sensitive test file and a target region. The upload starts only after you select Start upload test.
Auto uses four workers and adjusts block size to your connection. Sustained speed uses a complete interval of at least five seconds after warm-up. The file keeps uploading after this measurement; average speed and elapsed time cover the complete upload.
Choose an Azure region and a non-sensitive test file to measure upload speed.
Configure upload test
Explore more Azure performance tools
Frequently asked questions
When should I use this test?
Use this browser test to measure a real local file transfer to one Azure region. It can help investigate migration throughput, Azure Data Factory copy performance, and Self-hosted Integration Runtime network capacity.
For quick multi-region comparisons without selecting a local file, use the multi-region upload test. For repeatable server or CI/CD benchmarks, use AzCopy Bench.
How does the large file upload test work?
The page requests a short-lived upload URL, then your browser sends the selected file directly to Azure Blob Storage in the chosen region. It reports transferred bytes, elapsed time, sustained speed, whole-upload average speed, and estimated remaining time.
The result measures the current browser, device, local network, internet path, and Azure endpoint together. It is not a storage account performance guarantee.
What files are safe to upload?
Use generated or disposable test data only. Do not upload credentials, personal data, customer content, source code, production backups, regulated data, or any other confidential file.
The browser accepts files from 1 MiB through 5 GiB. Start with the generated 1 MiB file; choose a larger non-sensitive file when you need a longer measurement.
How should I choose block size and concurrency?
Start with Auto. It uses four workers and adjusts block size to your connection, using the same strategy as the upload speed test. You can select a fixed block size or a different concurrency to compare settings.
Compare settings only when the file, region, device, and network conditions are otherwise unchanged.
Why do results vary between runs?
Internet routing, Wi-Fi quality, VPNs, local CPU and memory pressure, regional congestion, and competing traffic can all change throughput. Repeat only when you need a fresh measurement, and compare runs with matching files and settings.