Chrome delete profile extension: what each step erases

A second Chrome profile was set up for a work account, an extension went into it, and now something has to go. The search that follows usually mixes the words delete, profile and extension, because the browser does not make it obvious which of the three is the thing to remove. They sit in different screens, they are worded almost identically, and each one destroys a different amount of data.

That difference is the whole problem. One of these actions is a two second reversal. Another wipes a folder that can be several gigabytes and cannot be undone from inside the browser. Knowing which is which before clicking is worth more than any cleanup guide written afterwards.

Three different jobs are hiding behind one phrase

The phrase gets typed by people in at least three unrelated situations, and the correct answer is different for each.

The first is straightforward removal. An extension was installed in one profile, it is no longer wanted there, and the question is whether removing it affects the other profiles that also have it. It does not, and the reason is worth understanding rather than just trusting.

The second is collateral. A profile is being deleted, usually because a project ended or an account was closed, and the concern is what happens to the extensions and their stored settings when the profile goes. Chrome's own warning about profile removal lists bookmarks, history and passwords, and stops there, which leaves the extension question unanswered.

The third is the frustrating one. An extension shows a greyed out Remove button, or it comes back after being removed. That is not a bug in the browser, and no amount of clicking Remove will fix it, because the instruction to keep the extension is arriving from somewhere outside the profile.

Where a Chrome extension actually lives on a Mac

A Chrome profile is a folder, not a record in a database. On macOS the profiles sit under ~/Library/Application Support/Google/Chrome. The first one is a folder named Default, and every profile added afterwards gets a folder named Profile 1, Profile 2 and so on, numbered in creation order rather than by the name shown in the browser.

Open one of those folders and the extension machinery is immediately visible. There is an Extensions directory holding the unpacked code of each installed extension, keyed by its 32 character ID. Alongside it sit Local Extension Settings, Extension State, Extension Rules, Extension Scripts and Extension Cookies, which between them hold everything an extension has saved. The list of what is installed and enabled is recorded in the Preferences and Secure Preferences files in the same folder.

Nothing about an extension is stored above the profile level. One directory up, at the root of the Chrome folder, a file named Local State holds the list of profiles, their display names, their avatars and their ordering. It knows which folders exist. It knows nothing about what is installed inside them.

The practical consequence is that an extension installed in five profiles is five separate copies on disk, with five separate storage areas and five separate background service workers when those profiles are open at once. This is why memory use climbs with the number of open profiles rather than with the number of extensions, and why removing an extension from one profile leaves the other four untouched.

Removing one extension from one profile

Open the profile in question, go to chrome://extensions, find the card and select Remove. The faster route is a right click on the extension's toolbar icon, which offers the same action. Both affect only the profile currently in front of you.

Two details cause avoidable mistakes here. The first is that the toggle switch on the extension card is not removal. Turning an extension off stops it running but keeps its code and its stored data in the profile, which is the correct choice when the goal is to test whether an extension is causing a problem. Only Remove deletes the folder and the settings.

The second is confirming which profile is actually open. With several profiles on one machine and identical toolbars, removing an extension from the wrong one is easy and is only noticed later. The avatar at the top right names the current profile, and the profile list under it shows what else is running.

Removal is genuinely local, but it is not silent. If the profile is signed in with sync switched on, uninstalling an extension is an event that travels to the account, and the same extension will disappear from other devices signed into that account. That is usually what people want. It is occasionally a surprise.

When Remove is greyed out or the extension keeps coming back

An extension whose Remove button cannot be clicked was installed by policy, not by a person. This happens on managed machines through the Chrome Enterprise policy that force installs a list of extensions, and it also happens on personal machines when a desktop application installs a companion extension.

Chrome Web Store help is explicit about the managed case.

If you're using a computer through your work or school, your organization might block some extensions. Source: support.google.com

To find out which applies, open chrome://policy and look at the extension policies listed there. On a Mac, policies delivered by an employer or a device management tool arrive as configuration profiles, which is why they survive reinstalling the browser and cannot be reversed from inside it. If the entry is there, the fix is a conversation with whoever manages the device, not another attempt at the Remove button.

The other reason for reappearance is different and much more common on personal machines. Deleting a profile locally is not the same event as uninstalling an extension. When a new profile is later created and signed into the same Google Account, the extension list stored in that account is applied to it, and everything that was in the deleted profile comes back. The extension was never uninstalled. The container holding it was thrown away, and a new container inherited the account's inventory.

What deleting an entire profile erases

Chrome's own wording on profile removal is short and worth reading before clicking.

Important: After you remove a profile from Chrome, the profile's bookmarks, history, passwords, and other settings are erased from the computer. Source: support.google.com

Extensions are not named in that sentence, but they are inside the folder being erased, so they go with it, along with their stored data, their cookies and their local settings. The phrase that carries the weight is "from the computer". Anything that had been saved into the Google Account is still in the account, and only local copies are being destroyed.

That is the useful mental model. Deleting a profile is a local operation with a global blind spot. It removes the folder and its entry in Local State, and it says nothing to the account about whether that data was still wanted.

Action	What it removes	What survives
Toggle an extension off	Nothing. The extension stops running	Code, settings, stored data, the other profiles
Remove an extension	The extension folder and its data in this profile	The same extension in other profiles, until sync catches up
Sign out of the profile	The account copy of synced data from this device	The account itself, the profile folder, local files
Delete the profile	The whole folder, extensions included, unrecoverable from the browser	Everything already saved in the Google Account

Read down the rows and the safe order becomes obvious. Removing an extension is cheap and specific. Deleting a profile is neither, and doing it to solve an extension problem is like moving house to fix a broken tap.

A safe order for retiring a profile you no longer need

When the profile really is going, the sequence below costs a few minutes and removes almost every way this goes wrong. It is written for the common case of a work profile being decommissioned after a contract ends.

Start by opening the profile and taking stock of what only exists there. Bookmarks are the usual casualty, and they export to an HTML file from the bookmark manager in three clicks. Saved passwords export from the password settings, and it is worth knowing that the exported file is plain text, so it belongs in a password manager and then in the trash rather than in Downloads. Anything an extension stored locally, such as a clipboard history or a note taking sidebar, generally has its own export in the extension's own options page, and none of it is covered by Chrome's export tools.

Next, decide whether the Google Account is also going away. If it is not, sign out of the profile before deleting it and check what the account still holds at the Chrome data dashboard. Signing out first separates two questions that are otherwise answered at the same moment: what leaves this Mac, and what leaves the account. Deleting the profile without signing out answers only the first, which is exactly how a new profile ends up re-inheriting the same extensions weeks later.

Finally, delete the profile from the profile manager rather than by dragging the folder to the trash. Chrome keeps the profile list in Local State, and deleting a folder by hand leaves an entry pointing at a folder that no longer exists. That mismatch produces profile errors at the next launch, and cleaning it up afterwards is more work than doing the removal in the browser in the first place.

When the profile itself is the wrong unit

There is a pattern worth naming, because it produces the same search every few months. Profiles get created to separate accounts, extensions get installed into each one, notifications and sessions drift out of alignment, and eventually a profile gets deleted to clean up. Then a new one gets created for the same purpose and the cycle restarts.

What is actually being asked for in that loop is a per application boundary, not a per account browser copy. A profile bundles identity, cookies, extensions, history and window state into one object, so anything that needs one of those separated drags the other four along with it. That is why a browser designed around Workspaces treats the boundary as a property of the work rather than of the sign in, and why a tool that keeps each web app in its own window can put two accounts of the same service side by side without a second copy of every extension. The list of what such a setup covers is on the Features page, and the services it has been built to handle are listed under Supported apps.

None of that removes the need to know what Chrome's delete button does. It changes how often the question comes up.

What to change first

Before deleting anything, open chrome://policy and check whether the extension in question is force installed, because that single check tells you whether the rest of the work is even possible. If the answer is no, remove the extension from the one profile that needs it gone and leave the profile alone. If profiles are being created and destroyed just to keep accounts apart, the boundary is in the wrong place, and SpaceDeck is built around moving it.