Website Only Works in Incognito Mode in Chrome? Here Is Why, and the Fix

When a website only works in Incognito mode in Chrome, it is telling you something useful: the site is fine, and something stored in your normal Chrome window is breaking it. Incognito is a clean start, so it is also the best clue you have.

People ask this on Reddit every month. One October 2026 post on r/chrome describes a site that opens only in Incognito, even after removing both installed extensions. That rules out one cause, but not the most common one. This guide shows the four causes, a two-minute test to tell them apart, and the fix for each, starting with the one that does not sign you out of anything else.

The short answer#

• Incognito skips your stored data: cookies, cache, extensions and accounts.
• Delete only that site's data first. It fixes most cases and keeps every other login.
• Then test extensions and accounts if the problem comes back.
• If Incognito fails too, the problem is the site or your network.

Why does a website only work in Incognito?#

An Incognito window behaves like a new browser that has never seen the site. Based on Google's help pages:

So when a site breaks only in the normal window, the cause is in the left column. In practice it is one of four things:

1. Outdated or broken data for that site. A cookie from an old session, or saved data written by an older version of the site. The site updates, your browser still sends the old data, and the site rejects it. This is the most common cause.
2. An extension. Ad blockers, privacy tools, translators and coupon tools change pages as they load.
3. The wrong account. Chrome or the site signs you in automatically with a personal account when the page needs your work one. This is the classic "SharePoint says access denied unless I use Incognito" case.
4. A stale offline copy. Some web apps install a service worker that keeps serving an old version of the page until it is removed.

How do I tell which cause it is?#

Run these tests in order. Each takes under a minute, and you stop at the first one that fixes the site.

What we reproduced on a Mac#

Tested on a MacBook Pro (M1 Pro), macOS 26.3, Chrome 155.0.8059.85, October 20, 2026.

To see cause 1 happen, we built a tiny test site on the Mac. Signing in saves a session cookie. The site then behaves as if it had been updated, so it rejects that old cookie with an error, the way a real site does after a change to how it handles logins. We loaded it with Chrome:

We used an empty profile because Chrome's headless test mode ignored the Incognito switch. An empty profile starts with no cookies, which is exactly what Incognito gives you. The result matches what people report: the site was never broken. One saved cookie was.

How to fix a site that only works in Incognito#

Close every tab of the site before you start, so it cannot write the bad data back while you clear it.

1. Delete that site's data only#

These are the steps from Google's help page, in current Chrome:

1. Open Settings, then Privacy and security, then Third-party cookies.
2. Click See all site data and permissions.
3. Search for the site's name in the search box at the top right.
4. Click Delete next to the site, then confirm.
5. Open the site again and sign in.

This removes that site's cookies, saved data and offline copies, and nothing else. You stay signed in everywhere else, and saved passwords are not touched. If the site uses several addresses, such as login.example.com and app.example.com, delete each one that appears in the search.

Do not reach for Delete browsing data with All time and every box ticked. It would also fix the site, but it signs you out of every website you use. The difference between the two kinds of stored data is in cache vs cookies, and more ways to clear one site are in clear cache for one site.

If you hit this often, Cleaner, a free Chrome extension we make, does step 1 from the toolbar: open it on the broken site, choose Fix broken page or Sign out & reset, and it clears only that site and shows what it removed.

2. Turn off extensions in your normal window#

If the site still fails after step 1:

1. Paste chrome://extensions into the address bar.
2. Turn every extension off with its switch. You do not need to remove them.
3. Reload the site.
4. If it works, turn extensions back on one at a time, reloading the site after each, until it breaks again. That last one is the cause.

Look first at ad blockers, privacy and script blockers, VPN extensions and shopping tools. When you find the culprit, most let you turn them off for one site, which is better than removing them.

3. Check which account you are signed in with#

If the site says access denied, you do not have permission or shows someone else's data:

1. On the site, open the account menu and look at which email is signed in.
2. Sign out of every account on that site, then sign in again with the right one.
3. If you use work and personal accounts every day, give each its own Chrome profile: click your profile picture, then Add. Each profile keeps its own sign-ins, so they stop fighting.

4. Remove a stale offline copy#

Web apps that work offline can keep serving an old page from a service worker. Deleting the site's data in step 1 normally removes it. If you want to check:

1. Open the site and press F12 (Command+Option+I on a Mac) to open DevTools.
2. Go to Application, then Service workers.
3. Click Unregister next to the site's worker, then reload.

The full DevTools method, including what each box removes, is in clear site data with Chrome DevTools.

5. Try a fresh profile#

If none of this works, open a new Chrome profile with no extensions and no history and load the site there. If it works, something in your main profile is still causing it, and moving to the new profile is a clean way out. If it fails there too, read the next section.

Why does it break again after a day?#

On r/techsupport, one user wrote that clearing cache and cookies fixed a site, but the problem came back a day or two later. That pattern means something keeps rebuilding the bad state:

• An extension that rewrites the page on every visit. Step 2 finds it.
• A second account that signs in automatically. Step 3 fixes it for good.
• The site itself writing a cookie it later rejects. Only the site can fix that, but clearing just that site each time keeps you signed in everywhere else while you wait.

What if the site does not work in Incognito either?#

Then your Chrome data is not the cause. Check, in order:

1. Load the site on your phone using mobile data, not Wi-Fi. If it fails there, the site itself is down or broken.
2. If it works on mobile data, your network, VPN or DNS is blocking it. Try another network.
3. If it fails only in Chrome on every network, see Chrome not loading pages for the deeper fixes.

If the site loads but keeps sending you back to the sign-in page, that is a different problem with its own fix: see website login loop.