How to Archive Old Projects on Mac (Without Losing Them Forever)

I once spent two days helping a former colleague track down a logo file from 2017. He had the project — somewhere — across three external drives, two Dropbox accounts, and a Time Machine backup that didn’t go back that far. We found it eventually, in a folder named New Folder (3) inside a folder named temp.

This is what a real archive system looks like — one that survives drives failing, software changing, and you forgetting where you put things.

What “archive” actually means

There’s a difference between a backup and an archive. Backups are about disaster recovery: a recent copy of your active work. Archives are about long-term preservation: stuff you’re done with but might need someday.

Backups churn — Time Machine overwrites old snapshots. Archives are static. Once filed, an archive shouldn’t change.

Both matter. Most people only have backups, which is why old projects end up lost.

The archive folder structure

The system that works long-term is dumber than people expect. Folders by year, then by client or project name. No tagging system, no database, no fancy software.

~/Archive/
  2023/
    acme-corp-rebrand/
    personal-photo-book/
    side-project-app/
  2024/
    nonprofit-website/
    book-cover-revisions/
  2025/
    [...]

Why this works:

• Year folders make it obvious which decade of drives the file is on
• Project names you can search with Spotlight or Finder
• Flat enough that nothing gets buried six levels deep
• Survives any Mac, OS, or app change — it’s just folders

Inside each project folder, keep it clean:

acme-corp-rebrand/
  source/             # native files (PSD, AI, etc.)
  exports/            # final deliverables
  reference/          # briefs, contracts, mood boards
  README.txt          # one-paragraph description

That README file is critical. Five years from now, you won’t remember what acme-corp-rebrand was. A 200-word description with dates, contacts, and what you delivered is gold.

Free up tens of gigabytesSweep finds the snapshots, caches, and old downloads adding up. Try Sweep free →

What to keep, what to ditch

Everyone’s first impulse is “keep everything.” Don’t. The point of an archive is being able to find the right thing when you need it. Keeping cache files and proxy media just means more to dig through.

Keep:

• Final delivered files (the actual outputs)
• Source files (PSDs, AIs, FCPX libraries, etc.)
• Original camera/scan files (you can always re-edit)
• Contracts, briefs, key emails (export as PDF)
• A README explaining what the project was

Skip:

• Cache and render files (regeneratable)
• Proxy media (regeneratable)
• “Old version” folders you made while working
• 50 incremental saves of the same file
• Slack/Discord/Teams chat exports unless legally required

A typical 6-month design or video project archives at 5–15% of its working size when you’re disciplined.

File formats that survive a decade

Software changes. Adobe drops formats. Indie apps disappear. Future-you needs files in formats that will still open.

Always export an additional copy in:

• PDF for any layout or design work — flat and layered if possible
• JPEG or PNG for any image
• MP4 (H.264) for any video
• WAV for any critical audio
• CSV for any spreadsheet data
• HTML or plain text for any document

Native formats (.psd, .ai, .fcpbundle, .sketch, .fig) might not open cleanly years from now. Always pair with an open format.

I’ve personally lost files in Aldus PageMaker, FreeHand, Microsoft Works, and AppleWorks. The PDFs from those projects still open fine.

Where to put the archive

Internal SSD: no. Archives shouldn’t live on the same drive you work on every day. SSDs do fail, and you don’t want both backup and archive on the same hardware.

Recommended setup for one person’s archive:

• Primary archive drive: external HDD (8–18TB), kept at home, plugged in monthly to add new archives
• Secondary archive drive: identical capacity, kept somewhere else (office, family member’s house, safety deposit box)
• Cloud copy: Backblaze B2 or AWS S3 Glacier for the truly important stuff

Two physical drives is the minimum. One drive is one failure away from total loss.

For larger archives (10TB+), a NAS with two-drive redundancy (Synology DS224+ or similar with mirrored 18TB drives) is more convenient than swapping externals.

Cleanup before archiving

Before moving a project to the archive, prune. This is the step everyone skips.

In Finder, navigate to the project folder. Apply these filters:

• Sort by size, look for files over 1GB you don’t recognize
• Search for ~$ (Microsoft Office temp files)
• Search for .tmp
• Look in any “Old,” “Archive,” or “Backup” folders inside the project — usually duplicate junk
• Delete .DS_Store files (cosmetic)

Adobe Bridge: clear caches before archiving. The cache lives separately and isn’t useful out of context.

Final Cut: consolidate all media into the library, then delete render files. File → Library Properties → Modify Settings.

Premiere/After Effects: collect files (File → Project Manager) to a clean folder, archive that, delete the original.

A 200GB project folder often archives at 30GB after this pass.

Verifying the archive worked

Don’t trust a Finder copy. Files can copy “successfully” while being silently corrupted.

Use one of these to verify:

• rsync -av --checksum source/ destination/ — slow but rock-solid
• Carbon Copy Cloner with checksum verification enabled
• ChronoSync with verify-after-copy

Or, after copying, generate hashes:

cd /path/to/source
find . -type f -exec shasum {} \; > ~/source-hashes.txt
cd /path/to/destination
shasum -c ~/source-hashes.txt

This actually compares every file. A 100GB project takes 10–20 minutes. Worth it.

Finding files years later

Spotlight indexes external drives, but only when they’re plugged in. Strategies for finding old work:

1. Keep a ~/Archive/index.md file on your Mac — a flat list of every project, year, and one-line description. Easy to search.
2. Use Finder tags consistently for project type (“logo,” “video,” “writing”) — searchable across drives
3. PDF every contract and brief; Spotlight searches PDF text
4. Name files descriptively; acme-logo-final-v3.ai beats Untitled-23.ai by an order of magnitude

If you’re searching for a file you can’t remember the name of, Spotlight’s date filters are your friend. Date last opened plus an approximate year narrows results fast.

Skip the manual huntSweep finds every cache, log, and forgotten file in seconds. Download Sweep free →

What to do when the archive grows huge

After 5–10 years, the archive gets unwieldy. A few options:

• Cold-er storage: move pre-2020 archives to a separate drive that lives in a drawer. Keeps the active archive smaller and faster.
• Compress: zip individual project folders. Loses some search-in-place but cuts size 20–40% for files that aren’t already compressed.
• LTO tape: for archives over 50TB, LTO-9 tapes hold 18TB each at low cost per GB. Drives are expensive ($3,000+) but tapes are cheap and last 30 years.
• Cull ruthlessly: every 5 years, look at archives 10+ years old and delete projects you genuinely don’t care about anymore. It’s hard but freeing.

A weekend setup

If you’ve never had an archive system, a weekend is enough to build one:

1. Buy two matched external HDDs
2. Format both as APFS or HFS+, name them “Archive A” and “Archive B”
3. Make the year-based folder structure on both
4. Move old projects from your Mac to “Archive A,” cleaning as you go
5. Mirror Archive A to Archive B with rsync or CCC
6. Set a quarterly reminder to add new archives and re-mirror

Once it’s running, it stops being something to think about. New projects archive when they’re done. Old ones are findable. The Mac stays clean.