ERR_FILE_NOT_FOUND is a Chrome-specific error that occurs when the browser cannot locate a file it needs to load. This error appears most often when a browser extension references a file that no longer exists, a local file path is incorrect, or a website links to a resource that has been deleted from the server.
Unlike 404 errors that come from the web server, ERR_FILE_NOT_FOUND is a Chrome browser-level error. It can point to local file paths (file:///), extension resource paths (chrome-extension://), or occasionally remote URLs. The fix depends on which type of resource is missing.
What Causes ERR_FILE_NOT_FOUND
The most frequent cause is a broken Chrome extension. When an extension is partially updated, corrupted, or improperly uninstalled, Chrome tries to load its resources from paths that no longer exist. This triggers ERR_FILE_NOT_FOUND with a URL starting with “chrome-extension://” followed by the extension’s unique ID. You might see this error on new tabs, during page loads, or when clicking browser toolbar buttons.
Other causes include typing a local file path incorrectly in the address bar (file:/// URLs), deleted bookmarks pointing to local HTML files, websites referencing removed JavaScript or CSS files, corrupted browser cache storing stale file references, and malware that hijacks new tab pages with broken local resources.
Fix 1: Identify and Remove the Broken Extension
If the error URL starts with “chrome-extension://,” the long string after it is the extension’s ID. Go to chrome://extensions and enable “Developer mode” (toggle in the top right). Now each extension shows its ID. Match the ID from the error URL to find the problematic extension. Remove it by clicking “Remove,” then reinstall it fresh from the Chrome Web Store if you still need it. If you cannot identify the extension by ID, disable all extensions and re-enable them one by one until you find the culprit.
Fix 2: Clear Browser Cache
Cached references to deleted files cause ERR_FILE_NOT_FOUND even after the underlying issue is fixed. Go to Chrome Settings, Privacy and Security, Clear browsing data. Select “All time” and check “Cached images and files.” Clear the data and restart Chrome. For a more thorough cache clear, also delete the Chrome cache directory manually: close Chrome, navigate to %LOCALAPPDATA%\Google\Chrome\User Data\Default\Cache on Windows, and delete all files in that folder.
Fix 3: Reset Chrome Settings
If the error persists across multiple sites or appears on the new tab page, reset Chrome to its default state. Go to Settings, Reset and clean up, Restore settings to their original defaults. This disables all extensions, clears temporary data, and resets Chrome flags. Your bookmarks, history, and saved passwords are preserved. After resetting, re-enable only the extensions you actively use.
Fix 4: Check for Malware
Malware that hijacks your new tab page or injects scripts often causes ERR_FILE_NOT_FOUND when its files are quarantined by antivirus software. Run a full scan with Windows Defender or your preferred antivirus. Also run Chrome’s built-in cleanup: go to Settings, Reset and clean up, Clean up computer (on older Chrome versions) or use the Safety Check feature. Look for suspicious extensions you did not install and remove them.
Fix 5: Fix Local File Paths
If you are trying to open a local file and see ERR_FILE_NOT_FOUND, verify the file exists at the exact path shown in the address bar. Windows file paths use backslashes but Chrome URLs use forward slashes, so the correct format is file:///C:/Users/name/file.html. Check for typos, missing file extensions, and incorrect capitalization. If the file was moved or deleted, update your bookmark or shortcut to point to the new location.
Frequently Asked Questions
Why does ERR_FILE_NOT_FOUND appear on every new tab?
A new tab page extension is broken or partially uninstalled. Go to chrome://extensions, find any new tab override extensions, and remove them. If none are visible, reset Chrome to defaults (Settings, Reset settings) to clear hidden extension remnants. Malware that hijacks the new tab page also causes this when its files are removed by antivirus.
Is ERR_FILE_NOT_FOUND the same as a 404 error?
No. A 404 error comes from a web server indicating a page does not exist on that server. ERR_FILE_NOT_FOUND is a Chrome browser error indicating Chrome itself cannot find a local file or extension resource. The 404 is a server response, while ERR_FILE_NOT_FOUND means no server was contacted at all because the resource is expected to be local.
Can ERR_FILE_NOT_FOUND affect website loading?
If a website references a JavaScript or CSS file that returns this error, parts of the page may not load correctly. Missing JavaScript can break interactive features, and missing CSS can break the page layout. However, this is rare for remote resources because servers typically return 404 instead. Check the browser console (F12, Console tab) for specific file loading errors.
