Skip to main content

File Organization Strategies

A system that finds any file in seconds, years later

In This Lesson

Why Organization Pays Off

Editing skill means nothing if you can't find last month's project file, or you overwrite a final with a draft. A simple, consistent organization system saves time on every project, prevents lost and duplicated work, and makes handing files to a client or collaborator painless. The best system is the one you'll actually follow — so keep it simple and use it every time.

🎨 An Analogy

A darkroom kept negatives, work prints, and finals in separate, labeled boxes. Your hard drive needs the same discipline: masters, working files, and exports never mixed together.

A Folder Structure

Group by project, and within each project keep the same sub-folders every time so your brain always knows where to look:

flowchart TD P[2025_ClientName_Project] --> O[01_originals] P --> W[02_working_xcf] P --> E[03_exports] P --> A[04_assets] E --> EW[web] E --> EP[print]

A repeatable per-project structure: originals in, working files in the middle, exports out.

  • 01_originals — untouched source photos. Never edit these in place.
  • 02_working_xcf — your layered GIMP masters.
  • 03_exports — deliverables, split into web and print.
  • 04_assets — logos, textures, brushes specific to the project.

Naming Conventions

Good filenames sort correctly and describe themselves. A reliable pattern:

YYYY-MM-DD_project_subject_version.ext
e.g. 2025-06-14_wedding_portrait-03_v02.xcf
RuleWhy
Start with the date as YYYY-MM-DDFiles sort chronologically by name
Use hyphens/underscores, no spacesSafe across systems, scripts, and the web
Pad numbers: 03, v02So 10 doesn't sort before 2
Lowercase, no special charactersAvoids cross-platform and URL problems

💡 Descriptive Beats Clever

"final_FINAL_v3_realfinal.jpg" is the meme for a reason. A dated, versioned name tells you exactly what a file is at a glance and never collides with "final" again.

Masters, Working, and Exports

Keep three kinds of files strictly separate, as the pipeline from Monday demands:

  • Originals — the camera files. Read-only in spirit; copy before you touch them.
  • Working masters — layered XCF files, your editable source of truth.
  • Exports — flattened JPEG/PNG/TIFF deliverables, regenerated any time from the master.

⚠️ Never Edit Originals In Place

Editing and re-saving an original JPEG degrades it and destroys your only pristine copy. Import, duplicate into your working folder, and leave the originals untouched — they are your negatives.

Versioning

When an edit reaches a milestone — before a big change, before sending to a client — save a new numbered version (_v01, _v02) rather than overwriting. It costs a little disk space and buys you a safety net: you can always return to an earlier state even after flattening or heavy edits. Delete old versions only once the project is truly closed.

🎓 Save Before You Risk

Before any drastic, hard-to-undo step — flattening, a destructive filter, a major recompose — bump the version number. "v-before-flatten" has rescued countless editors from a change that looked great until it didn't.

Practice Activities

  1. Build the structure. Create the four-folder project template and copy a real shoot into it.
  2. Rename a batch. Apply the dated, versioned naming convention to a folder of files.
  3. Version up. Take a working XCF and save v01, make a big change, and save v02 — confirm you can reopen v01.

Summary

✅ Key Takeaways

  • A simple, consistent system saves time and prevents lost or overwritten work.
  • Use a repeatable per-project folder structure — originals, working, exports, assets.
  • Name files date-first, padded, no spaces so they sort and describe themselves.
  • Keep originals, XCF masters, and exports strictly separate; never edit originals in place.
  • Version up before risky steps rather than overwriting.

➡️ What's Next

Next, the data inside your files: Metadata and File Information.

Additional Resources