What Is ERR_FILE_NOT_FOUND and How Do You Fix It in Chrome?

ERR_FILE_NOT_FOUND is an error showing that the file or folder Chrome tried to open could not be found. The browser then shows the code ERR_FILE_NOT_FOUND on the “Your file couldn’t be accessed” or “File not found” screen. This error is not the same as a website’s “page not found” (404) response: it usually comes from a file on the computer, a browser extension or a broken shortcut. In this guide we explain the causes and the fixes.

What Does ERR_FILE_NOT_FOUND Mean?

Chrome gives this code when the requested resource is a file path and there is no file at that path. It is most often seen on local files with addresses starting with file:/// and on extension pages with addresses starting with chrome-extension://. When a page on a website cannot be found, the server returns a 404 status code instead, which is a different problem.

Causes of the Error

• A removed or damaged extension: When an extension that changes the new tab or startup page is removed or damaged, Chrome tries to open an extension page that no longer exists.
• A moved or deleted local file: A bookmarked HTML or PDF file, or one in the recently opened list, may have been moved or deleted.
• A wrong startup page or shortcut: An old address added to the Chrome shortcut or the startup settings.
• Unwanted software: Software that changes browser settings can point the startup page to a file that does not exist.
• A wrong path during development: A relative path in an HTML file can point to the wrong location when the file is opened locally.

How to Fix ERR_FILE_NOT_FOUND

1. Check the Path in the Address Bar

If the address starts with file:///, check in File Explorer whether the file is still in that folder. If the file was moved, open it from its new location and update the bookmark.

2. Find the Problem Extension

If the address starts with chrome-extension://, the problem is an extension. Open the chrome://extensions page, turn on Developer mode and compare the extension ID in the address bar with the IDs in the list. Remove and reinstall the matching extension, or remove it completely. If the ID is not in the list, the extension has already been removed; check the settings in the next step.

3. Fix the Startup and Home Page Settings

On the chrome://settings/onStartup page, remove old addresses listed under “Open a specific page or set of pages”. On the chrome://settings/appearance page, check the address the home button points to.

4. Check the Chrome Shortcut

Right-click the Chrome shortcut on the desktop or taskbar and open Properties. The Target field should end with chrome.exe"; if a file path or address has been added after it, delete it.

5. Reset Settings and Scan the Computer

If the problem continues, restore the defaults on the chrome://settings/reset page; this does not delete bookmarks or saved passwords. If the settings keep changing back on their own, scan the computer for unwanted software with your security software.

For Developers

If the console shows net::ERR_FILE_NOT_FOUND for a CSS, JavaScript or image file, you are opening the page over file:/// and a path is wrong. Root-relative paths such as /css/style.css point to the root of the disk when a local file is opened; using a local development server for testing (for example python -m http.server) removes this problem.

If you see a generic error instead of this code, see our guide on ERR_FAILED.

Conclusion

ERR_FILE_NOT_FOUND shows that the local file or extension page Chrome tried to open could not be found. The path in the address bar tells you where the problem is: for local files, check the file’s location; for extension pages, check the extension and the startup settings. This usually solves the problem.