Quick answer: If WhatsApp login error on Chrome today happens on WhatsApp Web, start with a fresh QR code, your phone’s Linked devices screen, and Chrome’s WhatsApp site data. This is usually caused by an expired session, a verification loop, OTP not received, or a temporary account lock from too many attempts. Do not reset, reinstall, or wipe anything until these safer checks are complete.
If Chrome keeps sending you back to login, says verification failed, or will not complete sign-in after scanning, the fastest fix is to clear the broken web session and retry once carefully instead of repeating attempts.
Quick Fix Checklist
- Reload web.whatsapp.com and scan only the newest QR code.
- On your phone, open WhatsApp > Linked devices and confirm you are still signed in on the phone itself.
- Remove any stale Chrome session from Linked devices if it appears stuck or duplicated.
- If Chrome shows verification failed or loops back to login, close the tab fully and reopen a fresh WhatsApp Web tab.
- If you are waiting for an OTP, request it once and wait. Repeated requests can trigger a temporary block.
- If you see too many attempts, try again later, or an account lock warning, stop retrying and let the limit window expire.
- Check Chrome site data for web.whatsapp.com and remove only WhatsApp Web data if the session appears corrupted.
- If the problem started today after a Chrome update, test in an Incognito window to rule out a broken cookie or extension conflict.
Causes
Most WhatsApp login errors on Chrome today are auth problems, not general browser failures. The goal is to identify whether the block is caused by a bad session, failed verification, OTP delay, or a temporary security limit.
| Cause | What it looks like | Fix |
|---|---|---|
| Expired session | Chrome asks you to sign in again or logs you out suddenly | Refresh WhatsApp Web, remove the old linked session, and pair again with a new QR code |
| Verification loop | You scan the QR code, then return to the login screen again | Close the tab, reopen WhatsApp Web, and retry once after removing the stale session |
| Verification failed | Chrome accepts the scan but does not complete sign-in | Use a fresh QR code, confirm the phone is online and signed in, then retry carefully |
| OTP not received | The code never arrives or arrives too late to use | Wait before requesting another code and avoid repeated requests |
| Too many attempts / rate limit | WhatsApp says try again later or blocks more login attempts | Stop retrying, wait for the cooldown, then use one clean login attempt |
| Corrupt Chrome session cookie | Login fails only in Chrome but works elsewhere | Clear WhatsApp Web site data in Chrome or test in Incognito |
| Account security check | WhatsApp asks for extra verification or rejects unusual sign-in behavior | Complete the requested verification and avoid switching devices or retrying rapidly |
Step-by-Step Fix
- Use a new QR code, not the old one. Open web.whatsapp.com in Chrome and reload the page once. Scan only the current QR code because older codes often fail after a session expires.
- Check that your phone is still properly signed in. Open WhatsApp on your phone and make sure your main account opens normally. Then go to Linked devices and confirm Chrome is ready to pair or remove any stale web session.
- Fix a session expiration cleanly. If WhatsApp Web logged you out suddenly, remove the old Chrome session from Linked devices and sign in again with a fresh scan. This is safer than repeated retries on a broken session.
- Handle verification failed or a verification loop. If scanning works but Chrome returns to the login page, close the tab completely, reopen WhatsApp Web, and retry once. If the old Chrome session still appears on the phone, remove it first.
- If OTP is not received, slow down. Request the code once and wait for the full delivery window. Do not keep tapping resend, because repeated requests can trigger a temporary rate limit or delay the next code.
- Watch for too many attempts or account lock messages. If WhatsApp says you cannot log in right now, stop all attempts for a while. Repeated sign-in attempts can extend the lock window.
- Clear only WhatsApp Web site data in Chrome. In Chrome, open site settings for web.whatsapp.com and remove cookies/site data for that site only. This is an advanced but safe fix when the auth cookie or session token is stuck.
- Test in Chrome Incognito. If WhatsApp Web logs in normally there, the problem is usually a cookie, saved session, or extension conflict in your regular Chrome profile.
- Check whether the problem started after a Chrome update. If login broke right after Chrome updated, test with extensions disabled or in a fresh profile. Some privacy or script-blocking extensions interfere with QR pairing and session storage.
- Retry once after waiting. After clearing the stale session or waiting out a rate limit, make one careful login attempt. One clean attempt is better than multiple rapid retries.
Still Not Working
- Works on Wi-Fi but not on mobile data: this can point to a temporary verification or OTP delivery issue tied to your carrier path. Wait for the OTP window to expire, then request one new code only once.
- Works in another browser but not Chrome: the issue is likely Chrome-specific session data, blocked cookies, or an extension conflict. Clear WhatsApp Web site data in Chrome and test again in a normal window with extensions disabled.
- Works on another device but not this Chrome profile: your current Chrome profile likely has a bad stored session token. Remove the linked session from your phone, then sign in again from a fresh Chrome tab.
- Started after a Chrome update: test in Incognito first. If that works, disable privacy, ad-block, or script-control extensions one by one because they can break login storage or QR verification.
- Only one WhatsApp account is affected: this usually points to an account-specific verification check, rate limit, or temporary lock rather than a browser-wide problem. Stop retrying and wait before trying again with the same number.
- Fails on all networks and all browsers: this is more likely an account lock, verification hold, or service-side auth problem. At that point, avoid more attempts and use official WhatsApp support or in-app account recovery steps.
- OTP still not received after waiting: verify that the phone number format is correct and that you are requesting the code for the same account. Do not keep requesting new codes back-to-back.
- Session keeps expiring immediately after login: remove every old linked web session from your phone, then pair Chrome again once. Immediate logout often means the old token was never fully replaced.
- Escalation step: if you have waited through the rate-limit window, tested another browser, and confirmed the phone account is active, contact WhatsApp support from the official app or help center. Reinstall only after auth checks fail everywhere, because reinstalling does not usually fix account locks or OTP delays.
Why is WhatsApp not working on Chrome today?
Usually because the WhatsApp Web session expired, the QR sign-in looped, verification failed, or Chrome stored a bad auth session. Start with a fresh QR code and Linked devices on your phone.
Why does WhatsApp Web keep logging me out after I scan the QR code?
This usually means the old session token is stale or the new login was not fully accepted. Remove the old linked session from your phone and pair Chrome again with a new QR code.
What should I do if OTP is not received for WhatsApp login?
Request the code once, then wait for the delivery window to finish. Do not keep requesting new codes, because that can trigger a temporary block or delay.
Why does WhatsApp say I can’t log in right now?
That message usually means a temporary rate limit, too many attempts, or an extra security check on the account. Stop retrying and try again later with one clean sign-in attempt.
Why does WhatsApp verification fail on Chrome only?
If it fails only in Chrome, the most likely cause is corrupted site data, blocked cookies, or an extension conflict. Test in Incognito and clear site data for web.whatsapp.com if needed.
Should I reinstall WhatsApp to fix a Chrome login error?
No, not first. Reinstalling rarely fixes expired sessions, verification loops, OTP delays, or account locks, so finish the safer auth checks before trying anything disruptive.
Frequently Asked Questions
Why is WhatsApp not working on Chrome today?
Usually because the WhatsApp Web session expired, the QR sign-in looped, verification failed, or Chrome stored a bad auth session. Start with a fresh QR code and Linked devices on your phone.
Why does WhatsApp Web keep logging me out after I scan the QR code?
This usually means the old session token is stale or the new login was not fully accepted. Remove the old linked session from your phone and pair Chrome again with a new QR code.
What should I do if OTP is not received for WhatsApp login?
Request the code once, then wait for the delivery window to finish. Do not keep requesting new codes, because that can trigger a temporary block or delay.
Why does WhatsApp say I can’t log in right now?
That message usually means a temporary rate limit, too many attempts, or an extra security check on the account. Stop retrying and try again later with one clean sign-in attempt.
Why does WhatsApp verification fail on Chrome only?
If it fails only in Chrome, the most likely cause is corrupted site data, blocked cookies, or an extension conflict. Test in Incognito and clear site data for web.whatsapp.com if needed.
Should I reinstall WhatsApp to fix a Chrome login error?
No, not first. Reinstalling rarely fixes expired sessions, verification loops, OTP delays, or account locks, so finish the safer auth checks before trying anything disruptive.