Chrome weights.bin File: What the 4GB AI Download Is and How to Delete It

Chrome has been quietly downloading a file called weights.bin onto eligible computers, with no prompt, no notification, and no indication the transfer is happening, The Verge and Android Authority both reported today. The file ranges from 3GB to 4GB. Users are discovering it only after noticing unexplained drops in available disk space.

This affects a specific subset of users: those on qualifying hardware who have triggered Chrome's on-device AI features. If your machine meets the eligibility thresholds, the file may already be there. Deleting it alone won't solve the problem.

Below: what weights.bin is, whether your system qualifies, and the exact sequence needed to remove it permanently.

What is the Chrome weights.bin file?

weights.bin is Gemini Nano, Google's on-device AI model. More precisely, it's the model weights: the numerical parameters that allow the AI to run locally on your machine without sending requests to Google's servers. Chrome uses these weights to process AI tasks on-device, keeping your text prompts, draft emails, and page summaries off Google's cloud infrastructure, according to Android Authority.

Chrome ships seven on-device AI APIs backed by this model, according to a DEV Community technical analysis published earlier this week. Those APIs became generally available for Chrome extensions with Chrome 138, meaning the pool of triggers for the download has expanded well beyond Chrome's own built-in features. Any compatible extension or webpage with an Origin Trial token can now call the model.

The Gemini Nano model itself is documented as approximately 2GB, but users are reporting installed sizes of 3GB to 4GB (Android Authority, today; Gemini Lab, last month). The sources don't reconcile that discrepancy. Google acknowledges the size can vary across browser updates, but that disclosure sits in a lengthy developer guide rather than anywhere a typical user would encounter it, The Verge noted today.

The download kicks off silently. When a qualifying machine encounters a relevant page, an installed extension, or an Origin Trial token on an unmetered connection, Chrome begins pulling the model in the background. There is no installation prompt. No dialog. No notification that gigabytes are being written to disk, Android Authority confirmed.

Chrome also manages the model autonomously after installation. If free disk space drops below 10GB, Chrome removes it. If eligibility conditions go unmet for 30 consecutive days, the model is purged. Both removals happen without user interaction, and both trigger a silent reinstall when conditions return, the DEV Community analysis found.

Am I affected? How to check if Chrome downloaded the file

Start at chrome://on-device-internals. Open that address in a new Chrome tab. If your hardware qualifies and the model is present, it will appear with a version number and file size, the DEV Community analysis explains. You can also check Chrome's local data folder directly, looking for a directory called OptGuideOnDeviceModel that contains the weights.bin file (The Verge, today).

Chrome checks four system requirements before initiating the download: more than 4GB of GPU VRAM, at least 16GB of system RAM, four or more CPU cores, and at least 22GB of free storage on the drive holding the Chrome profile (Android Authority, today; DEV Community, this week). Supported operating systems are Windows 10 and 11, macOS 13 or later, Linux, and ChromeOS on Plus devices (DEV Community, this week).

If your system doesn't clear those requirements, Chrome won't download the model. If it does, and Chrome has encountered anything that calls the on-device AI API during ordinary browsing or extension activity, the file is likely already on your disk.

How to permanently remove the file and stop Chrome from re-downloading it

Deleting weights.bin directly won't hold. If on-device AI features remain enabled, Chrome will download the file again on the next browser restart, Android Authority reported today.

The correct sequence: disable the feature first, then delete the file. Go to Settings > System and toggle off On-Device AI (The Verge, today). With that toggle off, deleting weights.bin and the OptGuideOnDeviceModel directory should prevent Chrome from fetching a replacement, as long as On-Device AI remains disabled.

The tradeoff is concrete. Turning off On-Device AI disables the Chrome features that depend on it: scam detection alerts, writing assistance, autofill, and suggestion features, The Verge reported. Users who want those features keep the file. Users who want the storage back disable On-Device AI and reclaim it.

The privacy benefit Google isn't surfacing clearly

Google's rationale for local processing is straightforward. When Chrome handles AI requests on-device, your text prompts, page summaries, and autofill inputs don't travel to Google's servers, Android Authority explained today. For users who have wondered what Chrome's AI tools do with their input, that's a meaningful difference from cloud-dependent processing.

The features powered by Gemini Nano cover a lot of ordinary browsing ground: scam detection, writing assistance, autofill, and suggestion features that surface across many sessions, The Verge reported. Chrome now downloads and manages a local AI model the way an operating system manages a core library, installing it, removing it, and reinstalling it based on system conditions without user interaction.

The friction isn't with the privacy logic. It's with the disclosure. Google does specify that Gemini Nano's size may vary as Chrome updates the model, but that information appears in a lengthy guide for built-in AI features, not at any point where users are enabling those features in the browser, The Verge noted. Users affected by this aren't being asked to make a storage tradeoff. They're finding out about it after the fact, when space has already disappeared.

What to watch going forward

The more significant question isn't whether this particular file belongs on your disk. It's whether this pattern becomes the norm.

Chrome already treats Gemini Nano as a managed system component: it installs, removes, and reinstalls autonomously based on conditions the user never explicitly set, the DEV Community analysis documents. As the on-device AI API expands to more extensions and more sites, the trigger surface grows. A user who has never deliberately enabled any AI feature could still end up with the model on their disk because of an extension they installed for an unrelated purpose.

Whether Google updates its disclosure practices or adds a visible consent step before initiating a multi-gigabyte background download is worth watching in upcoming Chrome releases. For now, chrome://on-device-internals is the only way to know what's already there.