WhatsApp Web Login Not Working on Chrome? 9 Fixes (2026)

Quick answer: Fix WhatsApp login not working on Chrome by allowing cookies (including third-party) for [*.]whatsapp.com, clearing web.whatsapp.com site data, and disabling extensions that block scripts or WebSockets.

If it still fails, unregister WhatsApp’s service worker, test a clean Chrome profile, and check for managed policies or network filtering that blocks WhatsApp Web.

Quick Fix Checklist

• Open the correct URL: go to https://web.whatsapp.com/ (type it—don’t use old bookmarks/redirects).
• Hard refresh once: Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac).
• Test Incognito: Chrome menu > New Incognito Window > open web.whatsapp.com.
• Allow cookies: especially third-party cookies for WhatsApp domains.
• Clear WhatsApp Web site data: targeted wipe for web.whatsapp.com (not your whole browser).
• Disable/whitelist extensions: ad blockers, privacy tools, script blockers, antivirus web shields.
• Turn off VPN/proxy for a test: many block WebSockets or break TLS inspection.
• Try a different network: hotspot test quickly confirms corporate filtering.

Causes (realistic, not generic)

• Third-party cookies blocked: WhatsApp Web session creation can fail when Chrome blocks cross-site cookies/storage.
• Corrupted site storage: broken IndexedDB, Local Storage, or a stale Service Worker cache can cause blank pages, QR not loading, or login loops.
• Extension interference: blockers can prevent WhatsApp assets from loading or block WebSocket connections (common for “Connecting…”).
• Chrome profile issues: a damaged profile, sync conflict, or storage permission issue can break WhatsApp only in one profile.
• Managed device policies: work/school policies can enforce cookie rules or block WhatsApp domains.
• Network/HTTPS inspection: antivirus SSL scanning, corporate proxies, or DNS filtering can break WhatsApp endpoints.
• System clock mismatch: incorrect date/time can cause TLS failures that look like “can’t connect” or endless loading.

Cause	Fix that actually works
Third-party cookies blocked	Allow third-party cookies or add an exception for [*.]whatsapp.com
Corrupted WhatsApp Web storage	Clear site data for web.whatsapp.com + unregister Service Worker
Ad/privacy extension blocking scripts/WebSockets	Disable extensions or whitelist WhatsApp domains; retest in Incognito
Chrome profile corruption	Create a new Chrome profile and link WhatsApp there
Managed Chrome policies	Check chrome://policy; admin must allow WhatsApp + cookies
HTTPS scanning / proxy / DNS filtering	Disable SSL inspection for a test; change network or Secure DNS provider
Incorrect system time	Set OS time/date to automatic; restart Chrome

Step-by-Step Fix

1) Match the fix to your symptom (fast diagnosis)

• QR code not loading / blank page: usually blocked scripts, broken cache/service worker, or extension interference.
• QR scans but nothing happens: cookies/storage blocked, corrupted site data, or third-party cookie restrictions.
• Stuck on “Connecting…”: WebSocket blocked by extension, VPN/proxy, DNS filtering, or HTTPS scanning.
• Instant logout / keeps asking to link device: cookies cleared on exit, strict privacy settings, or profile issues.

2) Allow cookies (including third-party) for WhatsApp Web

This is the most common reason a WhatsApp login problem solution is “not working on Chrome”.

• Open Chrome Settings > Privacy and security > Third-party cookies.
• Fast test: choose Allow third-party cookies, reload web.whatsapp.com, try linking again.
• Better long-term: keep your preferred setting, but add an exception under Sites allowed to use third-party cookies for [*.]whatsapp.com.

If you clear cookies on exit, WhatsApp will keep logging out.

• Go to Settings > Privacy and security > Site settings > Additional content settings > On-device site data.
• Add [*.]whatsapp.com to Allowed to save data on your device.

3) Clear only WhatsApp Web site data (targeted reset)

This fixes most QR/login loops without wiping all Chrome data.

• Open web.whatsapp.com.
• Click the lock icon in the address bar > Site settings.
• Click Clear data (or Delete data).
• Close the tab completely, reopen web.whatsapp.com, scan the QR again.

If the page still behaves like it’s “stuck”, do the service worker reset next.

4) Advanced fix: unregister WhatsApp Web Service Worker + clear storage

WhatsApp Web uses a service worker for caching. If it gets corrupted, normal refreshes can keep reloading broken assets.

• Open web.whatsapp.com.
• Open DevTools: F12 (or Ctrl+Shift+I / Cmd+Option+I).
• Go to Application > Service Workers > click Unregister.
• In Application > Storage > click Clear site data.
• Hard reload: right-click the reload icon > Empty Cache and Hard Reload.

5) Disable extensions that commonly break WhatsApp login

If WhatsApp works in Incognito but not normal Chrome, an extension is the #1 suspect.

• Open chrome://extensions.
• Temporarily toggle off, then retry WhatsApp Web:

• Ad blockers (uBlock Origin, AdGuard)
• Privacy tools (Privacy Badger, Ghostery)
• Script blockers (NoScript)
• Antivirus “web protection” extensions
• Password managers that inject scripts into pages

If you must keep the extension, whitelist:

• https://web.whatsapp.com
• https://*.whatsapp.com

6) Reset site permissions (fix blocked pop-ups, notifications, camera/mic)

Permissions rarely stop basic messaging, but they can break linking flows or calls.

• Open web.whatsapp.com > lock icon > Site settings.
• Set Pop-ups and redirects to Allow (or reset to default).
• Set Notifications to Ask (or Allow if you want desktop alerts).
• For calling features: set Camera and Microphone to Allow.
• Click Reset permissions (if shown), then reload.

7) Fix “Connecting…” by testing WebSocket/network blocks

“Connecting…” is often a network path issue, not a WhatsApp account issue.

• Turn off VPN/proxy and reload WhatsApp Web.
• Disable antivirus HTTPS/SSL scanning (or add an exception) for a test. Look for settings like Web Shield, SSL inspection, or HTTPS scanning.
• Switch networks (mobile hotspot test). If it works on hotspot, your main network is filtering WhatsApp Web.
• Change Secure DNS: Chrome Settings > Privacy and security > Security > Use secure DNS > switch provider or turn off to test.

8) Fix Chrome profile corruption (when only one profile fails)

If Incognito works but normal mode fails even after clearing site data, your profile may be damaged or restricted.

• Chrome menu (top right) > profile icon > Add (create a new profile).
• Open web.whatsapp.com in the new profile and try linking.
• If it works, migrate gradually (bookmarks/passwords) and keep WhatsApp Web on the clean profile.

9) Check for enforced policies (work/school devices)

On managed devices, you may not be able to fix this yourself.

• Open chrome://policy > click Reload policies.
• Look for cookie/URL restrictions such as:

• BlockThirdPartyCookies
• CookiesAllowedForUrls / CookiesBlockedForUrls
• URLBlocklist / URLAllowlist

If these are enforced, ask your admin to allow https://web.whatsapp.com and permit cookie/storage access for [*.]whatsapp.com.

Still Not Working

• Check your system time (surprisingly common): set your computer’s date/time/timezone to automatic, then restart Chrome. Incorrect time can break secure connections and cause endless loading.
• Confirm Chrome is updated: open chrome://settings/help and update, then relaunch. Outdated builds can break modern web app features.
• Run a clean-room test (best isolation):
  • Create a new Chrome profile (no extensions).
  • Do not sign into Chrome sync yet.
  • Try web.whatsapp.com. If it works, the issue is your extensions, sync, or profile settings.
• Use DevTools to identify the blocker (real tech support step):
  • Open DevTools > Console: look for errors like IndexedDB blocked/denied, ERR_BLOCKED_BY_CLIENT (extension), or CSP violations.
  • DevTools > Network: reload and filter for blocked or ws (WebSocket). If requests are blocked, it’s usually an extension, proxy, or security product.
• Edge case: storage is blocked by settings: if you use strict privacy modes, ensure JavaScript is allowed and site data isn’t blocked for WhatsApp (Site settings > JavaScript / On-device site data).
• Try WhatsApp Desktop as a workaround: if your Chrome environment is policy-restricted, the desktop app may work even when WhatsApp Web is blocked.
• Escalation steps:
  • If you’re on a managed device, send your admin screenshots/exports from chrome://policy and request allowlisting for WhatsApp Web.
  • If it fails on multiple browsers and networks, check WhatsApp’s official help center and in-app Linked devices status; the issue may be account/device-side.
  • As a last resort, reinstall Chrome (after syncing/exporting bookmarks) to replace a corrupted installation/profile directory.

Fixes for Chrome

This section covers a specific troubleshooting angle related to whatsapp login problem solution not working on chrome. Use it to narrow the issue before moving to deeper fixes.

Why this happens

Problems like this often come from one of three areas: local app state, network conditions, or a recent configuration change.

How to fix it

1. Confirm the exact symptom before changing multiple settings at once.
2. Restart the app and the device before trying advanced fixes.
3. Test on a different network or device if possible.
4. Keep note of any exact error message because it often points to the real cause.

Important notes

• If the basic checks change the behavior, that usually tells you where the issue really lives.
• Move to stronger fixes only after the quick isolation steps above.

If the App Fails but the Browser Works

If the browser version works but the app fails, the account itself is usually not the problem.

Why this happens

This pattern normally points to corrupted app cache, stale local session data, or a device-specific networking issue.

How to fix it

1. Use the working browser session as a control test while troubleshooting the app.
2. Force close the app and reopen it before trying the same action again.
3. Disable VPN, proxy, DNS filtering, or security apps temporarily.
4. Update or reinstall the app if the same failure only appears inside the app.

Important notes

• This is one of the fastest ways to narrow the issue to the app layer instead of the account layer.
• If the app still fails after reinstalling, the device configuration may be the next thing to inspect.

Frequently Asked Questions