How To Fix the ERR_FILE_NOT_FOUND Error in Google Chrome (2025 Guide)

Google Chrome is generally reliable, but certain errors can leave you scratching your head. One of them is the ERR_FILE_NOT_FOUND error.

Unlike issues caused by poor internet connectivity, this one simply means Chrome is trying to load a file but can’t find it where it expects.

If you’ve seen this error recently, don’t panic. Whether you’re just browsing or working on a project, the cause is usually easy to track down and fix.

In this guide, we’ll explain what the error means, why it happens, and show you step-by-step fixes to get Chrome running smoothly again.

What Does the ERR_FILE_NOT_FOUND Error Mean in Chrome?

When Chrome shows the ERR_FILE_NOT_FOUND page, Chrome is telling you: “I was going to open this file, but it is not where I was supposed to find it.”

Sometimes this is due to an errant extension. Sometimes it’s due to a broken file path inside your own HTML or JavaScript project.

ChromeOS users often run into it when files are saved in the wrong location. Linux apps on Chromebooks can only access files stored in the Linux files section, not the standard ChromeOS folders like Downloads.

In short, the error is not a mystery, because it’s simply Chrome sending you a caution flag saying, “I cannot find what you are asking me to load.”

Common Causes of the ERR_FILE_NOT_FOUND Error

Before diving into the fixes, it helps to understand the possible reasons behind this error. Here are the most common ones:

1. Corrupted or Outdated Chrome Extensions

Most users run into this Chrome error because of an extension that’s outdated, corrupted, or improperly installed. The extension might be pointing to resources that aren’t there anymore.

2. Incorrect File Paths or Missing Resources

Developers will recognize this one. If your HTML references a JavaScript file in /scripts/app.js but you accidentally saved it as apps.js in /script/, Chrome has no way of finding it.

3. Deleted, Moved, or Renamed Files

If you’ve recently reorganized folders, Chrome might still be looking for the old file name or path.

4. Local File Access Issues (HTML/JavaScript Testing)

Opening files directly in Chrome using file:// often leads to headaches. Chrome enforces stricter rules compared to a proper server environment.

5. Chromebook Linux Environment File Path Conflicts

Linux files on Chromebooks live in their own environment. If your code uses a ChromeOS path but you’ve saved the file under Linux, Chrome won’t be able to locate it.

6. Rare Causes: File Corruption or Malware Interference

Very rarely, corrupted system files or malware can prevent Chrome from loading resources correctly. It’s not the first thing to check, but running a scan is a good precaution.

How to Fix the ERR_FILE_NOT_FOUND Error in Chrome (Step-by-Step Fixes)

Let’s walk through the most reliable fixes. Take them one at a time—most people find the issue within the first two steps.

1. Disable Chrome Extensions and Identify the Problematic One

Since extensions are the usual suspect, start here.

Open Chrome, type chrome://extensions/ into the address bar, and toggle everything off. Restart Chrome. If the error disappears, you’ve confirmed it’s an extension problem.

Now re-enable them one by one. The moment the error comes back, you’ve found the guilty party. Removing or updating that extension usually solves it.

Pro Tip: Extensions like “Chrome Default Tab” have historically been notorious for triggering this exact error.

2. Remove Leftover Extension Files from Chrome’s User Data Folder

Occasionally, Chrome leaves behind old extension files even after uninstalling. While not common, these leftovers can still confuse Chrome into looking for missing resources.

On Windows, close Chrome, press Win + R, and paste this:

%LOCALAPPDATA%\Google\Chrome\User Data\Default\Extensions
dir

On macOS, navigate to:

~/Library/Application Support/Google/Chrome/Default/Extensions

You’ll see folders with long cryptic names, those belong to extensions. Delete the ones related to extensions you’ve already removed.

When you reopen Chrome, it will stop trying to load those ghost files.

3. Reset Chrome to Its Default Settings

If you can’t pin it on an extension, resetting Chrome is your next best step.

Go to chrome://settings/reset and choose Restore settings to their original defaults. Don’t worry, you won’t lose bookmarks or passwords, just custom settings and extensions.

This gives Chrome a fresh start without the nuclear option of reinstalling.

4. Use a Local Web Server for Testing Files

If you’re a developer, you’ll thank yourself for this fix. Opening HTML files directly in Chrome (file://) often leads to ERR_FILE_NOT_FOUND because Chrome blocks certain relative paths.

Instead, spin up a lightweight local server. For example, in Python:

cd myproject
python -m http.server

Now head to http://localhost:8000 in Chrome. Your file paths will resolve properly just like they would in production.

Testing with file:// can hide problems that only appear later. A local server matches real browser behavior, so you’ll catch issues earlier.

5. Fix Chromebook Linux File Path Conflicts

If you’re on a Chromebook, double-check that your project files live under Linux files in your file manager. Otherwise, ChromeOS paths won’t align with Linux paths.

The fix is simple: move your project folder into Linux files and run it from there.

Other Troubleshooting Scenarios for the ERR_FILE_NOT_FOUND Error in Chrome

When ERR_FILE_NOT_FOUND Appears in Web Development Projects

Here’s a simple HTML example that will break:

<script src="scripts/app.js"></script>

If app.js doesn’t exist in the scripts/ folder, Chrome immediately throws the error.

To fix this, check your spelling and folder structure. Developers often spend hours chasing a “Chrome problem” when it’s just a typo in their code.

When the Error Happens in Web Apps or SaaS Dashboards

If you see it inside a SaaS product or web dashboard, the issue isn’t on your end. The platform’s deployment may have missing or outdated assets. All you can really do is report it, the dev team will need to fix it server-side.

How to Prevent ERR_FILE_NOT_FOUND From Happening Again

Here are few pointers to keep in mind to avoid getting this error in future:

• Keep your Chrome browser and extensions updated.
• If you’re a developer, stick to consistent naming conventions and test with a local server.
• Don’t let unused extensions pile up, they’re often behind these issues.
• Occasionally run malware scans as a precaution.

Final Thoughts

The ERR_FILE_NOT_FOUND error might feel disruptive, but in reality it’s Chrome pointing out a missing puzzle piece. For everyday users, it usually comes down to a rogue extension. For developers, it’s more often a simple file path mistake. Chromebook users face the unique wrinkle of Linux file paths not matching ChromeOS.

The best part? Every scenario has a straightforward fix. Disable or clean up extensions, reset Chrome if needed, and if you’re coding, set up a local server and double-check your paths.

For SaaS apps or larger platforms, similar errors can happen when files are missing on the server. That’s why stable hosting matters. Cloudways helps prevent these issues by delivering assets reliably, with built-in caching, scaling, and monitoring.

So the next time that Chrome indicates it “can’t locate a file”, think of it as a nudge in the right direction. Addressing the issue not only gets Chrome back to its optimal operation but can also enhance your workflow, regardless of if you’re simply browsing the web or building your next project.

Salwa Mujtaba

Salwa Mujtaba is a Technical Content Writer at Cloudways. With a strong background in Computer Science and prior experience as a team lead in Cloudways Operations, she brings a deep understanding of the Cloudways Platform to her writing. Salwa creates content that simplifies complex concepts, making them accessible and engaging for readers. When she's not writing, you can find her enjoying good music, reading a book, or spending quality time with her family.

Get Connected on: Twitter Community Forum