The 30-Second Fix: Kill the Cache (Really)
I've seen this exact error pop up after Chrome updates more times than I can count. The update messes with the disk cache, and suddenly every image that's served from cache throws ERR_FILE_NOT_FOUND. The fastest fix is to nuke the cache for the site you're on.
- Press Ctrl+Shift+Delete (Windows) or Cmd+Shift+Delete (Mac) to open the clear browsing data panel.
- Set the time range to “All time”.
- Check “Cached images and files” (uncheck everything else unless you're desperate).
- Click “Clear data”.
Then hit F5 or Cmd+R to reload. Nine times out of ten, that's it. I had a client last month whose entire product catalog looked like a broken image slideshow after 127 rolled out. Cleared cache, done. If that doesn't work, move on.
The 5-Minute Fix: Disable Hardware Acceleration
Chrome 127 also changed how it handles GPU-accelerated image decoding. On some machines (especially with older Intel GPUs or certain AMD drivers), that breaks image loading entirely. The error might show up on some images but not others, which makes it more confusing.
- Click the three dots in the top right, then Settings.
- Scroll down and click System.
- Toggle off “Use hardware acceleration when available”.
- Click Relaunch when the button appears.
After it restarts, try loading the page again. If images come through, you've found your culprit. You can live with hardware acceleration off—it's not going to kill your machine's performance for most tasks. If you need it back on (like for 4K video), then update your GPU drivers first, then re-enable.
The 15-Minute Fix: Reset Your Profile (The Nuclear Option)
When cache and hardware acceleration don't cut it, the problem is likely a corrupted profile. Chrome 127 had a known issue where the profile's Preferences file got corrupted during update, causing all sorts of weirdness—including this exact error.
Before you nuke everything, try a less invasive move: close Chrome, then rename the profile folder. This keeps your bookmarks and passwords safe because they're synced if you're signed in.
- Close Chrome completely (check the system tray for background processes).
- Press Win+R (Windows) or open Finder (Mac).
- Type
%LOCALAPPDATA%\Google\Chrome\User Data(Windows) or~/Library/Application Support/Google/Chrome(Mac) and hit Enter. - Find the folder named Default and rename it to Default.old.
- Restart Chrome. It'll create a fresh Default folder.
You'll lose your extensions and saved passwords that aren't synced, so only do this if you're okay with that or have sync enabled. If the images load now, you've got a corrupted profile. You can try to salvage bookmarks by copying the Bookmarks file from Default.old to the new Default folder, but honestly, if you're synced, just let it rebuild.
When It's Not Chrome: Check Your Antivirus
One more thing I've run into—some antivirus software (especially Bitdefender and certain corporate security suites) flags Chrome's cache after an update and blocks file access. If the above fixes don't work, temporarily pause your antivirus's web protection and reload. If images pop, add Chrome to the whitelist.
I've also seen this happen with network proxies that cache images. If you're behind a corporate proxy, ask your IT person to flush the proxy cache. But that's rare—most of the time it's the local cache or acceleration.
Still Broken? You Might Be on an Older Version
Chrome 127 had a couple of hotfixes released within days. Check your version in chrome://settings/help and make sure you're on at least 127.0.6533.99. If you're stuck on an older 127 build, update and get the fixes. I've had stubborn cases where only a full reinstall of Chrome did the trick—uninstall, reboot, and grab a fresh installer from google.com/chrome. That's the last resort if all else fails.
Start with the cache clear. It's fast, safe, and solves most cases. If you're still staring at broken images, work down the list. And don't skip the hardware acceleration toggle—that one's saved me more than once.