Subjects and lessons to explore.

Law

Computer Literacy · Foundations

Files and Folders

9 min read 5 practice questions
10 key termsSourcesReport an error
Want it in plain words first? Jump to Eli explains — the same idea, no jargon.
On this page 9 sections
  1. In 30 seconds
  2. Why this matters
  3. The college version
  4. Eli explains
  5. Worked example
  6. Key takeaway
  7. Quick check
  8. Study tools
  9. Sources & references

In 30 seconds

A is a named collection of data saved as one unit — a document, a photo, or a program. A folder (also called a directory) is a container that holds files and other folders, so storage forms a branching tree with a single top called the . A is the text address that locates a file within that tree. Once you can tell a file from a folder from a path, organizing a computer stops feeling like guesswork.

Why this matters

Nearly every task on a computer — writing a paper, submitting an assignment, editing a photo, running a program — means creating, finding, or moving files. Students who understand the folder hierarchy and how paths work waste less time hunting for lost work and are less likely to overwrite or misplace it. The same mental model scales up: command-line tools, code projects, shared drives, and servers all organize data as files inside nested folders addressed by paths. Good naming and folder habits formed early make later coursework in any field, technical or not, noticeably smoother.

The college version

What a file is

A file is the basic unit a computer uses to store information on a disk or device. Each file has a name and holds a specific kind of content: a text document, a spreadsheet, a photograph, an audio clip, or the code of a program. The operating system keeps track of where each file's data physically lives and lets you work with it by name rather than by hardware location, so you can open, edit, copy, or move it as a single package. File-system documentation describes a filename as a base name plus an optional extension separated by a period, such as report.docx — the extension signals the file's type, a detail covered in its own lesson. The idea to hold onto here is that a file is one named, self-contained unit of data.

Folders and the hierarchy

A folder — equivalently a directory — is a container used to group files. A folder can hold files and also other folders, called subfolders, and those subfolders can hold folders of their own, as many levels deep as you need. Because containers nest inside containers, the whole collection forms a tree: a branching hierarchy that grows from one starting point at the top. That top is the root. On Windows each drive has its own root, such as C:\; on macOS and Linux the entire system hangs from a single root written as a forward slash (/), the arrangement standardized for Unix-like systems by the Filesystem Hierarchy Standard. Every file and folder sits somewhere on this tree, inside exactly one parent folder, and that single-parent structure is what makes orderly storage possible.

Paths: how a file is located

A path is the text address that says where a file or folder sits in the hierarchy. It lists the folders you pass through, separated by a special character, ending in the file's name. An (also called fully qualified) names the complete route from the root, so it identifies the file no matter where you currently are — for example C:\Users\Sam\Documents\essay.docx. A is shorter and is read from your current location, known as the : essay.docx means a file in the current folder, images\logo.png points into a , and two dots (..) mean go up to the parent folder. One naming detail differs by system: Windows separates path components with a backslash (\), while macOS and Linux use a forward slash (/). The concept is identical; only the separator character changes.

Working with files and folders

The everyday operations are create, open, rename, move, copy, and delete. Moving relocates a file to a different folder; copying leaves the original in place and makes a duplicate elsewhere; renaming changes only the name, not the contents or location. Delete deserves special attention, because on a personal computer deleting a file usually does not erase it right away. Windows moves it to the Recycle Bin and macOS moves it to the Trash, where it stays and can be restored to its original place until you empty that container. Emptying the Recycle Bin or Trash is the step that actually removes the file. This two-stage design is a deliberate safety net against accidental loss, and it is worth knowing so you neither panic over a deletion you can undo nor assume a file is gone when it is still recoverable.

Organizing and naming well

Because you decide the folder structure, a little planning pays off. Keep related files together — one folder per course, project, or year — and use subfolders to break large groups into smaller ones instead of piling hundreds of files into a single place. Give files clear, specific names that will still make sense months later; a name like biology-lab3-2026-02.docx tells you far more than doc1.docx. Consistent names also sort predictably, so dating files or numbering them keeps a folder in a sensible order. Avoid characters the system reserves for other purposes, and do not rely on remembering where something is instead of putting it where it belongs. Good structure is not decoration: it is the difference between finding a file in seconds and losing an afternoon to searching.

Eli, the EliExplains learning guide

Eli explains

The same idea, in plain words

Explain it like I’m 10

Picture a big filing cabinet. The whole cabinet is your computer's storage. Inside are drawers, and inside each drawer are folders, and you can put smaller folders inside those. The actual papers — your essay, your photo, your song — are the files. A folder is just a container; a file is the thing with content in it. To tell a friend exactly where one paper is, you would say which drawer, then which folder, then which paper. That set of directions is the path: a list of every container you open, in order, to reach the file.

Picture it like this

A file path is like directions to a specific book in a library: go to floor 3, aisle H, shelf 4, the third book — each step narrows down where the book sits until only one place is left.

Where the picture stops working

The library analogy breaks down in two ways. A real shelf runs out of room and you cannot easily nest shelves inside shelves, but digital folders can hold other folders essentially without limit. And a physical book sits in exactly one spot, while a computer can also make shortcuts or links that point to the same file from several places without copying it.

Worked example

Suppose Sam is writing a history paper. The file lives at the absolute path C:\Users\Sam\Documents\History\paper.docx. Read from the root, that route is: drive C:, then the Users folder, then Sam, then Documents, then the History folder, and finally the file paper.docx. If Sam is already working inside the History folder, the relative path to the same file is just paper.docx, because the current directory supplies the rest of the route. A chart stored in a sibling subfolder named images would be reached from the History folder as images\chart.png, and a references file one level up in Documents as ..\references.txt, where the two dots mean the parent folder. Same file, two ways to name its location: absolute from the top, relative from where you stand.

Key takeaway

A file is a named unit of data, a folder is a container that nests to form a tree rooted at a single top, and a path is the address that locates a file within that tree — absolute from the root or relative from where you are.

Quick check

3 questions here, of 5 in this lesson’s practice set. Answers stay hidden until you check.

Question 1 of 3foundational

Which statement best distinguishes a folder from a file?

Choose an answer, then check it.
Question 2 of 3intermediate

In a file system, the single top-level point from which all other folders branch is called the:

Choose an answer, then check it.
Question 3 of 3intermediate

A file is stored at C:\Users\Lee\Documents\notes.txt. Which statement about this is correct?

Choose an answer, then check it.
Practice all 5

Keep learning

Ready to build on this? Continue to the next lesson.

Practice this lesson
Study tools & related lessonsYou’ll learn to · Common mistakes · Easily confused · Key vocabulary · Related

You’ll learn to

  • Define a file, a folder, and a file path in your own words.
  • Distinguish a file from a folder and explain how folders nest to form a hierarchy with a single root.
  • Explain the difference between an absolute path and a relative path.
  • Apply the create, move, copy, rename, and delete operations, and predict where a deleted file goes.
  • Evaluate a folder structure and naming scheme for how easily files can be found.

Common mistakes

  • Treating 'file' and 'folder' as interchangeable words.

    A file holds content and is opened to be read or edited; a folder holds no content of its own — it is a container for files and other folders. Confusing them makes paths and organization impossible to reason about.

  • Believing that deleting a file erases it immediately and permanently.

    On a personal computer, deleting usually moves the file to the Recycle Bin (Windows) or Trash (macOS) first, where it can be restored. It is removed only when you empty that container.

  • Confusing an absolute path with a relative one.

    An absolute path starts from the root and works from anywhere; a relative path is read from your current directory and can point to different files depending on where you are.

  • Assuming every system separates path components the same way.

    Windows uses a backslash (C:\Users\Sam), while macOS and Linux use a forward slash (/Users/Sam). It is only a naming convention — the underlying idea of a nested hierarchy is the same.

  • Saving everything into one folder with vague names like doc1, doc2, final, finalfinal.

    Group related files into clearly named subfolders and give files specific, dated or numbered names so they sort predictably and stay findable months later.

Easily confused

File vs. Folder

A file is a named unit of data with content you open; a folder is a container that organizes files and other folders and has no content of its own.

Absolute path vs. Relative path

An absolute path names the full route from the root and works from anywhere; a relative path is measured from the current directory and is shorter but location-dependent.

Folder vs. Path

A folder is one container in the hierarchy; a path is the whole sequence of folders (ending in a filename) that locates a specific item.

Key vocabulary

File
A named collection of data stored and handled as a single unit, such as a document, image, audio clip, or program.
Folder (directory)
A container that groups files and can also contain other folders; the file system treats it as a special kind of file.
Subfolder
A folder located inside another folder, used to break a large group of files into smaller ones.
Hierarchy (tree)
The branching structure formed when folders nest inside folders, with each item having exactly one parent.
Root
The single top of the file hierarchy from which every other folder branches (a drive root like C:\ on Windows, or / on macOS/Linux).
File path
The text address that specifies where a file or folder is located within the hierarchy.
Absolute path
A path that names the complete route from the root, identifying a file regardless of your current location.
Relative path
A path read from the current directory rather than the root, often using '..' to mean the parent folder.
Path separator
The character between components of a path: a backslash (\) on Windows and a forward slash (/) on macOS and Linux.
Current directory
The folder you are working in at a given moment, which is the starting point a relative path is measured from.

Sources & references

  1. Naming Files, Paths, and Namespaces — Microsoft Learn (Win32 apps documentation)
  2. Dealing with files — MDN Web Docs (Mozilla)
  3. Filesystem Hierarchy Standard 3.0 — The Root Filesystem — The Linux Foundation
  4. Delete files and folders on Mac — Apple Support (macOS User Guide)

EliExplains lessons are original prose written from the open, credible references above. See Copyright & Licensing.

Researched 2026-08-19

Educational content only. It is not medical, legal or professional advice. Found an error? Tell us.