Quick answer: ERR_FILE_NOT_FOUND usually means a browser extension is blocking or hijacking the page request, or a bookmark/shortcut points to a file or path that no longer exists. Disabling extensions one by one and checking the link itself fixes most cases in under five minutes.
What ERR_FILE_NOT_FOUND Means
Unlike a normal “page not found” (404) error that comes from a website’s server, ERR_FILE_NOT_FOUND is generated by Chrome itself, before the request even reaches the internet. It means Chrome tried to load a resource — often a local file, a `chrome-extension://` URL, or a redirect target — and couldn’t locate it at all.
Common Causes
- A browser extension is intercepting the request and redirecting it to a missing internal file.
- A bookmark or shortcut points to a local file (PDF, HTML, image) that was moved, renamed, or deleted.
- A corrupted browser profile with broken cached redirect rules.
- A malformed or truncated URL pasted into the address bar.
How to Fix ERR_FILE_NOT_FOUND
- Reload the page. Sometimes this is a one-off glitch from a slow redirect chain.
- Check the URL itself. If it points to a local file path (starts with
file://) rather thanhttps://, the file has likely been moved or deleted from your Chromebook or a connected drive. - Disable extensions one at a time. Go to
chrome://extensions, toggle each one off, and reload the page after each. Ad blockers and privacy/redirect extensions are the most common culprits. - Clear your browsing cache. See our guide to clearing cache and cookies on a Chromebook — corrupted cache entries can trigger broken internal redirects.
- Try the link in a Guest Mode window. This isolates your extensions and profile entirely. See our Guest Mode guide. If the page loads fine there, the problem is your profile or an extension.
Still Not Fixed?
If ERR_FILE_NOT_FOUND appears on every site you visit, not just one, your ChromeOS profile may be corrupted. Try creating a secondary user profile to test, or as a last resort, back up your data and Powerwash using our Powerwash guide.
FAQ
Is ERR_FILE_NOT_FOUND the same as a 404 error?
No. A 404 comes from the website’s server after a successful connection. ERR_FILE_NOT_FOUND happens before that, generated locally by Chrome when it can’t resolve the request target at all.
Can a VPN cause this error?
Yes, some VPN and proxy extensions rewrite request URLs and can trigger this error if misconfigured. Disable the VPN extension temporarily to test.
