Files, Folders, and Paths

What you’ll be able to do

• Explain what a file actually is and how a folder differs from one
• Read a file path and know what it’s telling you
• Explain what a file extension does and why it matters
• Navigate Google Drive the way you’d navigate a folder tree anywhere else

Read

A file is not a document

A file is any single item stored on a computer: a document, an image, a video, a saved project. A folder (sometimes called a directory) doesn’t hold data itself. It holds other files and other folders, and it exists purely to organize things.

That distinction matters more than it sounds like it should. A folder named “Final” with nothing in it is meaningless. A file inside the wrong folder is genuinely lost, even though it still technically exists somewhere.

Nesting

Folders can go inside folders, as deep as you want. That’s called nesting, and it’s how every real project gets organized: a top-level folder for the class, a folder inside it for each project, maybe a folder inside that for reference images.

Nesting too shallow means one folder holding two hundred loose files with no structure. Nesting too deep means six clicks to reach anything. Somewhere in between is where real projects live, usually two to four levels.

Paths

A path is the full address of a file: every folder you’d click through to reach it, in order, written out as text.

GAD1/01_Projects/Lantern/lantern_v03.blend

Read left to right, each slash is one level deeper: the GAD1 folder contains 01_Projects, which contains Lantern, which contains the actual file. Software shows you a path constantly, in title bars, in save dialogs, in error messages, so being able to read one at a glance saves real time.

Extensions

The letters after the final dot in a filename are the extension, and they tell the computer, and you, what kind of file it is: .docx is a Word document, .png is an image, .mp4 is a video, .blend is a Blender project.

The extension is not decoration. It’s how your computer decides which program should open a file, and changing it does not change what’s actually inside the file. Renaming photo.png to photo.docx does not turn an image into a document; it just makes the computer try to open an image with Word and fail.

Windows hides extensions by default. Turning that display on (View → File name extensions in File Explorer) is worth doing, because it’s much easier to spot a naming mistake when you can actually see what you typed.

Google Drive works the same way, underneath

Drive looks different from a traditional file browser, but the same ideas apply. What Drive calls a folder is a folder. What looks like a flat list of files inside it is still a directory, with a path, even if Drive doesn’t always show you that path directly.

One real difference: a Google Doc, Sheet, or Slide deck doesn’t have a traditional extension the way a downloaded file does, because it lives natively in Google’s system rather than as a file with a .docx or .pptx ending. Export one of those as a Word or PowerPoint file, though, and it immediately gets a real extension, because now it’s a standalone file again.

Why this matters for a shared class folder

Once you’re sharing folders with a teacher, a team, or a client, structure stops being a personal preference and becomes something other people depend on. A well-organized project folder means anyone can find what they need without asking. A messy one means everyone, including you in three weeks, wastes time hunting.

Quick Check

Terms

• File
• Folder
• Nesting
• Path
• Extension
• Directory

Next

• Naming Conventions (COMP-105) — version numbers, underscores, and avoiding special characters
• File System & Naming Conventions Drill — organize your Drive workspace and practice professional naming standards