Resetting Chrome settings is a troubleshooting step that fixes a surprisingly wide range of problems — Chrome slowing down over time, extensions behaving oddly, search engine changed without you doing it, startup pages altered, or general instability that appeared gradually. The good news: “reset settings” in Chrome doesn’t mean losing your bookmarks, saved passwords, or browsing history. Those are stored in a different place and are untouched by a settings reset. We go deeper on the whole subject in our How to Manage Google Chrome.
What actually gets reset: your default search engine (back to Google), your startup page, new tab page, pinned tabs, content settings, and any tweaks you’ve made to Chrome’s appearance and behaviour settings. Extensions stay installed but get disabled during the reset. You re-enable the ones you want after.
What a settings reset does and doesn’t affect
To be specific about what’s preserved:
- ✓ Bookmarks — fully preserved
- ✓ Saved passwords — fully preserved
- ✓ Browsing history — fully preserved
- ✓ Downloaded files — not browser data, unaffected
- ✓ Autofill data (addresses, payment methods) — preserved
- ✓ Extensions — still installed, just temporarily disabled
What gets reset to defaults:
- ✗ Default search engine → back to Google
- ✗ Startup and new tab page settings
- ✗ Pinned tabs
- ✗ Browser theme → back to default
- ✗ Chrome flags settings → all returned to default
- ✗ Site permissions (notifications, location, camera, microphone) → all cleared
- ✗ Content settings (cookies, JavaScript, pop-ups, etc.)
- ✗ Extension on/off states → all disabled
The site permissions being cleared is worth noting: after a reset, you’ll be prompted again for location, notification, and camera access by sites you previously allowed. This is actually useful as part of the troubleshooting — it exposes which sites had permissions you may have forgotten about.
How to perform the reset
chrome://settings/reset → “Restore settings to their original defaults” → a dialog explains what will be reset → “Reset settings” button. Chrome reloads with default settings. The whole process takes about 10 seconds.
Alternatively: chrome://settings → scroll to the bottom → “Reset settings” section → “Restore settings to their original defaults.”
No restart required. Changes take effect immediately. You’ll notice the browser looks slightly different (default theme, extensions not visible in toolbar) and settings like startup behaviour will have reverted.
After the reset — what to do next
The reset leaves Chrome in a state that needs some post-reset configuration, but the sequence is usually quick:
- Go to chrome://extensions → re-enable the extensions you actually use (skip any that were causing the problem)
- Set your preferred search engine if not Google: chrome://settings/searchEngines
- Configure startup behaviour: chrome://settings → On startup
- Re-grant necessary site permissions as sites prompt you (or proactively: chrome://settings/content)
This takes 5-10 minutes and leaves you with a clean Chrome configuration. If the problem you were troubleshooting is gone after the reset: it was a settings or extension issue. If it persists: the problem is deeper (profile corruption, Chrome installation issue) and different steps are needed.
When a settings reset isn’t enough
If problems persist after resetting settings: consider a profile reset (more thorough) or Chrome reinstall (most thorough, still preserves data through Google account sync).
Profile reset: close Chrome → navigate to %localappdata%GoogleChromeUser Data → rename the “Default” folder to “Default.bak” → reopen Chrome. A fresh profile is created. Your old data is in Default.bak and can be accessed if needed. If Chrome works correctly with the new profile: the original profile was corrupted. Sign into Chrome to restore bookmarks, passwords, and history from your Google account.
Full reinstall (nuclear option): uninstall Chrome from Settings → Apps → reinstall from google.com/chrome. After reinstalling and signing in: Chrome pulls everything back from your Google account. This resolves Chrome installation corruption that a settings or profile reset doesn’t address.
Our guide on Chrome stability troubleshooting covers the crash-specific path when resets don’t solve the problem, and our Chrome data management covers cleaning up data without full resets. For Chrome’s sync recovery and profile data management, Google’s Chrome Help covers account-based data recovery after profile resets.
Settings reset vs Malware Cleanup tool
Chrome includes a built-in cleanup tool that’s separate from the settings reset. chrome://settings/cleanUpComputer → “Find harmful software” (Windows only). This scans for software that has altered Chrome settings — hijacked search engines, altered startup pages, unwanted extensions installed by other software.
If Chrome’s settings were changed by malware or aggressive PUP (potentially unwanted program): the Malware Cleanup tool addresses the cause, while a settings reset addresses the symptoms. For the cleanest resolution: run the cleanup tool first, then reset settings. The cleanup removes the software that’s changing settings; the reset restores what it changed. Without removing the cause, settings may get altered again after reset.
Sync and settings reset — a clarification
If Chrome Sync is enabled when you reset settings: the reset settings state might get overwritten by synced settings from your Google account within minutes. Chrome Sync considers your account’s settings as the authoritative source and may push them back to the local device after a reset.
If this happens: the reset looks ineffective (settings revert after a few minutes). The fix: sign out of Chrome Sync before resetting → perform the reset → sign back in → check whether Sync pushes the old settings back. If it does: your sync data contains the problematic settings. You’d need to clear sync data: myaccount.google.com → Data & Privacy → Google services → Google Chrome → Manage Chrome data → “Reset sync” removes all Chrome-specific sync data from your account, allowing a truly clean settings state to sync back up.
| What’s wrong | Best approach |
| Search engine changed, startup page altered, extensions acting up | Settings reset → run Malware Cleanup too if PUP suspected |
| Chrome slow, notifications and permissions piling up | Settings reset — clears all permissions, gets clean defaults |
| Problems persist after settings reset | Profile reset (rename Default folder) |
| Chrome crashing frequently | Profile reset, then Chrome reinstall if still crashing |
| Settings reverting after reset | Pause Sync before reset, check for sync data conflicts |
A Chrome settings reset is one of the more useful troubleshooting tools available precisely because it’s thorough without being destructive. Your important data (passwords, bookmarks, history) is completely untouched. The settings that get cleared are exactly the settings that accumulate problems over time — permissions, content settings, extension states, search engine changes. It’s a clean slate for browser behaviour while preserving everything you’ve saved. When Chrome has been behaving strangely for a while with no obvious cause: a reset is often the fastest diagnostic and fix combined.
How often should you reset Chrome settings
There’s no maintenance schedule for Chrome resets — they’re troubleshooting actions, not routine maintenance. Reset when Chrome is behaving in ways you can’t otherwise explain after the standard checks (disable extensions, clear cache, check for malware). Chrome should work well without resets for months or years on a well-maintained system.
If you find yourself resetting Chrome frequently (every few weeks): that suggests the underlying cause is recurring rather than being addressed. Common recurring causes: downloading software from untrusted sources that includes PUPs (potentially unwanted programs that modify Chrome), allowing too many extension installations from unofficial sources, or a browser hijacker that’s reinstalling itself after each reset. Addressing the source rather than the symptoms — cleaning up software installation habits, adding an ad blocker that prevents some PUP delivery, being more selective about extensions — reduces the frequency of needing resets.
Chrome settings reset on managed devices
On organisation-managed Chrome: the reset option may be present but policies may repush settings after the reset. In managed environments, Chrome settings are typically controlled through Google Admin Console or Group Policy rather than user-level settings. After a reset, the next policy sync (usually within minutes) re-applies organisation settings.
This means a reset on a managed device may appear to do nothing — settings return to the policy-configured state almost immediately. On managed devices: if settings seem wrong, the issue is likely in the policy configuration rather than local Chrome settings. Contacting IT with specific details is more effective than repeatedly resetting.
Distinguishing settings problems from performance problems
A settings reset helps with behaviour problems (wrong search engine, notifications not working, extensions misbehaving, site permissions acting strange). It doesn’t help with performance problems caused by RAM constraints, a slow internet connection, or heavy content on specific websites. These are different categories of Chrome issue with different solutions.
If Chrome is slow: the relevant tools are Chrome’s Task Manager (Shift+Esc), the Memory Saver feature (chrome://settings → Performance → Memory Saver), and an extension audit — not a settings reset. A reset won’t free RAM or make your internet faster. It will sometimes improve performance indirectly if a problematic extension was consuming resources and the reset disables it — but the targeted fix (auditing extensions and disabling the heavy ones) is more precise.
Backing up before resetting
Since bookmarks and passwords are preserved through a settings reset, backup isn’t strictly necessary for those. But if you’ve customised Chrome’s settings extensively and want to be able to restore them: Chrome doesn’t have a settings export feature. Document any custom configurations (unusual content settings, specific site exceptions you’ve configured) before resetting, so you can re-apply them afterward.
For extensions: go to chrome://extensions and note which ones are installed with their names before resetting. After the reset, they’ll all be disabled (not removed) and you can selectively re-enable them — potentially using the post-reset state to test whether each extension is contributing to the problem before re-enabling it.
The reset function in Chrome is deliberately designed to be safe for everyday users — it would be a troubleshooting liability if it deleted passwords or bookmarks. Trust it to do what it says: restore settings to original defaults without touching your saved data. That design makes it a reliable first resort when Chrome settings have drifted from working state, rather than something to approach with excessive caution.
Recovering specific settings after a reset
Some settings you might want to restore after a reset:
- Search engine: chrome://settings/searchEngines → change “Search engine used in the address bar” back to DuckDuckGo, Bing, or whatever you use
- Startup page: chrome://settings → On startup → restore “Open a specific page” or “Continue where you left off”
- Third-party cookie blocking: chrome://settings/cookies → restore your cookie blocking preference
- Notification blocking: chrome://settings/content/notifications → if you had it set to “Don’t allow”: set it again
- Theme: chrome://settings → Appearance → re-apply your preferred theme
The reset effectively returns Chrome to the “just installed” state for all these settings. Running through the list of things that were different from defaults and resetting them after the reset takes about 5 minutes. From there, re-enabling extensions one at a time (starting with the ones you use most) lets you identify any extension that immediately causes the behaviour you were troubleshooting — if the problem comes back as soon as you enable a specific extension, you’ve found the cause.
This iterative approach — reset, test, re-enable one extension, test, repeat — is the fastest way to isolate extension-caused problems in Chrome. The settings reset makes it possible because it removes extension states without removing the extensions themselves, giving you a clean starting point to test each one independently. Without a reset, trying to isolate a misbehaving extension from among 15 installed ones is much more tedious.
The difference between Chrome sync reset and browser settings reset
There are two different “resets” worth keeping distinct. The one covered in this guide — chrome://settings/reset → Restore settings — is a local device reset that changes Chrome’s local configuration back to defaults. It doesn’t affect what’s in your Google account.
The other type — resetting Chrome Sync data — clears what’s stored in your Google account for Chrome: bookmarks, history, passwords, settings stored in the cloud. This is done from myaccount.google.com → Data & Privacy → Google Chrome → Manage Chrome data → “Reset Sync.” This is more drastic and actually deletes synced data from the cloud. The local device settings reset described throughout this guide does not do this — it only changes local settings, leaving your cloud data untouched. See also Reset Your Router Without Losing Your Settings for a related case.
For most troubleshooting: you want the local settings reset only. The sync reset is only relevant when you suspect the problem is in your cloud-synced data (like problematic settings being pushed from the cloud to every device you sign into). Knowing which reset you’re doing prevents the accidental deletion of cloud-stored data when you only intended to fix local settings. You might also run into How to Reset Chrome Settings Safely.
