Fix Your Apps. Keep Going.

Chrome Shows "No Internet" Despite WiFi? 6 Fixes (2026)

October 15, 2026

Here's a weird one: your Wi-Fi icon shows full bars. YouTube plays. WhatsApp sends. Then you open Chrome and every page says "No internet" — sometimes with the ERR_INTERNET_DISCONNECTED error for good measure. If Chrome shows no internet despite WiFi while everything else works, stop blaming your router. Your network is fine. Chrome itself is broken — it runs its own private network stack, and that stack can jam while the rest of the phone hums along. Six fixes, from a 30-second restart to a full reset.

Chrome shows no internet despite WiFi on Android - phone displaying the No internet error in Google Chrome

Quick Answer: Chrome dead on WiFi while other apps work? Force stop Chrome first — Settings → Apps → Chrome → Force stop — then reopen it. Still offline? Clear its cache (Settings → Apps → Chrome → Storage → Clear cache), switch off Use secure DNS in Chrome → Settings → Privacy and security, disconnect any VPN, and confirm date & time are automatic. A wrong clock silently kills every secure connection Chrome makes.

Why Chrome Loses the Internet Alone

Most apps hand their networking to Android and share one connection. Chrome doesn't — it keeps its own DNS settings, its own proxy handling, its own cached connection data. That's why it can go dark solo. The usual ways it breaks:

  • A stuck process — a crashed network thread keeps reporting "no connection" long after the network recovered.
  • Corrupted cache — stale files that confuse Chrome's connection checks.
  • Chrome's Secure DNS — Chrome can override your phone's DNS with its own provider. Provider unreachable? Every page fails.
  • A middleman failing — VPN, proxy, or Data Saver rerouting traffic through something that's down.
  • A wrong clock — HTTPS certificates are time-bound. Off by hours, and Chrome rejects every secure page. Looks exactly like dead internet.

Fastest triage: if it broke right after you toggled a VPN or changed a Chrome setting, jump to Fix 5. If it broke out of nowhere, start at Fix 1 — stuck processes are the most common cause.

Fix 1: Force Stop and Restart Chrome

Swiping Chrome away doesn't fully kill it. A hung network thread survives in the background, still insisting there's no connection. Force stop actually ends it.

  1. Open Settings → Apps. Pixel: tap See all apps. Xiaomi (HyperOS): Apps → Manage apps.
  2. Tap Chrome.
  3. Tap Force stop, confirm.
  4. Open Recent apps and swipe Chrome away too — belt and suspenders.
  5. Reopen Chrome and load a page.

Pages loading? That was it — a stuck process, thirty seconds, done. Still "No internet"? The corruption is deeper. Fix 2.

Fix 2: Clear Chrome's App Cache

Chrome's app cache holds temporary files Android manages — and when they corrupt, Chrome can misjudge the network entirely. Clearing it is safe: tabs, history, and logins stay put.

Clear Chrome app cache on Android to fix Chrome no internet despite WiFi - Settings Apps Chrome Storage screen

  1. Go to Settings → Apps → Chrome (same place as Fix 1).
  2. Tap Storage (Samsung, Xiaomi) or Storage & cache (Pixel).
  3. Tap Clear cache — the cache button, not "Clear storage." That's the nuclear option, saved for Fix 6.
  4. Reopen Chrome and test.

Low on space? Chrome misbehaves with under ~1–2 GB free — check Settings → Storage.

Fix 3: Clear Browsing Data Inside Chrome

Fix 2 cleared Android's side. But Chrome keeps a second, private stash — cookies and site data inside its own profile — that Android's cache clear never touches. If the corruption lives there, you have to evict it from inside Chrome.

  1. In Chrome, tap the ⋮ three-dot menu (top right) → Settings → Privacy and security → Clear browsing data.
  2. Set Time range to All time.
  3. Tick Cached images and files and Cookies and site data.
  4. Tap Clear data, confirm, restart Chrome, test.

Heads-up: this signs you out of websites, so expect to log back in. If only one site fails, don't nuke everything — open that site, tap the tune/lock icon in the address bar → Cookies and site data → Delete. Surgical beats scorched-earth.

Fix 4: Set Date & Time to Automatic

This one surprises people. Nearly every site uses HTTPS, and HTTPS certificates only work inside a valid time window. Phone clock wrong — after a drained battery, a manual tweak, a timezone hiccup — and Chrome rejects every secure connection. Other apps may shrug it off; Chrome treats it as no internet. Classic symptom, five-second fix.

  1. Pixel / stock Android: Settings → System → Date & time.
  2. Samsung (One UI): Settings → General management → Date and time.
  3. Xiaomi (HyperOS): Settings → Additional settings → Date & time.
  4. Switch Automatic date & time (a.k.a. "Use network-provided time") ON — plus Automatic time zone.
  5. Reload a page in Chrome.

Already on? Flip it off, set the time by hand, flip it back on. Forces a fresh sync with the network clock.

Fix 5: Turn Off VPN, Proxy, Secure DNS, and Data Saver

Anything that reroutes Chrome's traffic through a middleman — VPN, proxy, custom DNS, Data Saver — becomes a single point of failure. Middleman stumbles, Chrome goes dark, everything else keeps working. Disable them one at a time and test after each, so you know which one did it.

Turn off secure DNS and VPN in Chrome settings to fix Chrome no internet despite WiFi on Android

A) Disconnect the VPN:

  1. Pixel: Settings → Network & internet → VPN. Samsung: Settings → Connections → More connection settings → VPN. Xiaomi: open Settings and search "VPN" in the search bar — the menu moves between HyperOS versions, search finds it instantly.
  2. Disconnect any active VPN. Also pause ad-blockers and security apps (AdGuard, Blokada, antivirus suites) — many run a local VPN you'd never notice.

B) Kill any proxy on your Wi-Fi network:

  1. Pixel: Settings → Network & internet → Internet → tap your network → edit (pencil) → Advanced → Proxy → None. Samsung: Settings → Connections → Wi-Fi → long-press your network → Manage network settings → Proxy → None.
  2. A leftover manual proxy from some long-forgotten setup is a frequent culprit here.

C) Toggle Chrome's Secure DNS:

  1. In Chrome: ⋮ → Settings → Privacy and security → Use secure DNS.
  2. Turn it OFF and test. Pages load? Chrome's custom DNS provider was the problem. You can switch it to Automatic afterward if you'd rather keep the feature.

D) Check Android's Data Saver:

  1. Note: Chrome's own Data Saver / Lite mode no longer exists — Google removed it back in Chrome 100 (2022). The one that matters now is Android's system Data Saver, which throttles background data and can starve Chrome.
  2. Pixel: Settings → Network & internet → Data Saver → turn it Off while testing. Samsung: Settings → Connections → Data usage → Data saver → Off.
  3. If you need Data Saver on for your plan, add Chrome to its unrestricted apps list instead.

Fix 6: Reset Chrome Completely

Nothing targeted worked — time for the deep clean. Wiping Chrome's data rebuilds its entire profile from zero: every cached file, cookie, setting, and flag override that could be breaking its connection, gone.

  1. Safety first: open Chrome → ⋮ → Settings → Sync and confirm your Google account is syncing bookmarks and passwords. A wipe without sync can strand locally-stored logins.
  2. Go to Settings → Apps → Chrome → Storage (Storage & cache on Pixel).
  3. Tap Clear storage ("Clear data" on some brands), confirm.
  4. Reopen Chrome, sign back into Google, test.

One alternative first, if the trouble started right after a Chrome update: roll the update back. Settings → Apps → Chrome → ⋮ menu → Uninstall updates restores the factory version; then grab the latest fresh from the Play Store. A bad build is rare, but it happens.

What If Nothing Works?

  • Update Chrome from the Play Store — networking bugs get patched, and you might be sitting on the buggy build.
  • Test on mobile data. Chrome works on data but not Wi-Fi? Then it's your network's config (proxy, DNS, captive portal) — not Chrome. Our WiFi guide in Related Guides covers that side.
  • Try another browser. Firefox or Samsung Internet loading fine on the same Wi-Fi proves it's Chrome-specific.
  • Restart the phone. Clears stuck system networking services that no app-level fix can reach.
  • Forget and rejoin the Wi-Fi: Settings → Network & internet → Internet → your network → Forget → reconnect.
  • Flush Chrome's DNS cache: type chrome://net-internals/#dns in the address bar → Clear host cache. (On very new Chrome builds this internal page may not open — skip it if so.)
  • Factory reset, last resort — back up first.

Watch: WiFi Connected But No Internet Fixed Step by Step

Prefer a walkthrough? This video covers the 'WiFi connected but no internet' problem step by step:

Video by GlitchGuru — full credit to the creator.

Frequently Asked Questions

Why does Chrome say "No internet" when my other apps work fine?

Chrome keeps its own network stack — separate DNS settings, proxy handling, and cached connection data. A stuck process, a dead Secure DNS provider, an active VPN or proxy, or a wrong system clock can each knock Chrome offline independently while the rest of the phone stays connected.

Will clearing Chrome's data delete my bookmarks and passwords?

Not if sync is on — they live in your Google account and come back when you sign in again. Clearing just the cache (Fix 2) never touches them at all. Only a full data wipe (Fix 6) removes locally-stored items, which is why the sync check comes first.

How is this different from "WiFi connected but no internet"?

Different problem, different fix. "WiFi connected but no internet" means nothing can reach the web — router, DNS, or ISP trouble. Chrome-only failure means the network is fine and the breakage is inside Chrome. Every app offline? See the WiFi guide linked above instead.

By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026