If Amazon is not letting you sign in, reset your password, confirm verification codes, and clear app or browser data to get back in.
If you’re stuck thinking “amazon is not letting me sign in,” don’t keep poking the login box. Repeated guesses can trigger a lock, captchas, or a cooldown timer. A calmer plan works better this time.
This checklist starts with the fastest fixes, then moves into password resets, two-step code problems, lock screens, and device or network quirks. Go in order and stop when you’re back in.
Keep your inbox open, keep your phone charged, and stay on one device until you’re signed in.
Amazon Is Not Letting Me Sign In on Phone or PC
Start with checks that take under two minutes. They fix a lot of sign-in trouble because they remove simple mismatches that the error message won’t spell out.
- Use the right Amazon site — Open Amazon from a bookmarked home page, not an old email link, and confirm the country domain matches your account.
- Try your other login ID — If you sometimes sign in with a phone number and other times with email, test both and watch for small typos.
- Type the password once — Autofill can paste an older password. Enter it manually one time to rule that out.
- Wait one full minute — After several tries, Amazon may slow responses. A short pause can clear rate limits.
If you see a wrong-password message, stop guessing. A clean reset is safer and usually faster than trial and error.
Fast symptom map
Use this table to match what you see to the next step. It keeps you from bouncing around and making the lockouts worse.
| What you see | What it often means | Try this first |
|---|---|---|
| Password rejected | Old saved password or typo | Run one password reset |
| Code never arrives | Email delay, SMS blocked, wrong number | Switch the code method |
| Captcha repeats | Bad cookies, extensions, or VPN | Private window, then clear site data |
| Account locked message | Too many attempts or a risk flag | Wait, then use recovery steps |
Amazon sign in not working on web and app
Sometimes your password is correct, but the sign-in page loops, reloads, or freezes on the same screen. That’s usually stored site data or a blocker that stops the page from loading the code prompt.
Fix browser sign-in loops
Run these steps on the device where the web sign-in fails. Don’t change three things at once. One clean change, then retry.
- Open a private window — Sign in there. If it works, cookies or an extension in your normal window is the culprit.
- Clear Amazon site data — Remove cookies and cached files for Amazon only, then restart the browser.
- Disable extensions briefly — Ad blockers and script filters can break captcha and code prompts. Turn them off for the login step.
- Turn off VPN or proxy — A changing IP can trigger extra checks. Use your normal connection for sign-in.
- Try a second browser — If one browser stays stuck, switch to another to finish the login, then return later.
Fix Amazon app sign-in loops
On phones, cached app data can trap you in an old session. Clearing it forces the app to rebuild the sign-in flow from scratch.
- Update the app — Install the latest Amazon app from the app store, then retry.
- Force close the app — Swipe it away, then reopen to refresh the session.
- Clear app cache or storage — On Android, clear cache first, then storage if needed. On iPhone, offload or reinstall to wipe stored app data.
- Restart the phone — A reboot clears stuck background tasks that can block login screens.
After you clear app data, you may need to sign in again on other devices.
Fix password resets and verification code failures
If your password is wrong or stale, the fastest path is a single reset. Amazon’s password assistance flow can send a one-time password by email or SMS to confirm it’s you, then it activates the new password right away.
Reset your Amazon password the clean way
- Use Password assistance — Tap “Forgot password” on the sign-in page and enter the email or phone number tied to the account.
- Enter the one-time password — Use the code from the email or SMS message that arrives from Amazon.
- Create a fresh password — Pick a new password you haven’t used on Amazon, then sign in once.
- Update saved logins — Replace the stored password in your browser and password manager so it won’t keep pasting the old one.
Get the code to arrive
Codes can fail due to carrier filtering, inbox rules, or a phone number change.
- Search your inbox — Look for “Amazon” and “OTP” and open the newest message, not an older one.
- Check spam filters — Review spam and promotions tabs, then mark the sender as safe if your mail app offers that control.
- Switch the code method — If SMS fails, try email, voice call, or an authenticator method if Amazon offers it.
- Request one code, then wait — Repeated taps can trigger cooldown timers. Request once, then wait a few minutes.
- Refresh your phone signal — Toggle airplane mode, then retry so the phone re-registers on the network.
Use the alternate code entry for two-step verification
On some devices, the code box never appears, even when two-step verification is active. Amazon documents an alternate sign-in path where the code is entered as part of the password.
- Submit email and password — Sign in as usual, even if you don’t see a code prompt.
- Wait for the code — If you get an error, stay on the sign-in page and wait for the SMS, call, or authenticator code.
- Add the code to the password — Type your password again and append the code to the end with no spaces, then submit.
If you can’t access the phone number or authenticator you set up, you’ll need recovery steps. The next section shows that path.
Stop lock screens, captcha loops, and identity checks
After too many attempts, a new device, or a new network, Amazon may add extra checks. At that point, guessing passwords makes things worse. Your job is to remove triggers, then retry from one clean device.
Break a captcha loop
- Clear Amazon cookies — Delete cookies and cached files for Amazon, then restart the browser.
- Turn off blockers briefly — Disable ad blockers or script filters for the sign-in step, then turn them back on.
- Switch networks — Move from public Wi-Fi to mobile data or a home connection.
- Use the Amazon app — The app often completes sign-in when a browser session is flagged.
Handle “locked” or “verify your identity” prompts
A lock message can clear after a short wait. Some accounts still require an identity check. If the screen asks you to verify ownership, follow the on-screen steps and prepare for a document upload request on some flows.
- Stop attempts and wait — Close the tab or app and wait at least 15 minutes so you don’t extend the lock.
- Run one password reset — Use password assistance once, then retry from a private window or the app.
- Finish verification in one sitting — If Amazon requests extra checks, complete them at once so you don’t time out mid-process.
- Contact Amazon customer service — If you’re stuck at a verification screen, use the official help pages to reach customer service and ask for account access recovery.
Watch for scams while you’re stressed. Amazon won’t ask for gift card codes to restore access, and a real Amazon email will not push you to call a random phone number.
Fix device, time, and network issues that block sign-in
If sign-in fails on one device but works on another, your account is probably fine. Stick with the device that fails and clean up time, network, and storage issues that break secure sessions.
Sync date and time
Secure cookies and time-based codes rely on a correct clock. A clock that drifts can break sign-in even when your password is correct.
- Set time automatically — Turn on automatic date and time on your phone or computer, then restart the browser or app.
- Reboot after the change — Restarting forces apps to rebuild secure sessions with the corrected clock.
Stabilize your connection
Amazon sign-in uses several services at once. A shaky network can load the page but fail during the captcha or code step.
- Swap Wi-Fi and mobile data — Switching connections separates account issues from router issues fast.
- Restart your router — Power it off for 30 seconds, then reconnect and retry.
- Try a different DNS — If your ISP DNS is flaky, switch to a public DNS and try again.
- Use an unrestricted network — Work and school networks can block scripts needed for captcha and code screens.
Check storage and permissions on phones
Low storage and blocked permissions can stop the app from saving session data. That can throw you back to the login screen again and again.
- Free up space — Keep a few hundred MB free so the app can write cache and session files.
- Allow network access — Make sure the Amazon app can use cellular data and background refresh.
- Update your system — Older system web components can fail on modern sign-in pages.
Recover access and avoid the same login trap next time
Once you’re back in, take two minutes to set up backup routes. That way a dead phone, a changed number, or one bad browser update won’t lock you out again.
Set up backup sign-in options
- Confirm email and phone on file — Update your contact info so codes go to an account you can still open.
- Add an authenticator method — If Amazon offers it, an authenticator app can be steadier than SMS in some areas.
- Save backup codes securely — If you get one-time backup codes, store them in a password manager or an offline note.
Clean up saved logins across devices
- Update password manager entries — Replace old Amazon records so autofill won’t fight your new password.
- Sign out of old devices — Remove devices you no longer use from your account settings.
- Keep the app current — Updates can fix login bugs and keep the sign-in flow compatible.
Know when the issue is on Amazon’s side
If every device fails at the same moment, password reset emails never arrive, and the site won’t load past login, the issue may be an Amazon outage. In that case, step away and try later from one device. Repeated attempts won’t speed it up.
If you’re still stuck, re-run the first section slowly on one device, then try a password reset once more. Most “amazon is not letting me sign in” cases come down to a wrong login ID, a password mismatch, or a code route that needs a reset.
