Chrome says your file may have been moved or deleted

When opening locally stored PDFs in Chrome, sometimes Chrome says the file may have been moved or deleted. More specifically, the error message says “Your file was not found. It may have been moved or deleted. ERR_FILE_NOT_FOUND.” But nobody moved or deleted the file, because I just clicked on it. In fact, I could still see it sitting right there in Windows Explorer.

Oddly enough, I had other files in the very same folder that opened fine. No errors.

Your file was not found. It may have been moved or deleted. ERR_FILE_NOT_FOUND
Getting this error message on a file you just tried to open is frustrating, but it’s easy to avoid.

It turns out the problem is the filename. That explains why other files in the same folder open just fine. I found that if I have the # character anywhere in the filename, I get the error message. When I rename it to not include that character, the file opens with no issues.

The operating system doesn’t care if you put the # character in a filename, but that’s an illegal character for web browsers, so Chrome doesn’t know how to handle it.

Here are some other characters that can cause the same problem:

# pound < left angle bracket > right angle bracket + plus sign
% percent $ dollar sign ! exclamation point ` backtick
& ampersand @ at sign ‘ single quotes | pipe
{ left bracket } right bracket “ double quotes = equal sign

Avoid using these characters in filenames for PDFs, if you frequently open PDFs in Chrome or another web browser. Using Chrome for PDFs is a good idea, by the way.

I’m not sure I want to admit how many other things I tried before I found this solution. It’s probably a good thing I lost count.

When you name your PDFs, to keep Chrome from saying the file may have been moved or deleted, avoid those characters. If you don’t want to memorize that list, stick to using just letters, numbers, periods, and spaces in your filenames. Letters and numbers are always safe.

I hope this helps you. You might also want to check out my advice on avoiding aw snap errors in Chrome.

Leave a Reply