Android 'Download Failed' on Google Play — Fix Guide

What it means

'Download failed' (sometimes shown with codes like 'Error retrieving information from server. [RPC:S-7:AEC-0]', 'Error 403', 'Error 495', or 'Error 504') means the Play Store reached the store but couldn't complete the install.
The usual causes are a glitched Play Store cache, low free storage, an unstable network, or a problem with your Google account on the phone.
It's almost always fixable in a few minutes without losing apps you already have.

Affected Models

All Android phones and tablets with Google Play
Common after switching Wi-Fi networks while a download was in progress
Also common on phones running low on internal storage

Common Causes

Google Play Store's cache or data is corrupted
Phone is low on free storage
Network dropped partway through the download (Wi-Fi to mobile data swap, weak signal)
Google Play Services is out of date or itself misbehaving
Phone's date and time are wrong
Multiple Google accounts on the phone and the Store is using the wrong one
A pending system update is interfering with installs
VPN or custom DNS on the router blocking Google's CDN

How to Fix It

Cancel the download, restart the phone, retry.

Open Play Store > profile > Manage apps & device > the failing download > tap the X to cancel.
Hold the power button and restart.
Open the app's Play Store page and tap Install again.
A clean retry after a restart fixes a surprisingly large share of cases.
Clear Play Store cache and data.

Settings > Apps > Google Play Store > Storage > Clear cache.
Try again.
If it still fails, come back to the same screen and tap Clear storage / Clear data — you won't lose installed apps; the Store just rebuilds its local index.
Also clear cache on Google Play Services and Download Manager.
Switch network and try again.

Many 'Download failed' errors are network-related.
If you were on Wi-Fi, switch off Wi-Fi and try over mobile data (and vice versa).
For a big app or game, a strong Wi-Fi connection is needed; a weak signal that keeps reconnecting causes failures partway through.
Check free storage.

Settings > Storage.
If you have less than a couple of gigabytes free, that's the problem — installs need scratch space.
Free up several gigabytes by clearing photos already backed up (Google Photos > Free up space), WhatsApp media, and apps you don't use, then retry.
Fix the date and time.

Settings > System > Date & time > Set automatically.
A wrong clock breaks Play Store's secure connection and downloads fail with no useful error.
This is a quick win that's easy to miss.
Use the right Google account.

Play Store > tap your profile photo top right > switch to the Google account you want to install with.
If the failing app was bought on a different account, you have to be signed into that one to install it.
This is the cause of many 'Download failed' errors on dual-account phones.
Remove and re-add the Google account, or update Play Services.

Update Google Play Services in the Play Store first.
If downloads still fail, remove the Google account (Settings > Accounts > Google > Remove account), reboot, add it back.
If you use a VPN or a custom DNS that filters Google domains (Pi-hole, ad-blocking DNS), turn it off during the install — those routinely break the Play Store's CDN downloads.

Frequently Asked Questions

Why does Google Play say Download failed but everything else on Wi-Fi works fine?

Because the Play Store uses Google's content delivery network and a few specific domains that other apps don't touch — so other apps can be fine while Play Store downloads break.
The usual cause is the Play Store's own cache (clear it in Settings > Apps > Google Play Store > Storage > Clear cache).
A custom DNS or VPN on the router can also block Google's CDN while leaving normal browsing alone — toggle them off briefly to test.
And on dual-account phones, make sure the Play Store is using the account that actually owns the app you're installing.