The Binance APP installer itself is only 85MB (Android) or 200MB (iOS). In theory, on a 100 Mbps broadband connection, it should download in 10 seconds. If your download speed is stuck at 50KB/s or even a few KB/s, it's most likely not the file itself, but one of four reasons: ISP throttling, CDN node mis-selection, time-slot congestion, or local DNS poisoning. The fastest self-help methods are: cross-test by switching between Wi-Fi/4G, change your local DNS to 1.1.1.1, try a different time slot, or directly download the Binance Official App via the binance.info / binance.bz backup domain from the Binance Official Site. iPhone users with slow App Store downloads should switch to a US region Apple ID as per the iOS Install Guide and try again. Below, we lay out common causes and their targeted methods.
Common Slow-Speed Cause Reference Table
| Symptom | Possible Cause | Speed-Up Method |
|---|---|---|
| Extremely slow on Wi-Fi, normal on 4G | Home broadband DNS poisoning | Switch DNS or use mobile hotspot |
| Extremely slow on 4G, normal on Wi-Fi | ISP throttling or poor node | Change time slot, change Wi-Fi |
| Fast at first, drops sharply after a few seconds | ISP QoS throttling | Disconnect/reconnect, change download tool |
| Stuck around 50KB/s | CDN node routed overseas | Switch backup domain and retry |
| App Store spinning without downloading | Apple CDN unreachable | Switch Apple ID region or DNS |
| Slowdown around 10 PM | Local network peak | Download at dawn or noon |
Find the symptom closest to yours in the reference table, then follow the specific operations in the sections below.
Network-Layer Troubleshooting
Step 1: Test Real Bandwidth
Open speedtest.net or fast.com to test the actual upstream/downstream of your current broadband. If the actual downstream is only 2-5Mbps, the link itself is slow and unrelated to Binance. If bandwidth meets spec but downloads are slow, continue troubleshooting.
Step 2: Switch DNS
Windows network icon in the bottom right → "Network & Internet Settings" → "Change adapter options" → double-click current adapter → "IPv4 Properties" → "Use the following DNS" → fill in 1.1.1.1 and 8.8.8.8. After the change, run ipconfig /flushdns in the command line.
macOS: "System Settings → Network → Details → DNS", add 1.1.1.1 / 8.8.8.8.
Step 3: Use nslookup to See Where It Resolves To
Run nslookup dl.binance.io in the command line. Normally it should resolve to AWS CloudFront IPs (most in the 13.x or 54.x range). If the result is an unfamiliar domestic IP, DNS is being poisoned to a low-quality node, which is a common cause of slow downloads.
Step 4: Enable DoH / DoT
Chrome Settings → Privacy and Security → Security → "Use secure DNS" → select Cloudflare (1.1.1.1). Once enabled, DNS queries themselves travel over HTTPS, and ISPs and intermediate nodes cannot poison them. On Android, you can fill in 1dot1dot1dot1.cloudflare-dns.com under "Private DNS" on the Wi-Fi settings.
Handling ISP Throttling
When Does Throttling Usually Appear?
ISP QoS policies suppress the speed of large file downloads, especially during peak hours from 8 PM to 11 PM. Download speeds are often compressed to 100-500KB/s. Between 1 AM and 6 AM, you can usually saturate your bandwidth.
Switch to a Different Link
- If the phone is slow on Wi-Fi, try 4G/5G mobile data first
- If the computer is slow at home, try using phone hotspot for downloading
- If you have multiple ISP broadbands, compare with another
Use a Download Tool for Segmented Downloads
Browsers' default single-threaded downloads are hit harder by ISP throttling. Switching to multi-threaded download tools (Motrix, IDM, aria2) can significantly improve performance. The Binance APK direct link generally allows 8-thread concurrency, improving speed 3-5x.
Disconnect and Reconnect to Refresh the Node
If the speed suddenly drops from 1MB/s to 30KB/s, it's most likely that the ISP has triggered sustained-transfer throttling. Pause the download for 30 seconds, or toggle airplane mode once to reconnect, letting the TCP connection reestablish. Often you can restore full speed.
Fixing CDN Node Mis-Selection
Binance CDN Distribution
Binance downloads use AWS CloudFront as the main CDN, with nodes in the Asia-Pacific region including Tokyo, Seoul, Singapore, Hong Kong, and Mumbai. Under normal ISP routing, the nearest node should be selected.
Symptoms of Node Mis-Selection
You're closest to the Hong Kong node, but routing takes you to the Frankfurt node. Round-trip latency goes from 30ms to 280ms, and download speed drops from 2MB/s to 150KB/s.
Correction Methods
- Switch DNS: 1.1.1.1's EDNS Client Subnet supports more accurate geolocation
- Try another time: CDNs periodically refresh geoIP mapping
- Use binance.info entrance to re-download, triggering a re-selection of nodes
Speed-Up Methods by Platform
Android APK
- If Chrome is slow, try Edge / Firefox / Brave, which use different download backends
- Enable browser experimental feature QUIC (chrome://flags search QUIC)
- Use Motrix / IDM for multi-threaded segmented downloads
iOS App Store
- "Settings → Wi-Fi → i icon next to connected Wi-Fi → Configure DNS → Manual", add 1.1.1.1 and 8.8.8.8
- Pause and resume the download: long-press the APP icon on the home screen → "Pause Download" → "Resume Download"
- Switch Apple ID region: if China region can't download Binance, switch to a US region account and re-download
Mac Client
- When .dmg downloads are slow, use the
curl -Ocommand line to download and see the real speed - Connect via VPN to a Hong Kong node, then download (note compliance)
Windows Client
- Disable "Scan downloads" in Windows Defender real-time protection (turn it back on after downloading)
- Download directly using PowerShell's
Invoke-WebRequest
4-Step Process for a Complete Fix
Step 1: Record the Baseline Speed
First test bandwidth with speedtest; then test single-connection download speed on dl.binance.io. A gap within 50% is normal.
Step 2: Switch DNS + Reconnect
Switch to 1.1.1.1 per the earlier method, refresh DNS cache, and re-download. You should usually see 2-5x speed-up immediately.
Step 3: Change the Download Tool
If the browser is slow, switch to a multi-threaded downloader like Motrix, with 8 threads.
Step 4: Change the Time Slot
If none of the above works, postpone the download to 2-4 AM. After 30 minutes of router restart + DNS flush, you can almost always finish the download.
FAQ
Why does the downloaded file have a .apk.download extension?
That's a temporary file during browser download. After the download completes, it's automatically renamed to .apk. If it stays stuck at .download, the download wasn't completed and needs to be restarted.
Why is it even slower when I connect to a VPN?
Some VPNs route through overseas nodes, which are farther from the Binance CDN and can be slower. Try disabling the VPN for a direct connection, or switch to a Hong Kong/Singapore node.
Can my home router cause slow downloads?
Yes. Older routers with congested 2.4GHz signals and poor NAT forwarding capability can compress downloads below 1MB/s. You can try: connecting to 5GHz, using wired Ethernet, restarting the router, and upgrading firmware.
My phone download finished but it's stuck at "Installing"?
Usually this is because system signature verification of the APK takes a while. Patiently wait 30 seconds. If it still doesn't move, restart the phone and tap the installer again. Don't repeatedly clear install data.
What if the version number after download is old?
Check whether you visited the real binance.com site; phishing sites often host an old APK. Go to the real site and re-download the latest version per the earlier method.
Will downloading via mobile hotspot burn through my data?
The Android full package is about 85MB, and the iOS package is about 200MB, equivalent to watching 3-8 minutes of short videos. Plans usually have plenty of room; but if you're in a throttled period after "unlimited data with 5GB daily soft cap", you'll be squeezed to tens of KB/s. In that case, waiting for Wi-Fi is more reliable.
Why does resumable downloading sometimes fail?
The Binance CDN has a time-window limit for persistent connections from the same IP; connections idle for over 60 seconds are reclaimed. If the download tool can't automatically rebuild the connection, it will prompt a resume failure. Just restart the full download from scratch.