A lot of file confusion comes down to one thing: not knowing where a file physically is. It was opened from an email, or found in a search, or it's in "Recent," and none of those are places.
Understanding paths fixes this permanently, and it takes about ten minutes.
What a path is
A path is the address of a file — the sequence of folders you'd click through to reach it.
On Mac and Linux:
/Users/laurie/Documents/Projects/report.pdfOn Windows:
C:\Users\laurie\Documents\Projects\report.pdfRead it left to right as a set of nested containers: the drive, then the user folder, then Documents, then Projects, then the file.
The differences are cosmetic. Mac and Linux use forward slashes and start from a single root; Windows uses backslashes and starts from a drive letter.
Drive letters versus mount points
Windows gives each drive a letter. C: is usually the internal drive, D: or E: might be an external drive or a network location. Two separate trees for two separate drives.
Mac and Linux have one tree. Additional drives appear as folders inside it — external drives typically at /Volumes/DriveName on a Mac.
This is why "which drive is it on" is an obvious question on Windows and a slightly hidden one on a Mac. On a Mac, a path starting /Volumes/ means an external or network drive; anything starting /Users/ is on the internal one.
The standard folders and what they're for
Every system creates the same set inside your user folder, and they have intended purposes people mostly ignore.
Desktop — files shown on your screen background. Intended for things in active use. In practice, the default dumping ground. A file on your desktop is in a folder called Desktop; it's not floating in space.
Documents — your files. This is the one that should hold your actual work, and the one worth structuring properly.
Downloads — where browsers put things. This is a transit area, not storage. Nothing should live here permanently, and everything eventually does. Empty it monthly.
Pictures / Photos — image files, and often the photo library.
Music, Movies/Videos — media, and where some applications keep libraries.
Library (Mac) / AppData (Windows) — application settings, caches, and support files. Hidden by default because you shouldn't need to go in there. Some applications store your actual data here, which is worth knowing when you're checking backup coverage.
What isn't a location
Three things in every file manager look like folders and aren't.
Recent / Recents — a list of files you've opened, pulled from all over the system. The file isn't "in" Recents. If you only ever open things from here, you'll never learn where anything actually is.
Search results — same. A view, not a place.
Tags and favourites — labels applied to files that live elsewhere.
"Shared with me" in cloud services — files in someone else's storage that you have permission to see. If they delete or move it, it disappears from your view.
The practical consequence: when you open a file from any of these and save it, you may not know where it went. Which is how files end up scattered.
Finding out where a file actually is
Every system has a way to reveal the true location, and it's worth learning:
Mac: select the file and press Command-I for info, which shows the path under "Where." Or right-click a file in Recents and choose "Show in Enclosing Folder." Or drag a file into Terminal to print its path.
Windows: right-click → Properties shows the location. Or right-click in a search result → "Open file location." The address bar in File Explorer shows the current path — click into it to see the text version.
On both: the title bar or the top of the window usually shows the current folder, and the breadcrumb trail above the file list shows the path.
Get in the habit of checking. "Where is this actually?" is the question that resolves most file confusion.
The email attachment problem
You open an attachment, edit it, and save. Where did it go?
Usually to a temporary folder created by the mail application, with a name you'd never find. Sometimes it's deleted when the mail app closes. Either way, the work is effectively lost.
The rule: save attachments to a real location before working on them. Save As, choose a folder in Documents, then edit. Every time.
The same applies to files opened from messaging apps, from cloud service web interfaces, and from anywhere that opens a file without you choosing where it lives.
Absolute versus relative paths
Occasionally useful to know.
Absolute — the full address from the root: /Users/laurie/Documents/report.pdf. Unambiguous.
Relative — relative to where you currently are: Projects/report.pdf means the Projects folder inside wherever you are now.
This matters in two practical situations:
Linked files in documents. Design files, spreadsheets with external references, and web pages link to other files. If the link is absolute and you move the whole folder to another computer, the links break. If it's relative and you keep the folder structure intact, they survive.
This is why "package" or "collect for output" functions exist in design software — they gather linked assets into one folder with relative references, so the project travels intact.
Path length, which breaks things
Windows has historically limited full paths to around 260 characters. Modern versions can exceed this and many applications still can't.
The symptoms are strange: files that can't be copied, moved, renamed, or deleted, with errors that don't mention path length.
Prevention: keep folder nesting shallow and names reasonably short. If you find yourself six folders deep with long names, restructure — the depth isn't helping anyway.
Deeply nested structures also break when moving files between systems, uploading to services, and creating archives.
Characters that cause problems
Never use: / \ : * ? " < > | — reserved by one system or another.
Avoid: leading or trailing spaces (invisible and confusing), multiple periods, and unusual symbols.
Spaces are fine on modern systems for everyday use, and they become %20 in URLs and need quoting in scripts. For anything web-facing, use hyphens.
Where your files actually live, checked
Worth doing once, deliberately. Open your file manager and answer:
- Where does my browser download to?
- Where does my camera or phone import to?
- Where does my photo library live? Is it on the internal drive or an external one?
- Where do my applications save by default?
- What's on my desktop, and is any of it the only copy?
- Do I have files on a second drive that my backup doesn't cover?
- Is my documents folder synced to the cloud, and do I know that for certain?
The answers frequently reveal a gap — a folder outside the backup, a library on a drive nobody thought about, a download location that's been filling for years.
Setting defaults so files stop scattering
Ten minutes of configuration:
Set your browser's download location to a folder in your structure, or at least know where it is and clear it monthly.
Set application default save locations to your documents structure.
Set your file manager to open at your documents folder, not at Recents.
Turn on file extensions, so you can see what things actually are.
Create a scratch folder for temporary work, so transient files have a home that isn't the desktop.
After this, files go where you intended by default, which is most of what file organization actually is.
The one habit worth building
When you save something, look at where you're saving it.
The save dialog shows the location, and most people click through it without reading. Reading it takes a second, and it's the difference between a structure and a scattering.
Next in this series: How to Set Up Automatic File Organization With Rules