How to Fix Google Play Store Error 481
What error 481 means
Error 481 is a Google Play Store account error that appears when Google’s servers refuse to accept the account your phone is signed into. The message shows up the moment you try to download or update anything: the store knows who you claim to be, but the account fails its handshake on Google’s side, so the download dies before it even starts.
What makes 481 different from its neighbors like 491, 492, or 495 is where the fault lives. Those errors are usually about corrupted cache or download data — cleaning the store’s storage fixes them. Error 481 is famous as the one that often means the account itself is the problem: the account may have been deleted or disabled on Google’s side, its password may have changed elsewhere, or its authentication session may be damaged beyond repair. That is why the standard advice for this code starts at Settings > Accounts, not Settings > Apps.
The good news is that a dead session is far more common than a dead account. Most of the time, removing the account from the phone and adding it back rebuilds the link and 481 disappears immediately — the whole repair takes a few minutes and costs you nothing. Only when the account itself is genuinely gone do you need the heavier steps further down. Work through the fixes in order; the very first step tells you which path you are on.
Common causes
- Deleted or disabled Google account: the account was removed or suspended on Google’s side, so the phone’s stored credentials point at an account that no longer exists — the classic trigger for 481.
- Broken authentication session: the sign-in token on the phone went stale or corrupt, and Google’s servers now reject every request the Play Store makes with it.
- Password changed elsewhere: the account password was changed on another device or a browser, and the phone is still trying to authenticate with the old credentials.
- Corrupted Play Services account data: Google Play Services holds the master copy of the account state, and if that copy is damaged, every app that depends on the account — including the Play Store — fails along with it.
- Account sync conflict after device changes: a factory reset, a transferred account, or a long-dormant phone can leave the on-device account record out of sync with Google’s records.
How to fix error 481 — step by step
Work through these fixes in order. Step 1 tells you whether your account is alive — do not skip it.
- Check whether your Google account still exists. On any device with a browser, go to accounts.google.com and try signing in with the same email and password your phone uses. If the sign-in fails or Google says the account was deleted or disabled, error 481 is telling you the truth: the account your phone is attached to is gone from Google’s side, and no amount of cache clearing will fix that. In that case, skip ahead to step 5 and move to a working account instead.
- Remove and re-add your Google account. This is the fix that resolves most 481 cases, because it rebuilds the broken link between your phone and Google’s servers. Open Settings, then go to Passwords & accounts (or Accounts & backup, then Accounts). Tap your Google account, then tap Remove account and confirm. Restart the phone, return to Settings > Passwords & accounts, tap Add account > Google, and sign back in with the same account. Open the Play Store and try a download.
- Clear the Google Play Store’s cache and data. If the account re-add alone does not clear the error, stale store data may still be holding the old broken session. Open Settings, then go to Apps (or Apps & notifications), then See all apps. Tap Google Play Store, then Storage & cache. Tap Clear cache first, then Clear storage (or Clear data) and confirm. Reopen the Play Store, accept the terms again, and retry the download.
- Clear Google Play Services data. Play Services holds the account authentication state the store relies on, and wiping it forces a fresh handshake with Google’s servers. In Settings > Apps > See all apps, tap Google Play Services, then Storage & cache. Tap Clear cache first, then Clear storage (or Clear data) and confirm. Note that clearing Play Services data can temporarily make your other Google apps act up until everything re-syncs, so give the phone a few minutes afterward.
- Sign in with an alternate Google account. If 481 keeps appearing after the fixes above, the account itself is the problem, and the only way forward is a different one. Go to Settings > Passwords & accounts, tap Add account > Google, and sign in with another Gmail address (or create a new Google account at accounts.google.com). In the Play Store, tap your profile icon and switch to the new account, then try downloading again. Your old paid apps stay tied to the old account, so this is the step to take only after you are sure the original account cannot be recovered.
- Try Google account recovery. Visit accounts.google.com/signin/recovery and follow the recovery flow with any phone number, recovery email, or device Google has on record for you. If recovery succeeds, the re-added account will clear error 481 on its own. If the account was permanently deleted by Google or recovery fails, your options are the alternate account from step 5 or, as a last resort, a factory reset (Settings > System > Reset options > Erase all data) after backing up everything.
Did this fix it? Quick checklist
- The Play Store downloads apps and updates without the 481 error
- Your Google account stays signed in after the phone restarts
- The account signs in normally at accounts.google.com in a browser
- Play Services syncs without authentication warnings
If error 481 still appears after all six steps, the original account is almost certainly unusable. Commit to the alternate account from step 5 (paid apps are tied to the account that bought them, so this decision is permanent) or contact Google support if you believe the account was disabled by mistake.
Frequently asked questions
What does Google Play Store error 481 mean?
Error 481 means there is a serious problem with the Google account linked to your phone — Google’s servers no longer accept it for Play Store access. Unlike cache errors, this one lives at the account level: the account may have been deleted or disabled, its password may have changed, or its sign-in session may be broken beyond repair. That is why the standard fix is to remove the account from the phone and sign back in, or move to a working account.
Is my Google account deleted if I see error 481?
Not necessarily, but it is a real possibility — 481 is famous for appearing when the account was deleted on Google’s side. Before assuming anything, sign in to the account in a browser at accounts.google.com. If the sign-in works, your account is alive and the problem is just a broken session on the phone, which removing and re-adding the account will fix. If the sign-in fails, try account recovery or switch to an alternate account.
Will I lose my data when I remove my Google account from my phone?
Removing the account only unlinks it from the phone — it does not delete your Google data. Your emails, contacts, photos in Google Photos, Drive files, and purchased apps stay attached to the account in Google’s cloud. When you add the same account back, everything syncs again. Just make sure you know the account’s password before removing it, and note that paid apps are permanently tied to the account that bought them, not the phone.
What if error 481 persists after removing and re-adding my account?
If the error survives a clean account re-add plus clearing the Play Store’s and Play Services’ data, the account itself is almost certainly unusable. Sign in with an alternate Google account (step 5) — if downloads work under the new account, that confirms the diagnosis. Your remaining options are Google’s account recovery flow, contacting Google support for a disabled account, or as a last resort a factory reset after a full backup.