Chrome profiles not working: what to check, in order

When pages load in one Chrome profile but not in another on the same Mac, the network is almost never the cause. The other profile proves the connection, DNS and Chrome itself work. What differs between profiles is everything stored inside them: extensions, a proxy or VPN set by an extension, cookies and site data, settings changed by another program, and policies from a work or school account. So the fastest route is to rule those out one at a time, from the least destructive check to the most, and only build a new profile at the end.

The order below follows that logic. Each step names the exact menu items Chrome uses today, checked against Google's Chrome help pages on October 18, 2026. Most people find the cause by step 3.

Step 1: Confirm the problem really belongs to the profile

Before changing anything, take two minutes to prove the fault is inside the profile and not in Chrome or the Mac.

1. Open the same page in another profile you already have. If it loads there, the problem is profile-specific.
2. Open it in Guest mode. Select Profile at the top right, then Open Guest profile. Google's Guest mode help page explains that in Guest mode you cannot see or change any other profile's information, and that browsing activity is deleted when you exit. That makes it a clean, empty profile.
3. Open it in an Incognito window from the broken profile (Command-Shift-N).

How to read the results:

Result	What it points to
Fails in every profile and in Guest	Not a profile problem. Follow Google's general steps for connection errors.
Works in Guest, fails in the broken profile	Something stored in that profile. Continue with step 2.
Works in Incognito from the broken profile	Most likely an extension or stored site data. Steps 2 and 3.
Fails in Incognito from the broken profile too	Possibly an extension allowed in Incognito, a proxy, or a policy. Steps 2 and 4.

Incognito is a useful test because Chrome's extensions help page treats it separately: an extension runs there only if you turn on "Allow in incognito" in its Details page. Google's own connection and loading errors guide makes the same point: if the issue is fixed in Incognito, the next steps are to disable extensions or delete browsing data.

Read the error message before changing anything

The text Chrome shows on the failed page narrows the search a lot, and it is worth noting before step 2. Google's common error messages page explains the main codes. A few of them point straight at something inside one profile:

Error shown	What Google says it means	Profile-related cause to check
ERR_CONNECTION_RESET	Something interrupted the connection, such as a VPN issue or security software that blocks the page	A VPN or proxy extension in this profile
ERR_CONNECTION_REFUSED	The page did not let Chrome connect, or the page is blocked	A blocking extension, or a policy from a work account
ERR_NAME_NOT_RESOLVED	The web address does not exist or has a new IP address	Rarely profile-specific; check the address first
NET::ERR_CERT_AUTHORITY_INVALID	On work computers, often a missing certificate for an HTTPS-inspecting proxy	Ask the administrator; Google advises against installing certificates yourself

If the page shows no error at all and simply stays blank or half drawn, that usually points to scripts being blocked, which brings you back to extensions. The full list of codes is available by typing chrome://network-errors/ in the address bar.

Step 2: Extensions, especially anything that touches the network

Extensions are the most common reason one profile breaks and another does not, because extensions are installed per profile.

To check, open More (the three dots) at the top right, then Extensions, then Manage extensions. Turn every extension off, reload the failing page, and see whether it loads. Google recommends exactly this: disable all extensions, and if that solves it, turn them back on one at a time to find the one responsible.

Pay particular attention to:

• VPN and proxy extensions. Google's extensions help page notes that extensions which change lower-level network access through VPNs or proxy settings are not limited by the usual site permissions. A VPN extension that has lost its connection can stop every page in that profile from loading while other profiles are unaffected.
• Ad and content blockers. An overly broad filter list can block the scripts a site needs, so the page loads blank or half drawn.
• Privacy and security extensions that rewrite requests or block cookies.

If one extension is the cause, you can keep it but narrow it. On the extension's Details page, under Permissions, you can choose whether it runs only when you click it, on specific sites, or on all sites.

A related case: if Chrome says an extension is corrupted, Manage extensions shows a Repair button for it. Google adds that if a repaired extension becomes corrupted again, another program may be changing its files, and suggests running anti-malware software.

Step 3: Site data and cookies for the failing sites

If extensions are not the cause, the next suspect is stored data for the site itself: a stale cookie, a broken cached file, or a login state the site no longer accepts. This is especially likely when only one or two sites fail rather than everything.

Start narrow, with just the failing site. Google's cookies help page gives the path: More, Settings, Privacy and security, Third-party cookies, then See all site data and permissions. Search for the website's name at the top right, select Delete next to it, and confirm with Delete.

If several sites are affected, clear more broadly. Type "Delete browsing data" in the address bar and select the action that appears, or go through Settings. Clearing cookies signs you out of sites that remember you, and may remove saved preferences on those sites, so do it in the broken profile only.

Signs that it is site data, not Chrome

• One site fails, every other site in the same profile is fine.
• The site loads in Guest mode but loops on its sign-in page in your profile.
• The problem started right after you signed in to a second account of the same service in that profile.

The last one is common with Google, Microsoft and Slack accounts. A profile holds one cookie store, so several accounts of the same service compete for it.

Step 4: Whether the profile is managed, or settings were changed

Profiles signed in with a work or school account can receive policies from the organisation, and those policies can block sites, force a proxy or install extensions you cannot remove. This explains many cases where only the work profile fails.

Google's page on checking whether Chrome is managed gives three checks:

1. Open More and look at the bottom of the menu. If it says "Managed by your organization", the browser is managed.
2. Enter chrome://management in the address bar to see extensions managed by the organisation.
3. Enter chrome://policy to see the policies that are set.

If the profile belongs to an employer or school and a policy is blocking a site, the fix is with their IT team, not in Chrome settings. If the Mac is personal and you do not expect any management, Google's page suggests checking which account the profile is signed in with: a custom domain such as @company.com means a managed account.

Programs installed on the Mac can also change Chrome's settings without asking. Google's reset settings page notes that Chrome checks for this on every launch and may reset the default search engine, homepage, startup pages, pinned tabs and extensions automatically if something looks wrong.

Step 5: Reset the profile's settings

If the profile still fails, reset its settings. Go to More, Settings, Reset settings, then "Restore settings to their original defaults", and confirm Reset settings.

Know what this does before clicking. According to Google's reset page:

• It changes: default search engine, homepage and startup tabs, the new tab page, pinned tabs, content settings (such as pop-ups or microphone permissions), cookies and site data, and extensions and themes.
• It keeps: saved bookmarks and passwords.
• It does not fully reset: some settings, such as fonts and accessibility, are left alone.
• It applies everywhere the profile syncs. The reset changes these settings on all devices where you are signed in with that profile.

The last point surprises people. If the broken profile syncs to a second computer, that computer's settings for the profile are reset too.

Step 6: Move to a fresh profile

When nothing above helps, the profile's stored data is likely damaged in a way settings cannot reach. Google's reset page says so directly: the reset is not a full reset, and to start from scratch you add a new profile.

Do it in this order so nothing is lost:

1. Create the new profile first. Select your profile picture at the top right, then Add Chrome profile. Google's multiple profiles help page explains that if you sign in with your Google Account, bookmarks, passwords and settings saved to that account come back.
2. Test the failing pages in the new profile before installing any extensions.
3. Add extensions back one at a time, checking the failing site after each.
4. Only then remove the old profile. Select your profile picture, open Manage Chrome profiles under "Other Chrome profiles", choose the old profile, select More, then Delete, and confirm. Google warns that removing a profile erases its bookmarks, history, passwords and other settings from the computer, so make sure anything not synced is exported first.

When the fix keeps coming undone

If the same profile breaks again within days, look at what that profile is being asked to do. A common pattern is one profile holding many web apps with several accounts each: two Google accounts, a client's Slack, a second Microsoft login. Every one of those shares the profile's single cookie store, and every one brings its own extensions and sign-in quirks. The usual Chrome answer is one profile per account, which works but multiplies windows and Dock icons.

Another approach is to move the always-open web apps out of the browser profile entirely, into an app aggregation browser where each web app has its own isolated container and sign-in. The workspaces page explains how that separation works, and the comparison with other tools shows how different products handle multiple accounts.

What to change first

Run the Guest mode test, then turn off all extensions in the broken profile; between them they settle most cases in minutes. If the trouble is really several accounts colliding in one profile, keeping those web apps in separate containers in SpaceDeck stops the collisions from coming back.