No Such File or Directory? Causes and Fixes

Updated 5 November 2026 · Standard formula, shown below

“No such file or directory” means a program tried to open or use a path that the operating system could not find. The file or folder may be missing, but an incorrect path, working directory, filename spelling, mount, or symbolic link can produce the same message.

What the Error Means

This wording is common on Unix-like systems, including Linux and macOS, and appears in command-line tools, scripts, programming environments, and applications. It is a description of a failed file-system lookup, not proof that the named file was deleted. The system could not resolve the path as supplied at that moment.

A path identifies a location. An absolute path starts from the file-system root, such as /home/sam/report.txt on Linux or /Users/sam/report.txt on macOS. A relative path is interpreted from a current working directory: report.txt means “look for this in the directory the process is currently using.” If that directory differs from what you expect, a valid file elsewhere will not be found.

Related errors can be easy to confuse. “Permission denied” generally indicates that a path was found but access was refused. “Is a directory” means a program treated a directory as though it were a regular file. Exact wording varies by operating system and application, so use the full error message as a clue rather than assuming all failures have one cause.

Check the Path and Working Directory

Start by checking the location the program is actually searching. In a terminal, pwd prints the current directory on Linux and macOS. Then list its contents with ls, or inspect the intended location directly. For example, if you run cat notes.txt from /home/sam/projects, the command looks for /home/sam/projects/notes.txt, not for a file in your home folder or Downloads.

Use an absolute path as a diagnostic when a relative path fails. If cat /home/sam/notes.txt works but cat notes.txt does not, the file exists and the likely issue is the working directory or the relative path. On Windows, the equivalent checks use Windows paths and commands, such as cd to inspect or change the current directory and dir to list files. Do not assume paths are interchangeable between operating systems.

In scripts and applications, the working directory may not be the folder containing the script. A program launched from a desktop shortcut, scheduler, IDE, or another process can start in a different location than it does when run from a terminal. Check the application’s working-directory setting or build the path from a known directory rather than relying on where the user happened to launch it.

Check Spelling, Case, and Filename Characters

Compare the path with the actual filename, one character at a time. Common slips include a missing extension, an extra space, a different dash or apostrophe, or a misspelled folder name. On many Linux file systems, uppercase and lowercase letters are distinct: Report.txt and report.txt can be different files. Case handling can vary on other systems and file systems, so matching the exact spelling is the safest approach.

Shells also interpret certain characters. Spaces can divide a command into separate arguments unless the path is quoted or the spaces are escaped. For example:

cat "quarterly notes.txt" treats the spaced name as one path.
cat quarterly\ notes.txt escapes the space in many Unix-like shells.
Autocomplete can reduce typing mistakes: type part of a name and press Tab in a shell that supports it.

Quoting rules differ between shells, so commands copied from one environment may not work unchanged in another. Also be cautious when pasting paths: a visually similar character, trailing space, or hidden newline can make the entered path differ from the displayed one.

Look for Missing Folders, Links, and Mounted Storage

The missing item may be a parent directory, not the final file. For /data/archive/2025/log.txt, every directory in the chain must exist and be reachable. Check each component from the closest known parent outward. A program cannot create a file inside a directory that does not exist unless it first creates that directory.

A symbolic link can also point to a target that has been moved or deleted. The link itself may still appear in a directory listing, while opening it fails because its destination no longer exists. Inspect the link and its target before replacing or deleting it; other programs may rely on the link’s location or name.

If a path refers to an external drive, network share, removable device, or mounted file system, confirm that it is connected and mounted where expected. A folder that normally represents mounted storage may still exist when the storage is absent, but its contents will not be available there. Reconnecting or mounting the correct storage may restore access; avoid creating a replacement file in that empty mount location until you know where data is meant to go.

Fixes for Commands, Scripts, and Applications

Copy the complete error. Note the exact path and which command or application reported it. A message may name an executable, configuration file, input file, or directory rather than the item you first suspect.
Confirm the current location. Check the working directory and list its contents. In a script, temporarily print the process’s current directory if the language or runtime provides a straightforward way to do so.
Test the exact path. Check that the file and every parent folder exist, including the correct capitalization and extension. Use an absolute path to separate a location problem from a filename problem.
Check how the path is passed. Quote paths with spaces where required, inspect environment variables used to build paths, and verify that command-line arguments are in the expected order.
Check dependencies and storage. For a command that will not start, confirm that the executable exists at the path being invoked. For a data file, confirm that its drive, share, or mount is available.
Retry in the intended environment. A command that works in a terminal may fail in a service or scheduled task because it has a different user, environment, or starting directory. Set these deliberately instead of assuming they match.

When writing code, prefer a reliable base directory and join path components with the language’s path utilities rather than manually combining slashes. This helps avoid separator and relative-path mistakes. It does not guarantee that the result exists, so applications should still handle missing-file errors clearly.

What This Error Does Not Tell You

The message does not, by itself, establish why a path is unavailable, whether data was permanently deleted, or whether permissions are correct. A permission issue is often reported separately, but the precise behavior depends on the operating system, the operation, and what information the process can see. Likewise, changing permissions will not repair a misspelled path or recreate a missing directory.

Do not create a file merely to silence the error until you know what the program expects. The missing path could be an important configuration file, a removable drive, or a directory that should be supplied by another part of a workflow. If the file may contain valuable data, check backups, trash or recycle locations, and the correct storage device before attempting recovery actions that could overwrite data.

Frequently Asked Questions

Does “No such file or directory” mean the file was deleted?
No. It means the path could not be resolved in the process’s current context. The file might be elsewhere, the path may be wrong, or a parent folder, link target, or mounted device may be missing.

Why does a file exist but the command cannot find it?
The command may be running from a different working directory, using different capitalization, or interpreting spaces and special characters differently. Try the file’s exact absolute path and check the directory from which the process runs.

Why does this happen when I run a script?
A script may use relative paths, and its working directory is not necessarily the script’s own folder. It may also expect an input file, executable, or configuration directory that is absent from the environment where it runs.

Is this the same as “Permission denied”?
No. “No such file or directory” generally points to an unresolved path. “Permission denied” generally means the requested item or operation was found but access was not allowed. Read the exact message and check both path and access if the situation is unclear.

How do I check whether a path exists?
On Linux or macOS, inspect it with commands such as ls and check your location with pwd. On Windows, use dir and inspect the current directory with cd. For application code, use the language’s file-existence or file-opening functions and handle failures explicitly.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.