ERR_FILE_NOT_FOUND in Chrome: What it Means and How to Fix It

Seeing ERR_FILE_NOT_FOUND in Google Chrome usually means the browser can’t reach a file it expected to load. Most of the time the file still exists—the problem is often a Chrome extension or a wrong path.

Below is a quick, no-nonsense guide to fix it.

Quick checks (do these first)

1. Check the address bar. Make sure the URL or file path is correct. Typos and extra characters are common.
2. Hard refresh the page.
   • Windows: Ctrl + F5
   • Mac: Cmd + Shift + R
3. Try a different browser. If it loads in Edge/Firefox, Chrome is the likely culprit.

The common cause: extensions

Extensions can point Chrome to missing or blocked resources, or clash with each other.

1) Turn extensions off one by one

1. Open chrome://extensions/
2. Toggle Off an extension.
3. Hard refresh the page you’re testing.
4. If the error is still there, toggle the next one.
   When the error disappears, you’ve found the problematic extension. Update it or remove it.

Tip: After removing an extension, test again before moving on.

2) Clean up leftover extension files (Windows)

Sometimes removed extensions leave files behind.

1. Press Win + R, paste and open:%LOCALAPPDATA%\Google\Chrome\User Data\Default\ExtensionsIf you use multiple Chrome profiles, the folder may be Profile 1, Profile 2, etc. Check your profile path at chrome://version/ (look for Profile Path).
2. Open each subfolder and check its manifest.json to see which extension it belongs to.
3. Delete the folder for the extension you already uninstalled.

If you just removed an extension, sort folders by Date modified to find it faster.

3) Special case: “Default Tab”

If you spot a Default Tab extension or program, remove it from Control Panel → Programs → Uninstall a program, then delete it from chrome://extensions/. It tends to reinstall itself if you only remove it from Chrome.

Reset Chrome (when nothing else works)

Resetting turns off all extensions and clears temporary data while keeping your bookmarks and passwords.

1. Open chrome://settings/reset
2. Click Restore settings to their original defaults → Reset settings
3. Restart Chrome and test again.

Other places you might see it

• Android (Chrome): Try another mobile browser to confirm it’s a Chrome issue.
• Outlook web / PDF preview: Check or disable PDF-related extensions.
• Windows 10/11: Follow the same extension steps above.
• While developing (HTML/JS): Verify your file paths. A missing or moved image/script will trigger this. Use relative paths carefully and confirm the file actually exists in that location.

In other browsers this often shows up as a plain 404 Not Found.

Prevent it from coming back

• Keep extensions updated. Outdated add-ons break more often.
• Use fewer extensions. Only what you need. Avoid duplicates that do the same job.
• Watch compatibility after Chrome updates. If something breaks, check the extension’s recent reviews or changelog.
• For developers: double-check paths and deployment steps so assets don’t go missing.

FAQs

Is this a server or hosting problem?
Usually no. This error is mostly on the browser side, often caused by extensions or bad paths.

Will changing my host fix it?
Not for this specific error. Hosting won’t fix a broken Chrome extension or a wrong file path.

Do I lose passwords if I reset Chrome?
No. A standard reset keeps bookmarks and saved passwords. It disables extensions and clears temporary data.

Short fix checklist

• Check URL or file path
• Hard refresh
• Disable extensions one by one
• Remove leftover extension folders (if on Windows)
• Reset Chrome if needed

That’s it. Start with extensions, confirm paths, and reset only if you must.