How to Turn Off Google AI Mode in Chrome: Settings and Limits

Chrome has started pushing AI deeper into the browser experience—buttons in the address bar, shortcuts in the New Tab Page, and AI-heavy Google results that often bury the classic “ten blue links.”

If you tried disabling AI using chrome://flags, you probably noticed the catch: flags are experimental and can revert after updates. Chrome updates frequently, so the AI UI can come right back.

The more reliable approach is to use Chrome’s enterprise policies—the same controls IT teams use in companies.

This guide shows two things: how to disable the Chrome AI Mode button persistently, and how to reduce AI clutter in Google Search.

What You’ll Do in This Guide?

• Disable the AI Mode button permanently using Windows policy registry keys (instead of temporary flags).
• Optionally disable additional Chrome AI features using policy settings.
• Clean up Google Search (remove or reduce AI Overviews) using safer, reversible methods.
• Verify everything using chrome://policy.

First: Why Chrome Flags Don’t Stick

Chrome flags are meant for testing. Google can rename them, move features around, or reset them after updates. Even if a flag works today, it may stop working tomorrow.

If you want “set it once and forget it,” use policies. Google officially supports policies for managing Chrome features at scale, including newer AI capabilities.

Step 1 — Permanently Disable AI Mode in Chrome (Windows)

On Windows, the most common way to apply Chrome policies locally is via the Registry. You’ll create a policy path used by managed environments:
HKLM\Software\Policies\Google\Chrome.

Important: Editing the registry carries risk. If you’re not comfortable, create a restore point first.

Step-by-step: Create the Policy Keys

1. Close Chrome.
2. Open the Start menu, type regedit, and run Registry Editor.
3. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Policies.
4. If Google doesn’t exist, create it: Right-click Policies → New → Key → name it Google.
5. Inside Google, create another key named Chrome.

Disable the AI Mode Button: AIModeSettings

Google provides an enterprise policy named AIModeSettings that administrators can use to turn off AI Mode. Chrome Enterprise release notes explicitly mention disabling AI Mode using AIModeSettings (and also a broader policy called GenAiDefaultSettings).

1. Right-click the Chrome key → New → DWORD (32-bit) Value.
2. Name it: AIModeSettings.
3. Double-click it and set the value.

Which value should you use?

Google’s enterprise notes indicate that admins can turn off AI Mode using AIModeSettings (value 1), or by using GenAiDefaultSettings (value 2) to disable covered GenAI features more broadly.

In practice, many Windows how-to guides use 2 to force AI Mode off, but the safest approach is: start with what Google documents (value 1 for AI Mode off), and use GenAiDefaultSettings if you want a stronger “default off” stance.

Stronger Option: Disable Covered GenAI Features by Default

If your goal is “turn off AI features across Chrome wherever possible,” Google supports a broader policy called GenAiDefaultSettings, which can disable covered generative AI features by setting the default to “disabled.”

This is especially useful if Google moves buttons around again. Instead of playing whack-a-mole with UI entry points, you’re disabling the default permission for the feature set.

Verify Your Policy Is Active

1. Open Chrome.
2. Go to chrome://policy.
3. Click Reload policies.
4. Confirm you see AIModeSettings and/or GenAiDefaultSettings listed with the values you set.

If you don’t see them: you likely wrote the key to the wrong hive (HKCU vs HKLM), misspelled the value name, or created it under the wrong path.

Step 2 — Disable Chrome’s Local GenAI Model Download (Optional, But Powerful)

Some Chrome AI features can rely on locally downloaded AI components. There is a policy specifically designed to control local foundational model behavior: GenAILocalFoundationalModelSettings.

Security configuration guidance (STIG) and Chrome Enterprise notes both reference this policy as a way to disable the underlying model download.

Step-by-step: Disable Local Model Download

1. In Registry Editor, go to: HKLM\Software\Policies\Google\Chrome.
2. Create a new DWORD (32-bit) Value.
3. Name it: GenAILocalFoundationalModelSettings.
4. Set the value to 1 (disabled).
5. Restart Chrome and verify in chrome://policy.

If you care about performance, disk usage, or simply don’t want Chrome pulling local AI components, this policy is one of the cleanest “stop it at the source” switches available.

Step 3 — Remove AI Overviews in Google Search (Two Practical Options)

Disabling Chrome UI entry points is one thing. Cleaning up Google Search is another. Here are two approaches—one extremely simple, one more customizable.

Option A: Force “Web results only” with &udm=14

Google Search supports a parameter, udm=14, that pushes results toward a cleaner “web results” view. Tech sites have documented this as a reliable way to reduce AI Overviews and extra modules.

You can do this manually by adding &udm=14 to the end of a search URL, or use a lightweight extension that automatically applies it.

Trade-off: it’s a “web-first” mode. If you like blended results (videos, forums, etc.), you may prefer the next option.

Option B: Hide AI modules with a customization extension

If you want to keep some modern result blocks (videos, “People also ask,” etc.) but remove AI Overviews and AI panels, a dedicated extension can do that.

One well-known example is “Bye Bye, Google AI,” widely covered and designed to hide AI elements from results pages.

The advantage here is control: you can tailor what appears without forcing “web-only” mode.

Bonus: Disable Other Chrome AI Features (If You Want a Full Lockdown)

AI Mode is just one piece. Recent guides highlight additional policy switches that can disable other AI features in Chrome,
including “Help me write,” AI theme generation, DevTools AI assistance, tab organization, and more.

If your objective is a broadly AI-minimized Chrome, you can selectively apply those policies the same way: create the DWORD under HKLM\Software\Policies\Google\Chrome and set the recommended value.

What This Does (And Doesn’t) Mean for Privacy?

Let’s be precise. Disabling UI entry points and features reduces exposure and limits functionality, but it does not automatically guarantee “zero data collection.”
Policies vary in how they handle data sharing and model improvement.

Google’s enterprise documentation distinguishes between allowing features with or without model improvement. :contentReference[oaicite:11]{index=11}

If your goal is privacy-first browsing, the best approach is layered: disable features you don’t want, reduce AI surfaces in Search, and regularly review settings after major Chrome updates.

Troubleshooting Checklist

• Nothing changed: Verify spelling and path. Use chrome://policy and “Reload policies.”
• AI Mode moved somewhere else: Use GenAiDefaultSettings to set a broader default.
• Search still shows AI: Use udm=14 or a results-hiding extension.
• Concerned about local AI components: Set GenAILocalFoundationalModelSettings to disabled.

Next Steps

Start simple: apply the AI Mode policy, verify it in chrome://policy, then decide how aggressive you want to be.

If you want the cleanest browsing experience with minimal ongoing maintenance: combine Chrome AI Mode disablement with a Search cleanup method (udm=14 or an extension).

That gets you most of the benefit with minimal complexity.