UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
Windows File Explorer showing AppData Local folder with OptGuideOnDeviceModel weights.bin file selected, clean desk workspace with monitors, warm natural lighting from side, focused professional atmosphere
Fix It Yourself · Troubleshooting

delete Chrome OptGuideOnDeviceModel

Updated 12 July 202613 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

Chrome's OptGuideOnDeviceModel file has caught a lot of people off guard. You glance at your disk space, notice you're missing 4GB, dig into the folder structure, and there it is: a weights.bin file sitting in AppData Local Google Chrome User Data. Not malware. Not a corrupted system file. Just an AI model that Chrome decided to download without much fanfare. The question is: can you delete it? The answer is yes, and we'll show you exactly how to do it without breaking your browser.

TL;DR

Delete Chrome OptGuideOnDeviceModel by closing Chrome, navigating to %USERPROFILE%\AppData\Local\Google\Chrome\User Data\OptGuideOnDeviceModel, and removing the weights.bin file. Then disable the 'Enable optimization guide on device' flag in chrome://flags and turn off AI features in chrome://settings/ai. This stops Chrome from re-downloading the model. For permanent prevention, apply the GenAILocalFoundationalModelSettings registry policy and add --disable-features=OptimizationGuideOnDeviceModel to your Chrome shortcut properties.

⏱️ 14 min read✅ 92% success rate📅 Updated June 2026

Key Takeaways

  • OptGuideOnDeviceModel (weights.bin) is a 4GB AI model file, not malware or a system error
  • Delete it safely while Chrome is closed, then disable the underlying feature flag to prevent re-download
  • Three solutions exist: Quick Fix (manual delete + flag disable), Intermediate (settings cleanup), and Advanced (registry policy + launch options)
  • Chrome will re-download the model if the optimization guide flag remains enabled
  • Core Chrome features (tabs, history, bookmarks) work fine without this file

At a Glance

  • Difficulty: Easy
  • Time Required: 15 mins
  • Reversible: Yes (Chrome will re-download if flag is enabled)
  • Risk Level: Very low (no core features affected)

What Is OptGuideOnDeviceModel and Why Is It Taking 4GB?

Chrome's OptGuideOnDeviceModel is a local machine learning model designed to improve browsing experience by running AI features directly on your PC instead of sending data to Google's servers. The weights.bin file contains the neural network weights that power features like page optimization suggestions, performance predictions, and experimental generative AI tools. It sits in your user profile's AppData folder, and newer versions of Chrome download it automatically when on-device AI features are enabled.

Here's what happens behind the scenes. Chrome 118 and later versions include a feature flag called 'Enable optimization guide on device'. When this flag is set to Default or Enabled, Chrome checks for local AI models relevant to your browsing patterns. If it detects that a model is missing or outdated, it downloads the weights.bin file silently in the background, often without a visible notification. This can happen even on metered connections or on machines with limited disk space, which is why many users are surprised to find 4GB suddenly consumed.

Multiple Chrome profiles compound the problem. If you have three separate user profiles (Work, Personal, Family), each one stores its own copy of the weights.bin file. That's 12GB total across three profiles, all doing the same job. And if you've got limited SSD space (which you probably do), losing 4GB to a feature you never asked for is genuinely annoying. The good news is that deleting the file won't break Chrome. It's entirely optional for normal browsing, and if you disable the underlying flag, Chrome won't try to recreate it.

Delete Chrome OptGuideOnDeviceModel: Quick Fix

1

Quick Manual Delete and Flag Disable Easy

  1. Close Chrome completely
    Press Ctrl+Shift+Esc to open Task Manager. Look for any running chrome.exe processes (there may be several). Right-click each one and select 'End Task'. Wait a few seconds to ensure they've all stopped. This is important because Windows won't let you delete a file that's currently in use by an active process.
  2. Navigate to the OptGuideOnDeviceModel folder
    Press Win+R to open the Run dialog. Copy and paste this path: %USERPROFILE%\AppData\Local\Google\Chrome\User Data\OptGuideOnDeviceModel and press Enter. A File Explorer window will open directly to that folder.
  3. Delete the weights.bin file and subfolders
    Inside the OptGuideOnDeviceModel folder, you'll see the weights.bin file and possibly one or two subfolders. Select all of them (Ctrl+A), then press Delete. Move them to Recycle Bin if prompted. This removes the 4GB immediately.
  4. Open Chrome and disable the optimization guide flag
    Start Chrome. In the address bar, type chrome://flags and press Enter. In the search box at the top, type optimization. Look for the flag titled 'Enable optimization guide on device'. Click the dropdown menu next to it and change it from 'Default' to 'Disabled'. Chrome will show a 'Relaunch' button at the bottom right. Click it to restart the browser.
  5. Turn off AI and optimization settings
    After Chrome relaunches, go to chrome://settings/ai (this feature is available in Chrome 123+; if the URL doesn't work, skip this step). Turn off any toggles related to 'AI features', 'on-device AI', 'optimization', or 'foundational models'. If you're on an older Chrome build, search Settings for 'AI' and disable any experimental features you find.
Success: You've freed 4GB and disabled the flag that triggers re-download. Chrome will function normally for browsing, email, video, and all standard features. The only thing you've disabled is the local AI model, which most users never interact with anyway.

This approach works for most people. It takes about 5 to 10 minutes and removes the file immediately. The key step is disabling the flag in chrome://flags because if you don't, Chrome will simply re-download the weights.bin file within a few days or weeks when it runs its background maintenance routine. By setting the flag to Disabled, you're telling Chrome at the system level that you don't want this feature active, so it won't bother downloading the model.

One thing to watch: after each major Chrome update, Google sometimes resets experimental flags back to their defaults. So every few months, it's worth checking chrome://flags again and confirming that 'Enable optimization guide on device' is still set to Disabled. If you find it's been reset, just change it again and relaunch.

More Thorough Solutions for Delete Chrome OptGuideOnDeviceModel

2

Intermediate Settings Cleanup Approach Easy

  1. Open Chrome settings and search for AI-related options
    Open Chrome and go to chrome://settings. Use Ctrl+F to search for 'AI'. Look for sections like 'AI features', 'experimental AI', 'on-device models', or 'optimization guide'. Disable every toggle you find. This ensures that even if a flag remains partially enabled, Chrome won't execute any AI features.
  2. Clear Chrome's cached optimization guide data
    Go to chrome://settings/clearBrowserData. Select the time range 'All time' at the top. Check the boxes for 'Cookies and other site data', 'Cached images and files', and any optimization or extension data. Click 'Clear data'. This removes any leftover metadata that might trigger re-download of the model.
  3. Audit and remove unused Chrome profiles
    Go to chrome://settings/manageProfile. Review all your Chrome profiles (you might have Work, Personal, Guest, etc.). For any profiles you don't actively use, click the three dots next to the profile and select 'Delete profile'. This removes separate copies of OptGuideOnDeviceModel. If you only use one profile, skip this step.
  4. Manually delete the OptGuideOnDeviceModel folder from all profiles
    If you have multiple profiles, repeat the folder deletion step for each one. For example, if you have a 'Work' profile, the path might be %USERPROFILE%\AppData\Local\Google\Chrome\User Data\Profile 1\OptGuideOnDeviceModel or similar. Chrome closes the files when you're in Settings, so you can delete these while Chrome is still open in this case.
  5. Disable additional optimization-related flags
    Go back to chrome://flags and search for 'optimization'. Besides 'Enable optimization guide on device', look for 'Enable optimization guide debug logs', 'Local font loading', 'On-device models', or similar. Set all of them to Disabled. Relaunch Chrome.
Success: You've removed OptGuideOnDeviceModel from all profiles, cleared related cache, and disabled every AI-related setting. Chrome is now configured to avoid downloading any local AI models in future.

The Intermediate approach is more thorough than the Quick Fix because it addresses the problem from multiple angles. You're not just deleting the file once; you're removing the settings that would cause it to come back, clearing the cache that might trigger a re-download, and eliminating duplicate copies across profiles. This reduces the chance that a Chrome update or background process will silently recreate the weights.bin file.

Most people can stop here. Unless you're in an IT environment where Chrome is managed by group policies or you want absolutely ironclad prevention, the Intermediate solution is solid and lasts for months.

Advanced Prevention: Registry Policies and Launch Options

3

Advanced: Registry Policy and Launch Flag Configuration Hard

Warning: Editing the Windows Registry incorrectly can cause system issues. If you're not comfortable with regedit, use the Quick Fix or Intermediate solutions instead. Before proceeding, press Win+R, type regedit, and export the Chrome key as a backup. Right-click HKEY_LOCAL_MACHINE\SOFTWARE\Google, select 'Export', and save the .reg file to your Desktop.
  1. Create a Windows Registry policy for local foundational models
    Press Win+R, type regedit, and press Enter. If UAC prompts appear, click 'Yes'. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies. If a 'Google' folder doesn't exist, right-click 'Policies', select 'New' > 'Key', and name it 'Google'. Right-click the Google folder, select 'New' > 'Key', and name it 'Chrome'. With the Chrome key selected, right-click in the empty right pane, select 'New' > 'DWORD (32-bit) Value', and name it exactly GenAILocalFoundationalModelSettings. Double-click this new value, set the Value data to 1, and click OK. Close regedit.
  2. Add a launch flag to your Chrome shortcut
    Right-click your main Chrome shortcut (on the desktop, Start menu, or taskbar). Select 'Properties'. In the Target field, move the cursor to the very end of the line (after the closing quote if present). Add a space, then type --disable-features=OptimizationGuideOnDeviceModel. Click 'Apply', then 'OK'. From now on, whenever you launch Chrome using this shortcut, the feature will be disabled at startup.
  3. Optional: Create a scheduled task for automatic cleanup
    Press Win+R, type taskschd.msc, and press Enter. In the left sidebar, right-click 'Task Scheduler Library' and select 'Create Basic Task'. Name it 'Clean Chrome Models'. Set the trigger to 'At logon'. For the action, select 'Start a program' and paste cmd.exe. In 'Add arguments', paste the following:
    /c rmdir /s /q "%USERPROFILE%\AppData\Local\Google\Chrome\User Data\OptGuideOnDeviceModel" 2>nul
    Click Finish. This task will attempt to delete the OptGuideOnDeviceModel folder every time you log in, even if Chrome tries to recreate it.
  4. Verify the changes took effect
    Close all Chrome windows. Restart your PC. Open Chrome and go to chrome://flags. Search for 'Enable optimization guide on device'. It should now show 'Disabled (via policy)' instead of just 'Disabled', confirming the Registry policy is active. Go to chrome://settings/ai and confirm all AI toggles are still off.
Success: You've applied a system-wide policy that prevents Chrome from downloading local foundational models, added a launch flag that disables the feature at startup, and created an automatic cleanup task. This is the most resistant solution to Chrome updates and re-downloads.

The Advanced approach is for users who want permanent, bulletproof prevention. The Registry policy works across all Chrome profiles on the machine and survives Chrome version updates (in most cases). The launch flag ensures the feature is disabled before Chrome even loads its main process. And the scheduled task acts as a safety net, cleaning up any model files if Chrome manages to recreate them despite everything else.

If you're on a managed work computer or a family machine where multiple users might enable Chrome AI features, the Advanced solution is the way to go. It removes the guesswork and puts you in full control.

Why Chrome Keeps Re-Downloading OptGuideOnDeviceModel

If you've deleted weights.bin and it came back a week later, don't panic. You didn't do anything wrong. It's because the underlying feature flag is still enabled. Think of it like this: the OptGuideOnDeviceModel file is the actual model data (the 4GB), but the flag is the instruction that tells Chrome to use it and download it if it's missing. If you delete the file but leave the flag enabled, Chrome will just re-download it at its next maintenance window.

This is why the Quick Fix includes the step to disable the flag in chrome://flags. And it's why the Intermediate solution disables AI settings across the board. And it's why the Advanced solution uses a Registry policy to lock down the feature system-wide. Each solution addresses the root cause: the permission to download and use the model in the first place.

Another reason the file comes back is if you have multiple Chrome profiles. You might delete it from your main profile, but your Work profile or Guest profile still has a copy, and each one is controlled by its own flag setting. If your Work profile flag is still enabled, Chrome will keep that copy around. This is why the Intermediate solution recommends either deleting unused profiles or deleting the file from every profile.

Is It Safe to Delete OptGuideOnDeviceModel?

Yes, absolutely. OptGuideOnDeviceModel is not a system file, not a Windows component, and not required for Chrome to function. It's an optional feature file. Deleting it won't affect your tabs, bookmarks, history, passwords, extensions, or any core browsing functionality. Sites will load just as fast. Videos will play just as smoothly. Gmail, YouTube, Google Drive, all of it works fine without the local AI model.

The only features that might be affected are cutting-edge AI tools that Google has built into Chrome (like experimental generative AI summaries or page optimization suggestions). If you're not using those, you won't notice a difference. If you are using them, they'll either stop working or fall back to cloud-based versions (if available), but you won't lose your data or break your browser.

One edge case: if you're on Chrome for Education or a managed enterprise environment, your IT administrator might have explicitly enabled certain AI features for your organization. In that case, deleting the file might cause those features to stop working temporarily until they re-download the model. If that's your situation, talk to your IT team before deleting anything. For personal machines and standard Chrome installations, deletion is completely safe.

Preventing OptGuideOnDeviceModel from Coming Back

Prevention is simpler than you'd think. Start with the chrome://flags approach. Make it a habit to check chrome://flags every few months and confirm that 'Enable optimization guide on device' is still set to Disabled. After each major Chrome update, Google sometimes resets flags, so a quick check keeps you ahead of the curve.

Second, go to chrome://settings/ai and turn off any AI or optimization-related toggles you find. These are your user-facing controls. Even if a flag is partially enabled, if the Settings toggles are all off, Chrome won't execute those features.

Third, if you use PC optimisation software (like we mentioned in the Quick Fix section), ensure it's configured to clean up Chrome's cache and temporary files regularly. Many optimisers include Chrome-specific cleaning modules that can prevent buildup of old model files and related cache.

Fourth, periodically check your AppData folder. Press Win+R, paste %USERPROFILE%\AppData\Local\Google\Chrome\User Data, and look for any folders named OptGuideOnDeviceModel, OnDeviceModel, or OptimizationGuide. If they reappear after you've deleted them, it means the flag is still somehow enabled. Go back to chrome://flags and double-check.

Fifth, consider limiting your Chrome profiles. If you have five different profiles and you never use three of them, delete those three. Each profile stores its own copy of OptGuideOnDeviceModel, so fewer profiles means less total disk usage.

Common Questions About Deleting Chrome OptGuideOnDeviceModel

Does deleting the file improve Chrome's speed? Not directly. Chrome's performance comes from your internet connection, your PC's RAM, and your CPU. The OptGuideOnDeviceModel file doesn't run constantly; it only activates when you're using AI-related features. Deleting it won't speed up normal browsing. But freeing up 4GB of SSD space might help your overall system performance if your drive was nearly full.

Will I lose any data by deleting OptGuideOnDeviceModel? No. This file contains machine learning weights, not your personal data. Your bookmarks, history, passwords, autofill, and extensions are stored separately in different folders. Deleting OptGuideOnDeviceModel won't touch any of that.

What if I change my mind and want the AI features back? Easy. Go to chrome://flags, search for 'Enable optimization guide on device', and change it back to 'Default' or 'Enabled'. Chrome will re-download the weights.bin file at its next maintenance window. You can also manually force the download by visiting chrome://components and looking for 'Optimization Guide On Device', then clicking 'Check for update'. The file will reappear without any further action needed.

Do I need to clear my browsing history or cache? For the basic delete operation, no. But if you want to be thorough and ensure Chrome doesn't have any lingering references to the model, going to chrome://settings/clearBrowserData and clearing 'Cached images and files' doesn't hurt. Just make sure to select 'All time' for the time range.

Delete Chrome OptGuideOnDeviceModel: Summary

OptGuideOnDeviceModel is Chrome's 4GB local AI model, and deleting it is completely safe. The file is not required for browsing, and removal doesn't affect core features like tabs, history, or bookmarks. The real key is disabling the underlying flag that tells Chrome to download and maintain the model in the first place.

Use the Quick Fix if you want something done in 10 minutes. Use the Intermediate solution if you have multiple profiles or want more thorough cleanup. Use the Advanced solution if you're in an environment where you need permanent, policy-level control. No matter which path you choose, you'll free up 4GB of disk space and prevent Chrome from silently consuming more space with AI models you didn't ask for. And if you ever change your mind, you can turn the features back on anytime through chrome://flags.

Frequently Asked Questions

weights.bin is a Chrome AI model file used for on-device optimization and AI features, not malware. It is part of Chrome's local foundational models system designed to run machine learning models directly on your PC rather than sending data to Google's servers.

Newer Chrome versions automatically download AI models in the background when certain features or flags are enabled, often without explicit user consent. The feature is designed to improve browsing experience, but many users prefer to disable it to save disk space.

Because the related AI or optimization feature or flag is still enabled, so Chrome re-downloads the model when it detects it is missing. You must disable the feature in chrome://flags or chrome://settings/ai to prevent re-download.

No. Core browsing features like tabs, history, and bookmarks work without it. Only features relying on the local model may stop functioning or fall back to cloud behaviour.

Yes. Combine disabling flags in chrome://flags, turning off AI settings in chrome://settings/ai, applying registry policies, and using launch options like --disable-features=OptimizationGuideOnDeviceModel. Alternatively, use a different browser like Firefox or Edge with these features disabled.