Last updated: March 16, 2026
WhatsApp Web connection problems are almost never random. The error you're seeing — whether it's a blank QR screen, a "Phone not connected" banner, or a session that drops every few minutes — points to a specific cause. This guide works through each scenario separately so you're not wasting time on fixes that don't apply to your situation.
Before anything else: identify what you're actually seeing.
The QR code never loads at all → jump to Section 1
QR code loads but scanning does nothing → jump to Section 2
"Phone not connected" message after it was working → jump to Section 3
Connects fine but drops every few minutes → jump to Section 4
Blocked on a work or school network → jump to Section 5
If you go to web.whatsapp.com and see a loading spinner that never resolves into a QR code, something is actively blocking the connection before it starts. This is almost always one of three things.
Ad blockers and privacy tools like uBlock Origin, Privacy Badger, Ghostery, and even some VPN browser extensions intercept the WebSocket connection WhatsApp Web needs to generate the QR code. The page loads because it's HTML, but the real-time connection — which is what generates that QR — gets killed silently.
The fastest test: open a new incognito/private window in the same browser. Incognito disables most extensions by default. If the QR code loads there, you've confirmed an extension is the problem. Go back to your normal window, disable extensions one at a time, and reload to find the culprit. uBlock Origin is responsible more often than not.
If incognito also fails, the block is at the network level — not the browser. Check if you're on a custom DNS server (like 1.1.1.1 or 8.8.8.8) or if any proxy is configured in your system settings. Temporarily switch back to your ISP's default DNS and test again. On Windows, this is under Network & Internet Settings > Change adapter options > TCP/IPv4 properties.
A surprisingly common one. Make sure you're going to web.whatsapp.com, not www.whatsapp.com/web or any third-party site. Bookmark the correct URL after you confirm it's working.
privacy.resistFingerprinting set to true. This breaks WhatsApp Web's session detection. Chrome or Edge are more reliable for WhatsApp Web.
You see the QR code, you open WhatsApp on your phone, you scan it — and then either nothing happens, the code resets immediately, or you get a brief "connecting" message that then fails. This is a different problem entirely.
WhatsApp allows a maximum of 4 linked devices per account (not counting your primary phone). If you've linked this browser before plus a desktop app plus a tablet, you may be at the limit. On your phone, open WhatsApp, tap Settings > Linked Devices. You'll see every active session listed with device name and approximate last active time. Log out of any sessions you don't recognize or no longer need, then try scanning again.
WhatsApp's authentication is time-sensitive. If your phone's clock is off by more than a couple of minutes — because you manually set it or your timezone auto-detection misfired — the QR code handshake will silently fail, and the code will just reset. On iPhone, go to Settings > General > Date & Time and turn on "Set Automatically." On Android it's under Settings > General Management > Date and Time. After fixing the time, force-close WhatsApp and try scanning again.
If your WhatsApp version is significantly out of date, it may no longer be able to authenticate with WhatsApp Web's current protocol. Check your app store for pending updates. WhatsApp pushes protocol changes periodically, and old versions stop working with the web interface without any clear error message.
Less common but real: if WhatsApp doesn't have camera permission on your phone, the QR scanner will open but can't actually read the code. You might see it scanning visually but it never triggers. Check Settings > Privacy > Camera (iOS) or Settings > Apps > WhatsApp > Permissions (Android) and make sure camera access is granted.
This is the most frequently reported WhatsApp Web issue, and also the most misdiagnosed. People assume it's a browser problem or a network problem, but nine times out of ten the issue is on the phone side — specifically, the phone's operating system has suspended or killed the WhatsApp background process.
In WhatsApp's legacy mode (the older version, still used by some accounts), the web session runs through your phone as a relay. The phone must have WhatsApp running in the background and connected to the internet at all times. When the phone's OS aggressively manages battery by freezing background apps — which both Android and iOS do under certain conditions — the relay breaks and WhatsApp Web loses its connection.
Multi-device mode changed this. If your account has multi-device enabled, WhatsApp Web operates independently of your phone after the initial linking. But even in multi-device mode, sessions still need the phone to come online periodically — usually within 14 days.
When Low Power Mode is active on iPhone, iOS severely restricts background activity for most apps, including WhatsApp. This means the moment your iPhone screen turns off, WhatsApp stops maintaining its connection to WhatsApp Web. The fix isn't just to turn off Low Power Mode — you should also go to Settings > WhatsApp > Background App Refresh and make sure it's turned on. Without Background App Refresh, iOS won't let WhatsApp maintain a connection when the app isn't in the foreground.
Also check: if you have Focus modes active (like Do Not Disturb or Sleep Focus), some of these configurations restrict background activity as a side effect. Go to Settings > Focus and check whether your current Focus mode has app restrictions.
Android's battery optimization features, especially on Samsung, Xiaomi, OnePlus, and Huawei devices, are extremely aggressive. The OS learns that WhatsApp hasn't been opened manually for a few minutes and suspends its background processes to save battery. From WhatsApp Web's perspective, the phone has gone offline.
The path varies by manufacturer, but the general approach:
Samsung-specific: Also go to Settings > Device Care > Battery > Background Usage Limits and check the "Sleeping apps" list. Samsung silently moves apps into this list after periods of inactivity. If WhatsApp is listed there, remove it.
Xiaomi/MIUI-specific: Go to Settings > Apps > Manage Apps > WhatsApp > Battery Saver, and set it to "No restrictions." MIUI's battery management is the most aggressive of any Android skin and will cause WhatsApp Web to drop without this setting.
Some routers have client isolation or Wi-Fi sleep settings that disconnect idle devices. Also, Android has a "Keep Wi-Fi on during sleep" setting that may be set to "Only when charging" — meaning when you put your phone down, it drops Wi-Fi and switches to mobile data, which can briefly interrupt the WhatsApp connection. Find this under Settings > Wi-Fi > Advanced > Keep Wi-Fi on during sleep and set it to "Always."
A session that works initially but drops on a regular cycle — say, every 5 to 15 minutes — is almost always the Android battery optimization issue described in Section 3. But if you've already addressed that and the problem continues, there are a few other causes worth checking.
Modern browsers throttle or suspend background tabs to save resources. If you have WhatsApp Web open in a tab behind other tabs, and you don't interact with it for a while, the browser may throttle its WebSocket connection. The fix is simple: keep the WhatsApp Web tab active or use the WhatsApp Desktop app instead, which doesn't have this limitation.
In Chrome specifically, you can test whether tab throttling is the cause by going to chrome://flags and searching for "throttle." However, permanently disabling tab throttling affects battery and performance. The desktop app is a better long-term solution if you use WhatsApp Web regularly for work.
WhatsApp multi-device sessions expire after 14 days of inactivity on that specific browser. This isn't a 14-day timer from first linking — it resets each time you actively use the session. If you come back after two weeks away, you'll need to re-scan the QR code. This is by design and isn't a bug you can fix.
If you're logged into WhatsApp Web on both your work computer and a personal laptop, and your phone is in legacy mode (not multi-device), only one web session was supported historically. WhatsApp has largely moved past this with multi-device, but if your account is still on the older mode, logging in from a second computer will kill the first session. Check your Linked Devices list to see what's active.
Workplace and university networks commonly block WhatsApp Web specifically. It's not always blanket "no messaging apps" — some networks block the WebSocket connections WhatsApp Web relies on while leaving regular web traffic alone. Signs you're dealing with this: the page loads, you can see the WhatsApp Web interface, but the QR code never appears or the session never fully establishes.
The simplest test: enable your phone's mobile hotspot and connect your laptop to it. If WhatsApp Web works immediately on mobile data but not on the office Wi-Fi, the network is filtering it. You don't need to troubleshoot further — it's a policy enforcement, not a technical problem you can solve from your device.
The WhatsApp Desktop application (available at whatsapp.com/download) uses a different connection method than the browser-based version and sometimes works on networks that block the web version. This isn't guaranteed — heavily filtered networks block both — but it's worth trying before you give up.
Ask your IT department to whitelist web.whatsapp.com and *.whatsapp.net. WhatsApp Web uses ports 443 (HTTPS) and 5222 for its WebSocket connections. Some enterprise networks block WebSocket upgrades on port 443 as a matter of policy, so specific domain whitelisting is what's needed — not just unblocking a port.
If you haven't done this already and you're not sure which section applies to you: on your phone, open WhatsApp, leave it open on-screen, and then reload WhatsApp Web in your browser. Don't lock your phone or switch apps on it — keep WhatsApp visibly open. If the session connects now but drops when you lock the phone, you have confirmed the battery optimization issue from Section 3 and can go fix that specifically.
This one test eliminates about 60% of the cases I see, because most people troubleshoot the browser while the actual problem is sitting in their phone's power settings.
If you're using WhatsApp Web daily for work and you keep running into these issues, the desktop app is genuinely better. It maintains a more stable WebSocket connection, doesn't get throttled like a browser tab, and works with multi-device mode. Download it from whatsapp.com/download — it's available for Windows and macOS. Setup is the same: scan the QR code from your phone's Linked Devices menu, and you're done. You won't need to re-scan every time unless you're inactive for 14 days.
Why does WhatsApp Web say "Phone not connected" even though my phone has internet?
The most common cause is that WhatsApp on your phone was killed by the OS — either through battery optimization on Android or Low Power Mode on iPhone. The app needs to be running in the background to maintain the bridge. Open WhatsApp on your phone and leave it open, then check if the web session reconnects within 30 seconds.
WhatsApp Web QR code keeps spinning and never loads — what's blocking it?
A QR code that spins indefinitely almost always means a browser extension is interfering. Ad blockers and privacy tools like uBlock Origin or Privacy Badger commonly block WhatsApp's WebSocket connections. Test in an incognito window first — extensions are disabled there by default. If it loads in incognito, the issue is a browser extension.
Can I use WhatsApp Web without my phone nearby?
Yes, if your account has multi-device mode enabled. Once linked, WhatsApp Web operates independently for up to 14 days before the session needs your phone online to refresh. To check: open WhatsApp on your phone, go to Settings > Linked Devices — multi-device shows your browser session without requiring the phone to be active.
I scanned the QR code successfully but it just resets and asks me to scan again — why?
This usually means you've hit the 4-device limit, or your phone's clock is out of sync. Check Linked Devices and remove old sessions first. Then verify your phone's date and time is set to automatic. A clock that's off by even a few minutes causes the QR authentication to silently fail.
WhatsApp Web works fine for a few minutes then disconnects — what's happening?
Short sessions that cut off after a few minutes almost always point to Android battery optimization killing the WhatsApp background process on your phone. Go to Settings > Battery > Battery Optimization, find WhatsApp, and set it to "Not optimized." On Samsung, also check the Sleeping apps list under Device Care > Battery and remove WhatsApp from it.
WhatsApp Web is blocked at work — how do I use it?
Corporate networks block the WebSocket connections WhatsApp Web uses. Use your phone's mobile hotspot to bypass the office Wi-Fi, or try the WhatsApp Desktop app which sometimes uses a different path. Ask IT to whitelist web.whatsapp.com and *.whatsapp.net if you need it for legitimate work purposes.