Resetting Chrome settings is a troubleshooting move, not a routine maintenance task. It makes sense when Chrome has started behaving strangely — a search engine that changed itself, a new tab page you didn’t set, extensions acting oddly, pages breaking in ways they shouldn’t — and the cause isn’t obvious. The reset addresses all of these by returning browser configuration to its post-install state, without touching the data you actually care about. This fits into the wider topic we cover in our How to Manage Google Chrome.
The key thing people want to know upfront: bookmarks, passwords, and browsing history are not deleted by a settings reset. These are stored separately from browser configuration and survive the reset untouched. What changes is the configuration layer — search engine, startup behaviour, theme, site permissions, pinned tabs, and content settings all return to defaults.
How to run the reset
chrome://settings/reset → “Restore settings to their original defaults” → a dialog lists exactly what will be changed → click “Reset settings.” The whole operation takes about 10 seconds. Chrome restarts with default settings.
Alternatively: chrome://settings → scroll to the bottom → “Reset settings” section. The button text differs between Chrome versions but leads to the same place.
Before you reset — what to note down
Since certain settings return to defaults, it’s worth taking a mental note of any you customised before the reset:
- Which search engine you use (it resets to Google)
- Startup page configuration (resets to “Open new tab”)
- Extensions you have installed — they stay installed but get disabled; you’ll re-enable them manually
- Any unusual content settings (specific sites you gave notifications or camera access — these are cleared)
Bookmarks, passwords, and history don’t need backing up before a settings reset — they survive it. If you want to be extra cautious: export bookmarks first (Bookmarks Manager → three dots → Export bookmarks) and export passwords (chrome://settings/passwords → three dots → Export passwords). But for a standard settings reset, this isn’t necessary.
What the reset actually changes
| Data type | Reset affects it? |
| Bookmarks | No — fully preserved |
| Saved passwords | No — fully preserved |
| Browsing history | No — fully preserved |
| Default search engine | Yes — returns to Google |
| Startup page | Yes — returns to “Open New Tab” |
| Pinned tabs | Yes — cleared |
| Extensions | Disabled (not deleted) |
| Site permissions (notifications, location, etc.) | Yes — all cleared |
| Content settings | Yes — returns to defaults |
| Theme | Yes — returns to default |
| Chrome flags | Yes — all returned to default |
After the reset — re-enabling extensions carefully
After a settings reset: go to chrome://extensions and re-enable extensions one at a time rather than all at once. If Chrome was behaving oddly before the reset, an extension was likely part of the cause. Re-enabling one by one — and testing Chrome’s behaviour after each — identifies which extension was the problem. Re-enabling everything simultaneously just brings the problem back without identifying it.
This extension-auditing approach turns the reset into a diagnostic opportunity, not just a fix. By the time you’ve re-enabled the extensions you actually use, you’ve also identified and excluded the one causing trouble.
When a reset isn’t enough
Settings reset fixes configuration problems. It doesn’t fix a corrupted Chrome profile (profile corruption causes Chrome to crash at launch or behave erratically in ways that survive resets) or a corrupted Chrome installation (corrupted application files cause Chrome not to open or to behave in ways that no configuration change can address).
If the reset doesn’t help: the next step is a profile reset. Navigate to %localappdata%GoogleChromeUser Data → rename the “Default” folder to “Default.bak” → launch Chrome. A fresh profile is created. If Chrome works correctly with the new profile: the old profile data was corrupted. Sign into Chrome to restore your Google account data from sync.
Our guide on Chrome crash troubleshooting covers the profile and installation corruption paths, and our Chrome profiles guide covers how profiles work and when creating a new one is the right approach. For Chrome’s reset and cleanup tools in more technical detail, Google’s Chrome Help documents the full reset options including the Clean Up Computer tool that accompanies the settings reset.
The malware cleanup tool
chrome://settings/cleanup (on Windows) runs Chrome’s built-in software cleanup tool alongside the settings reset. This is useful when Chrome’s settings were changed by external software — adware, browser hijackers, or unwanted programs that modified the search engine, added extensions, or changed startup pages. The cleanup tool detects and removes this software; the settings reset then restores the configuration it changed.
Doing just the settings reset without running the cleanup tool is less effective when PUPs (potentially unwanted programs) are involved — the settings may revert to the hijacked state after the next browser launch if the software hasn’t been removed. Run cleanup first, reset settings second. That sequence addresses both the cause and the symptoms.
Settings reset and Chrome Sync
A less-known behaviour: if Chrome Sync is active when you reset, the synced settings from your Google account may re-apply shortly after the reset. Chrome treats the cloud copy of settings as authoritative and downloads them after reconnecting. If the problematic settings (like a hijacked search engine that also got synced) are in your account’s sync data: the reset appears to have done nothing because Sync is restoring the old settings.
Fix: before resetting, pause sync (chrome://settings/syncAndGoogleServices → Turn off sync) → reset settings → re-enable sync. After sync reconnects, Chrome re-downloads account settings. If the problematic setting was synced: it will come back again. To clear synced settings: myaccount.google.com → Data & Privacy → Google Chrome → Reset sync (this deletes the Chrome-specific cloud data; your bookmarks and passwords are separate and not deleted by sync reset).
What a reset doesn’t fix
Worth knowing before relying on a reset as the solution to everything: it doesn’t clear Chrome’s cache or cookies (those require Ctrl+Shift+Delete), doesn’t remove extensions (they stay installed, just disabled), doesn’t fix a broken Chrome installation (needs a reinstall), and doesn’t address system-level issues like RAM problems or antivirus conflicts that affect Chrome’s stability.
Think of the settings reset as a configuration flush. It’s effective specifically when configuration drift — settings that changed over time, usually through extensions or software — is the cause of the problem. For anything that survived extension disabling and configuration changes, the problem is below the settings layer and needs a different approach.
The reset is one of Chrome’s most useful troubleshooting tools precisely because it’s targeted (only settings, not data), fast (10 seconds), reversible in spirit (you can reconfigure what was reset), and effective for the specific class of problems it addresses. Knowing its exact scope — what it does and doesn’t touch — makes it easy to decide when it’s the right tool.
Resetting specific settings without a full reset
Sometimes you only need to change one specific setting back to default rather than resetting everything. Chrome’s settings pages often show the current state and let you change individual settings without the full reset. For example:
- Search engine: chrome://settings/searchEngines → set search engine used in address bar
- Site permissions: chrome://settings/content → click any permission type → “Reset permissions” for that type only
- Chrome flags: chrome://flags → “Reset all” → resets only experimental flags
- Extensions: chrome://extensions → disable individual extensions without resetting everything else
If the only problem is a changed search engine or a specific permission that’s wrong: a targeted fix is faster and less disruptive than a full settings reset. The full reset is the right choice when you’re not sure which setting is wrong and want a reliable clean baseline, or when multiple settings appear to have changed and individual fixes would take longer than starting fresh.
Settings reset on managed Chrome
On Chrome managed by an organisation: the settings reset works on user-controlled settings, but policy-managed settings are re-applied after the reset. If IT has configured specific settings via Google Admin Console or Group Policy: those settings return immediately after the reset through the policy mechanism. This is expected behaviour — the reset clears user-level settings, and policies then re-apply at the policy level.
If you’re trying to troubleshoot a problem on a managed Chrome and the reset doesn’t help: check chrome://policy for what’s policy-controlled. Settings shown there are outside the scope of a user-level reset and require an IT policy change to modify.
Regular Chrome maintenance vs reset
A settings reset shouldn’t be something you do on a schedule. Chrome doesn’t need periodic resets the way some people reset their phones seasonally. The need for a reset is a signal that something specific went wrong — extensions accumulated problems, external software altered settings, or configuration experimentation produced unexpected side effects.
Preventing the need for resets: periodic extension audits (removing ones you don’t use), being cautious about what you install alongside Chrome (software bundles that include browser hijackers), and not experimenting extensively with chrome://flags unless you’re prepared to reset them. These habits significantly reduce the situations where a settings reset becomes the troubleshooting tool of choice.
Chrome on macOS — the reset experience
The settings reset on macOS works identically to Windows at the Chrome level: chrome://settings/reset → same procedure, same data preserved, same settings cleared. The macOS keychain (where Chrome stores some credential data) is unaffected by the Chrome settings reset — keychain data persists regardless of Chrome’s configuration state.
On macOS, Chrome’s profile data location is ~/Library/Application Support/Google/Chrome rather than %localappdata% on Windows. For a profile reset on macOS: quit Chrome → navigate to that folder → rename the “Default” folder → relaunch Chrome. Same procedure as Windows, different path.
For users who haven’t done a Chrome settings reset before: it’s worth knowing about as a tool even if you don’t need it right now. When the moment comes that Chrome is behaving in ways you can’t explain — search redirecting somewhere unexpected, new tab pages you didn’t configure, extensions installed you don’t recognise — the reset is the most effective quick response available, and knowing it preserves your bookmarks and passwords removes the hesitation about using it.
The Chrome cleanup companion to the reset
Google periodically updates its Safe Browsing database with signatures for software that’s known to hijack Chrome settings. The cleanup tool (chrome://settings/cleanup on Windows) checks against this database. If it finds matches: it lists what it found and asks permission to remove it.
Unlike antivirus tools that scan all files: Chrome’s cleanup tool specifically targets software known to interfere with Chrome — browser helpers, persistent extensions that reinstall themselves after deletion, processes that monitor and revert Chrome settings changes. Running it after a reset and before reconfiguring Chrome ensures you’re not rebuilding on top of software that will undo the reset.
Combined workflow for thorough Chrome restoration: run the cleanup tool → restart Chrome → perform the settings reset → re-enable extensions selectively. This order matters: cleanup removes the cause, reset removes the effects, selective extension re-enable ensures you don’t reintroduce the problem. Following this sequence rather than just resetting gives you a genuinely clean Chrome in cases where external software was involved.
Resetting Chrome on a shared or borrowed computer
A settings reset on a shared computer affects only the Chrome profile that’s active when you run the reset. If the computer has multiple Chrome profiles (one per user), each profile’s settings are separate — resetting the Work profile doesn’t affect the Personal profile’s settings.
For a shared computer where Chrome was being used by multiple people without separate profiles: the settings reset clears everyone’s shared configuration, including their accumulated site permissions and any customisations. This is usually a benefit when shared use caused the configuration drift — a fresh start works better for shared computers than trying to identify which specific change caused the problem.
Going forward after a reset on a shared computer: create separate profiles for each user rather than sharing one. The settings isolation between profiles prevents one user’s browsing habits (accepting notification permissions, changing search engines) from affecting another’s. Our guide on Chrome profiles covers this setup in detail — it’s a 5-minute configuration that permanently solves the shared computer problem. See also Reset Chrome Settings Without Losing Data for a related case.
