Chrome Silently Installs 4GB Gemini Nano AI Model — Hanff Report

On May 4, 2026, privacy lawyer and former EU Commission advisor Alexander Hanff published a 27-minute forensic analysis showing that Google Chrome silently downloads a 4 GB Gemini Nano on-device AI model to the user's disk on any eligible profile — with no consent dialog, no opt-out short of chrome://flags, and an automatic re-download every time the user deletes it.

What Happened

Hanff's investigation, published on his "That Privacy Guy!" blog and rocketing to #2 on Hacker News with 744 points within eight hours, documents a four-way evidence chain — macOS kernel filesystem events, Chrome's per-profile Local State JSON, Chrome's runtime feature flags, and Google's component-updater logs — all agreeing that Chrome wrote a file called weights.bin into a directory named OptGuideOnDeviceModel on a freshly-created audit profile that had received zero human keyboard or mouse input.

According to Hanff's timestamps, on a clean Apple Silicon Chrome profile created on April 23, 2026, the install fired on April 24 at 14:38:54 UTC and completed 14 minutes 28 seconds later. Three concurrent unpacker subprocesses spawned by Chrome (not by the GoogleUpdater service) wrote the 4 GB weights.bin, a manifest, and four smaller text-safety models. The component version — 2025.8.8.1141 — matches the Gemini Nano weights Google has been rolling into Chrome since 2024 to power features like "Help me write", on-device scam detection, the Summarizer API and tab-group AI suggestions.

Google Chrome holds 64%+ global browser market share — between 3.45 and 3.83 billion users worldwide as of 2026.

Key Details

File and path: OptGuideOnDeviceModel/2025.8.8.1141/weights.bin in the user profile directory, ~4 GB. The naming is internal Chrome jargon for "OptimizationGuide on-device model" — the binary is not labelled "Gemini Nano" anywhere a non-technical user would look.
Trigger: Chrome profiles the device's hardware (CPU, GPU, RAM, VRAM) and pushes the model on any machine that meets a "performance class" threshold — roughly 16 GB of RAM and a capable GPU. The user's chrome://settings/ai surface is enabled in lockstep with the install, meaning the settings page that would let a user refuse the model only appears after the install has been triggered.
Re-download on delete: Multiple independent reports on Windows confirm that deleting weights.bin causes Chrome to silently re-download it on the next eligible window. Persistent removal requires either disabling the feature in chrome://flags, applying enterprise policy, or uninstalling Chrome entirely.
Hanff's climate estimate: using the Pärssinen et al. (2018) figure of 0.06 kWh/GB and an EU-27 grid factor of 0.25 kg CO2e/kWh, Hanff calculates the one-time delivery cost at 0.06 kg CO2e per device. Aggregated to a mid-band estimate of 500 million eligible Chrome installs, that is ~120 GWh of energy and ~30,000 tonnes of CO2e — the annual emissions of roughly 6,500 EU passenger cars, or one return London-Sydney flight for 8,000 economy passengers.
The "AI Mode" pill is cloud, not local: Hanff notes that the prominent "AI Mode" pill Chrome 147 renders next to the omnibox is a cloud-backed Search Generative Experience surface — queries typed into it are sent to Google's servers, not processed by the locally-installed Nano model. The on-device model only powers buried features like Help-Me-Write in <textarea> menus and tab-group AI suggestions.
Legal posture: Hanff argues the install is a direct breach of Article 5(3) of Directive 2002/58/EC (the ePrivacy Directive), which requires prior, freely-given, specific, informed, and unambiguous consent for storing information on a user's terminal equipment that is not strictly necessary to deliver a service the user explicitly requested. He further argues it engages Article 5(1) and Article 25 GDPR, plus deceptive-design pattern families catalogued in EDPB Guidelines 03/2022.

What Developers and Users Are Saying

Discussion on the Hacker News thread (item?id=48019219, 538 comments at the time of writing) is largely sympathetic to Hanff's analysis but split on the climate framing. The most upvoted comments focus on the consent and disk-space issue: power users on r/chrome and r/privacy report finding multi-gigabyte weights.bin files on machines they thought were clean, and several pointed to the existing reporting from Pure Infotech, Vishwam Dhavale, and WinAero through 2025 that flagged the same directory months before Hanff's piece.

The technical pushback, mostly from Chromium contributors and ex-Googlers, argues that Gemini Nano is invoked locally for privacy-positive features like on-device scam detection, that the download is gated by a hardware-eligibility check, and that the re-download behaviour is consistent with how Chrome ships any component update. The privacy-side rebuttal — "none of those framings answer the question of whether the user consented" — has been the dominant counter so far.

On Reddit's r/programming and r/degoogle, the recurring complaint from international users is the bandwidth cost on metered mobile data plans, where 4 GB is on the order of a month's allowance in much of Africa, South Asia and Latin America — populations Hanff explicitly singles out as bearing the welfare cost of the silent push.

What This Means for Users

If you run Chrome on a desktop machine with at least 16 GB of RAM and a capable GPU, check your user profile directory for OptGuideOnDeviceModel/. On macOS that is typically ~/Library/Application Support/Google/Chrome/<Profile>/OptGuideOnDeviceModel/; on Windows it sits under %LOCALAPPDATA%\Google\Chrome\User Data\<Profile>\OptGuideOnDeviceModel\; on Linux under ~/.config/google-chrome/<Profile>/OptGuideOnDeviceModel/.

To stop Chrome re-downloading the model, the most reliable home-user route is to open chrome://flags, search for OptimizationGuideOnDeviceModel and ProhibitedNotificationsOnDeviceModelPath-related flags, and disable on-device model components. Enterprise admins can use the GenAILocalFoundationalModelSettings policy to set the value to 1 ("do not download") and push it via Chrome Browser Cloud Management.

Deleting weights.bin on its own will not stop the behaviour — Chrome will re-fetch it from edgedl.me.gvt1.com the next time the device is eligible.

What's Next

As of publication, Google has not responded publicly to Hanff's piece. Historically, the company has documented the on-device model in Chrome for Developers and in I/O announcements going back to May 14, 2024, but the consumer-facing documentation does not, with prominence proportionate to a 4 GB silent download, surface what the cost of the feature is. Hanff is calling for retrospective notification, an explicit pre-install consent prompt, persistent respect for user deletion, and disclosure of aggregate model-push bandwidth and carbon footprint in Google's annual ESG report under the EU Corporate Sustainability Reporting Directive (CSRD).

Whether European regulators move on the Article 5(3) ePrivacy argument is the open question. The same provision underpinned the cookie-banner enforcement wave of 2018–2023; applying it to silently-pushed AI model weights would be a significant extension. The CNIL, the Irish DPC and the UK ICO have all opened informal inquiries into AI-feature distribution patterns over the past 18 months, but no formal investigation specific to the Chrome Nano push has been announced as of May 5, 2026.

Privacy Researcher Says Google Chrome Silently Pushes 4GB Gemini Nano Model to Users — Climate Cost Up to 60,000 Tonnes CO2e (May 4, 2026)

What Happened

Key Details

What Developers and Users Are Saying

What This Means for Users

What's Next

Sources