What is the difference between an absolute path and a relative path?

Think of a path as directions to a file. An absolute path starts from the filesystem’s root and identifies a location independently of the current directory. A relative path starts from a current location, so you need to know that starting point to know where it leads. [S1]

Here’s a small hypothetical folder tree:

/work/notes/plan.txt

If your current directory is /work, then /work/notes/plan.txt is an absolute path, while notes/plan.txt is a relative path that reaches the same file from /work.

But if your current directory is /work/archive, the relative path notes/plan.txt means /work/archive/notes/plan.txt, not /work/notes/plan.txt. The path text has not changed; its starting point has. That is the practical difference to keep in mind when copying commands or sharing instructions.

Assume this illustrative tree exists:

/project/ ├── data/ │ └── input.csv └── scripts/

The lines below assume a Unix-style filesystem and use /project as the root folder for this example; actual paths depend on the system and folders you have.

1. /project/data/input.csv — absolute: it starts at / and names the file from there.
2. data/input.csv — relative: from /project, it reaches the same file.
3. ../data/input.csv — relative: from /project/scripts, .. means the parent folder, so this also reaches the example file.
4. input.csv — relative: it reaches the file only if your current directory is /project/data.

Before relying on a relative path, identify the current directory your program, terminal, or instructions use. Some tools can choose their own starting location, so the folder you see in a separate window may not be the relevant one.

Choose based on what should stay the same:

1. Use an absolute path when the task must name one specific location regardless of the current directory—for example, when you are checking exactly which file a command refers to. The path must also match the machine and folder layout where it is used.
2. Use a relative path when the location should be found from a known project or working folder. For example, data/input.csv can describe a file within a project without writing the project’s full root location.
3. In instructions, state the starting folder alongside a relative path: “From the project folder, open data/input.csv.” If you do not know where the reader will start, explain how to identify or reach that folder first.

Here, “absolute” and “relative” describe the general distinction, not every platform’s full path rules. Python’s path documentation notes that path behavior varies by platform; for instance, Windows c:foo is not the same as c:\foo. [S1] The examples above do not establish how every application, operating system, or configuration handles a path. When in doubt, check the tool’s documentation and confirm the actual starting directory.

Use this short check, then try the path in the same context where it will be used:

1. Write down the intended file or folder.
2. Identify the starting directory for the command, script, or reader.
3. If the path is relative, join it mentally to that starting directory and check whether the result names the intended location.
4. If it is absolute, check that its root and folders apply in the environment where it will run.
5. In shared instructions, label the path style and state the starting folder when needed.

Copyable instruction template:

“Starting folder: [project folder]. Path: [relative path]. This should refer to: [intended file or folder].”

For an absolute path, you could instead write: “Path: [absolute path for this environment]. This should refer to: [intended file or folder].” Bracketed text is a placeholder, not a real location. These checks help clarify what a path is intended to mean; they cannot guarantee the location exists or that the reader has access to it.