The Definitive Guide to Removing Google Chrome's Hidden Gemini Nano AI Model from Your Mac

Overview

If you’re running a Mac with an Apple Silicon or Intel chip, you might have noticed your hard drive space mysteriously disappearing. The culprit? Google Chrome’s Gemini Nano – a 4GB AI model designed to accelerate on-device features like writing assistance and image editing. Starting with Chrome version 126 (released June 2024), this model has been silently downloaded onto millions of machines without explicit user consent. Security researcher Alexander Hanff first spotlighted this issue in May 2024, and while Google later introduced a setting to disable and remove Gemini Nano, that toggle has been slow to roll out, leaving many Mac users stuck with a 4GB space hog they didn’t ask for.

The Definitive Guide to Removing Google Chrome's Hidden Gemini Nano AI Model from Your Mac — Source: www.fastcompany.com

This guide walks you through several methods to banish Gemini Nano from your Mac – whether the official toggle appears in your Chrome settings or not. We’ll cover everything from simple switches to terminal commands, along with common pitfalls to avoid. By the end, you’ll have reclaimed that precious storage and stopped Chrome from re-downloading the model.

Prerequisites

Before you start, ensure you have the following:

A Mac running macOS 12 Monterey or later (methods tested on macOS 14 Sonoma and macOS 15 Sequoia).
Chrome version 126 or newer (check by navigating to Chrome > About Google Chrome).
Administrator privileges – you’ll need to modify system files and possibly use the terminal.
Backup of important data – though these steps are safe, it’s always good practice.

These instructions focus on Mac, but Windows users can adapt the flag-based method (step 2). The official toggle (step 1) works on Windows 11 as of Chrome 148.

Step-by-Step Instructions

Method 1: Use the Official Chrome Setting (If Available)

Google has begun rolling out a dedicated toggle called “On-device AI” in Chrome settings. If it’s present in your version, this is the simplest method.

Open Chrome and type chrome://settings in the address bar, then press Enter.
In the left sidebar, click “Advanced” then “System”.
Look for “On-device AI” option. If you see it, toggle it OFF.
A confirmation dialog may appear; click “Turn off”. Chrome will remove the Gemini Nano model immediately.
Verify removal: close and reopen Chrome, then check the file at ~/Library/Application Support/Google/Chrome/OptGuide – the weights.bin file should be gone.

Note: If this toggle is missing, proceed to Method 2 or 3.

Method 2: Disable Gemini Nano via Chrome Flags

Chrome flags are experimental settings that let you override hidden features. This method works regardless of your macOS version.

Type chrome://flags in the address bar and press Enter.
In the search box at the top, type “Gemini” or “Nano”.
You’ll see a flag called “Optimization guide on device model” (or similar). Click the dropdown next to it and select “Disabled”.
Chrome will prompt you to relaunch. Click “Relaunch”.
After relaunch, remove the existing model files (see Removing Leftover Files below).

Why this works: The flag prevents Chrome from loading or downloading the Gemini model. Without it, Chrome won’t recreate weights.bin.

Method 3: Terminal Command – Full Nuke (Advanced)

If flags aren’t enough (e.g., Chrome still re-downloads after updates), use Terminal to delete the model directory and set permissions to block future downloads.

Quit Chrome completely (Cmd+Q).
Open Terminal (Finder > Applications > Utilities > Terminal).
Run the following command to delete the model folder:
rm -rf ~/Library/Application\ Support/Google/Chrome/OptGuide
Now prevent Chrome from recreating this folder by setting an immutable flag on the parent directory. Run:
sudo chflags uchg ~/Library/Application\ Support/Google/Chrome/OptGuide
(You’ll be prompted for your admin password.)
Launch Chrome. The model should be gone, and Chrome will be unable to create a new OptGuide folder.

Important: This lock will prevent any future Chrome updates from writing to that folder. If you ever want to re-enable Gemini Nano, run sudo chflags nouchg ~/Library/Application\ Support/Google/Chrome/OptGuide and then toggle the flag or setting back on.

Removing Leftover Files (All Methods)

Regardless of which method you use, already-downloaded files may remain. Delete them manually:

Go to ~/Library/Application Support/Google/Chrome/OptGuide/. If the folder exists, delete the entire OptGuide folder.
Also check ~/Library/Google/Chrome/OptGuide/ (some versions may store files there).
Empty the Trash.

Common Mistakes

Mistake 1: Only deleting the file, not the folder. Chrome will simply re-download weights.bin if the folder structure remains. Always delete the whole OptGuide folder.
Mistake 2: Forgetting to disable the flag after deleting files. Without setting the “Optimization guide” flag to Disabled, Chrome will recreate the model on next restart.
Mistake 3: Using the wrong terminal command. Copy-paste the exact command from this guide – a missing backslash or typo can cause errors.
Mistake 4: Assuming the official toggle works instantly. The “On-device AI” setting is still rolling out; even if you have Chrome 148, you might not see it. If missing, fall back to flags.
Mistake 5: Not checking for Chrome updates after removal. An update can sometimes re-enable the flag default. After a major Chrome update, revisit chrome://flags to confirm “Optimization guide on device model” remains Disabled.
Mistake 6: Applying the immutable flag to the wrong folder. Double-check the path before using chflags – locking the Chrome folder itself can cause other issues.

Summary

Google’s Gemini Nano model consumes over 4GB of your Mac’s storage without asking, but you can reclaim that space in three ways. The easiest is the official “On-device AI” toggle in Chrome settings – if you see it. If not, the Chrome flag method reliably prevents future downloads. For a bulletproof solution, the terminal approach permanently locks the model folder. Always delete leftover files first, and remember to check flags after updates. With these steps, you’ll stop paying the “hard-drive tax” for AI you never wanted.

Tags: