
An archive needs clear project identity, original files, editing information and final deliverables. A folder named final alone is difficult to retrieve later, especially when you have dozens of projects and a faded memory of which one it was.

What to do
Collect the approved deliverables, record the editing software version where useful and retain the files needed to reopen the work. Verify the backup before moving or deleting working copies.
Name the project folder with a date, a client or subject, and a short descriptor. That alone makes it findable by browsing and by search.
What an archive folder should contain
- Originals: the untouched files from the camera, kept separate from edits.
- Edit data: catalog files, sidecar files or project files that hold your adjustments.
- Final deliverables: the exact files sent to the client, with version labels.
- A short notes file: project description, date, software used, delivery details and any special instructions.
- Licenses and agreements: a copy of the terms, if relevant to later use.
- Preview or contact sheet: a quick overview of the contents.
Keep the structure the same for every project, so you know where to look without opening each folder.
A mistake to avoid
Do not treat a catalog backup as proof that all original images are included. Test the files required to reopen a representative image. A catalog often stores edits only and depends on the originals being present.
A detail worth checking
Record any external dependency that matters to reopening the project. Fonts, linked assets or unavailable plugins can affect later work even when the original photographs are intact. Keep the archive understandable to a future reader.
Try this practical check
Pick one finished project and pretend you received a reprint request a year later. Find the original, final export and editing state using only the archive notes. If you struggle, improve the notes or the folder names.
Common questions
When is a project ready to archive?
After the client approves the delivery and your backup is verified, so you can safely tidy the working copies.
How many copies should I keep?
More than one, ideally in separate places, so a single failure does not lose the project.
Should I keep rejected images?
That is your choice. Many people keep them until delivery is complete and then decide based on space and project value.
Designing a Naming Scheme That Lasts
A good naming scheme is boring, predictable and easy to sort. Start with the date in a year-month-day order, because it sorts correctly in any file browser. Follow with a short project or client name and, if useful, a location or event. For example, a folder might begin with the date and continue with a short description. Use the same pattern every time so you can scan a list and understand it.
Keep names readable by people and safe for computers. Avoid special characters, accents and very long names, which can cause problems when moving files between systems. Use hyphens or underscores in place of spaces if you share files with others or upload to services that handle spaces poorly. Choose one style and stick with it.
File names within the project need a pattern too. You can keep the camera’s original numbering for raw files and add a prefix, or rename on import with a template that includes date and a sequence number. Edited exports can carry a suffix such as the size or purpose. Avoid names like “final” or “final2,” which become confusing. Instead use version numbers or dates. Write your scheme in a short text file kept in your archive root, so you remember it years from now.
Building a Folder Structure You Will Actually Use
A folder structure should mirror how you look for work. Many photographers use a top level by year, with projects inside, while others organize by client or topic first. Choose what matches your search habits, and avoid creating so many levels that files become hard to find. Two or three levels are often enough.
Inside each project, keep subfolders consistent. A simple set might include originals, selects, edits, exports and documents. Originals hold the untouched files from the camera. Selects contain the images you chose. Edits hold working files with layers or sidecar data. Exports hold the final files delivered or published. Documents hold contracts, release forms, shot lists and notes.
- Never edit the originals directly.
- Keep deliverables separate from working files.
- Store licensing and model release documents with the project.
- Leave a plain text note describing what is inside and any special handling.
If you use a catalog, make sure its structure still matches the file system. Moving folders outside the catalog can break links. Pick one place for organizing, and use the catalog’s own tools to move files so references stay intact. Test that you can find an old project quickly before you rely on the system. Review the structure once a year and tidy anything that has drifted, because small inconsistencies are easy to fix early and painful to untangle after hundreds of projects.
Metadata, Keywords and Rights Information
Metadata turns a pile of files into a searchable archive. At minimum, add your name and contact information to your copyright fields, and apply a consistent copyright notice during import. Keywords for subject, place and event allow you to find pictures without remembering the project. A short caption can be added to important images.
Use a limited, consistent vocabulary. If you tag one image “mountain” and another “mountains,” searches become messy. Create a short keyword list and reuse it. Add people’s names only if you have the right to do so and consider privacy before sharing images with embedded data. Be aware that location data can reveal where someone lives or works, so check what your export settings include before publishing.
Record rights details clearly. Note who owns the images, any usage limits in a client agreement, and expiry dates for licenses. Store model and property releases with the relevant project. If you work for a client, note what has been delivered and in what form. When a request arrives years later, this information saves you from reconstructing it from memory. Save metadata in a way that travels with the file, such as sidecar files or embedded fields, and test that it survives a move to another program before trusting it.
Storage Media and Long-Term Care
No storage device lasts forever, so plan for replacement. External hard drives, solid-state drives, network storage and cloud services each have strengths and weaknesses. Drives can fail or be dropped, cloud accounts can change terms, and formats can become hard to read. A good archive uses more than one type of storage in more than one location.
Check your storage on a schedule. Once or twice a year, open a sample of files from old projects to confirm they still open. Replace drives before they get old, following the maker’s guidance on expected life. Label drives clearly with contents and dates. Keep them in a cool, dry place away from strong magnets and moisture.
Consider file formats. Raw formats can change over time, so some photographers also save a converted open-format copy of important images. Keep exported finals in widely supported formats. Store the software version or notes about edits for complex projects. When you migrate to new storage, verify the copy by comparing file counts and sizes, or by using a checksum tool, before deleting the old one. Migration is a good moment to remove duplicates and clean up folder names. Write down where each backup lives and when you last checked it, so that a failed drive becomes an inconvenience rather than a crisis, and keep that note somewhere other than the drive itself.
Reviewing and Closing the Project
Closing a project properly saves time later. Begin with a checklist: all selects exported, deliverables sent and confirmed, invoices handled, releases stored, metadata applied and backups verified. Only after these steps should you mark the project as archived.
Make a small summary file for the project. Include the date, client, location, what was delivered, and any lessons. Add a line about editing choices that might matter later, such as color profile or export size. This note helps you or another person pick up the work again.
Decide what to keep and what to remove. Some photographers delete obvious rejects after a client has signed off, while others keep everything. Think about the cost of storage, legal needs and the chance that you will want alternates. If you delete, do it only after backups are verified. Create a final copy of the project folder in the archive location and confirm it opens. Update any catalogs or indexes so the project appears where expected. Finally, set a reminder to revisit your archive periodically. A project that is easy to find and easy to understand is worth far more than one stored carelessly. Over the long run, the habit of closing every project the same way is more valuable than any particular tool, because it keeps your archive predictable for anyone who needs to find something.
Common Questions
Should I rename my original raw files?
Many photographers rename on import with a template so names are unique and meaningful. Others keep camera names and rely on folders. Pick one method and use it consistently.
Is cloud storage enough for an archive?
It can be one part of a plan, but relying on a single service is risky. Combine it with local copies, and check the provider's current terms.
What is a sidecar file?
It is a small file stored next to a raw image that holds editing instructions and metadata. Keep it with the raw file when moving or archiving.
How do I archive files from a catalog?
Use the catalog's tools to move or export the folder with its edits, and check that the settings travel with the files. Back up the catalog file too.
Should I keep my edited files as well as exports?
Keeping working files with layers allows later revisions. If storage is tight, keep them for important projects and keep exports for the rest.
How long should I keep client projects?
It depends on your agreement and local requirements. Check any contracts and consider legal or tax guidance for your region.
Related reading
3-2-1 Backup Rule: A Simple Plan for Your Files (2026)
