Azure Large File Upload Speed Test
Upload a local test file directly from your browser to Azure Blob Storage and measure real-world throughput to one Azure region.
Configure Upload Test
Choose the Right Transfer Test
Multi-Region Upload Test
Generate non-sensitive test data and compare upload performance across several regions.
Azure Download Test
Measure download throughput from Azure Storage to your current network.
AzCopy Bench
Use Microsoft's CLI benchmark for servers, automation, and production-scale testing.
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, average Mbps, MiB/s, 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 and recommends 100 MiB or larger.
How should I choose block size and concurrency?
Start with Auto. It selects a 4-32 MiB block size and 4 or 8 upload workers based on the selected file. Larger blocks and higher concurrency can improve throughput, but also use more local memory and bandwidth.
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. Run several tests at different times and compare only runs with matching files and settings.