A brand photo archive works when anyone on your team can find the right approved image, know what it may be used for, and trust that the original still exists. To get there, you need five things: one internal archive, a folder and naming system that never changes, metadata that carries rights, a backup routine you have tested, and a separate, controlled way to share. This guide walks through each, in the order you would build them.
TL;DR
- Keep one internal archive as the source of truth, and publish only approved images in separate client or team galleries.
- Use a durable project ID, ISO dates and a fixed file-name pattern. Consistency matters more than cleverness.
- Put creator, copyright, keywords and usage terms into the file metadata, not just a spreadsheet.
- Follow the 3-2-1 backup rule, back up the catalog too, and test a restore.
- Review the archive on a schedule: remove duplicates, close finished jobs, and expire rights that have lapsed.
Table of Contents
- Start with roles, not folders
- Separate originals, selects and finals
- Build a folder hierarchy that supports retrieval
- Name files so they sort and stay unique
- Put rights and context into metadata
- Protect the archive with backups you have tested
- Share without losing control
- Keep it clean: a yearly upkeep routine
- Our perspective
- Getting shoots that arrive archive-ready
- FAQ
- Sources
Start with roles, not folders
Most archives fail because nobody owns them. Before you create a single folder, decide who does what. One approach is to define roles for the library itself, for each campaign, for rights, for contributors and for the people who only consume images. That keeps standards in place without sending every request through one overworked person (Phil Halfmann).
A workable split for a small marketing team looks like this:
- Library owner: keeps the structure, naming and metadata rules, and approves changes to them.
- Campaign lead: assigns the project ID, signs off on selects and confirms what is approved.
- Rights contact: records license terms, territories and expiry dates for each shoot.
- Contributors: photographers, agencies and in-house staff who ingest files using the rules.
- Consumers: sales, social and PR staff who search and download approved images only.
Then separate two things that people tend to blur. The internal archive is for search and rights management. Client or team galleries are for controlled access and delivery. Build the internal collection first, then publish only approved or reviewable assets into a separate gallery with controlled access and downloads (Framesora).
Separate originals, selects and finals
The most common mistake in a brand archive is a single folder where raw captures, half-edited files and final exports sit together. Within each project, keep distinct, clearly labeled subfolders for original captures, working selects and finalized approved exports, each traceable to the project ID (SendPhoto).
A simple project layout:
2026-05_P0412_spring-trail-campaign/
01_originals/
02_selects/
03_edits/
04_approved-exports/
05_delivery-docs/
Three habits make this layout hold up:
- Originals are read-only. Nobody edits, renames or deletes files in the originals folder after ingest. Edits live in the catalog or in the edits folder.
- Exports are labeled by channel. A web hero, a print file and a social crop are different derivatives of the same image. Say which is which in the name or subfolder.
- Delivery documents live with the project. The approval email, the shot list and the license summary stay next to the files they describe.
When you commission outside photographers, agree on this structure in the brief. Our own guidance on what to hand over in editorial photo deliverables covers how selects, captions and rights notes should arrive so they slot straight into your archive.
Build a folder hierarchy that supports retrieval
Folders should answer one question: where does this belong? For a brand library, a hierarchy that supports retrieval follows this order: brand or business unit, year and season, campaign or launch, asset type, status, and channel derivative (Phil Halfmann).
For a brand with two product lines, that might read:
Trailwear/2026-SS/Spring-Trail-Launch/Photo/Approved/Web/
Do not make it deeper than your team will tolerate. The Society of Photographers advises that consistency across the entire hierarchy matters more than a perfect or complex system, because it keeps retrieval predictable no matter who commissioned the work (The Societies).
Also accept what folders cannot do. They are good for reliable storage and organization, but metadata gives you more flexible retrieval than a folder tree ever will (Framesora). An image can sit in only one folder, yet it may belong to a campaign, a product, a location and a season at the same time. Keywords and fields handle that. Folders do not.
Use a durable project ID
Give every shoot a project ID that never changes, and put it in both the top-level folder name and the catalog metadata. The ID links the archive to exports, invoices, approvals and client communications, and it separates campaigns with similar names (Framesora). If two spring campaigns share a title, the ID is what stops someone using last year’s licensed set.
Name files so they sort and stay unique
Naming rules are boring and powerful. Use human-readable names with letters, numbers, hyphens and underscores, and avoid special characters and punctuation. Put dates in reverse order, as YYYY-MM-DD or YYYYMMDD. That format comes from ISO 8601 and makes folders sort chronologically by name (Image Science).
For delivered and approved assets, a pattern that carries meaning works well: brand, campaign, subject, channel, orientation and version, for example trailwear_spring-launch_ridge-rider_web_landscape_v02.jpg. It replaces the “final-final-2” habit with something a stranger can read (Phil Halfmann). ASMP, the US professional association for photographers, also suggests unique file names, such as a numeric date plus the photographer’s name (ASMP Digital Photography Guide).
A few practical rules we would add:
- Write the pattern on one page and pin it where contributors will see it.
- Keep camera-original numbers in the originals folder. Rename on ingest with a batch tool, not by hand.
- Version with
v01,v02, never with words such as “new” or “latest”. - Keep names short enough that they are not truncated in the tools your team uses.
Names also matter outside the archive. If the same images end up on your website, descriptive file names help search engines and accessibility. Here, optimizing image file names and alt text makes a useful companion to your internal naming rule, as long as you keep the public name and the archive name linked through the project ID.
Put rights and context into metadata
A file name tells you what an image is. Metadata tells you who made it, who owns it and what you may do with it. Embed creator and copyright details, searchable keywords and license information in the file itself, so the information travels with the image (ASMP).
In Adobe Lightroom Classic, metadata presets can hold IPTC copyright details such as the copyright holder, usage terms and web address, plus IPTC creator fields. You apply them to one or many photos at ingest, so nobody types the same text again (Adobe).
A field list that serves a brand archive:
| Field | What to record | Why it matters |
|---|---|---|
| Project ID | The durable ID from the folder name | Links to invoices, approvals and briefs |
| Creator and copyright holder | Photographer or agency, and the owner | Proves authorship and ownership |
| Usage terms | Channels, media, territory, duration | Stops out-of-license use |
| Rights expiry | A date or “perpetual” | Drives your review routine |
| People and releases | Who appears, release on file or not | Avoids unreleased faces in ads |
| Location and date | Place name and capture date | Supports captions and search |
| Keywords | Product, activity, season, mood | Makes search flexible |
| Status | Draft, approved, retired | Separates usable from unusable |
Larger media operations go further, adding scene context, people, topics, locations, restrictions and approved use so that each asset is ready to answer a request (Vector Methods). You may not need that depth, but the principle holds: the more a stranger can learn from the file alone, the less your team depends on one person’s memory.
Rights need extra care. A license is only as good as your record of it. If you are unsure how to check what a photographer actually granted, our walkthrough on verifying image usage rights in the US shows the questions to ask before an image enters the approved folder. For sports and editorial material, the sports photography licensing workflow shows how those terms are tracked from request to publication.
Protect the archive with backups you have tested
A tidy archive on one drive is a single point of failure. The 3-2-1 rule, described in guidance from the US Cybersecurity and Infrastructure Security Agency, calls for three copies of your data, on two types of media, with one copy offsite (CISA). Photographers apply it to every file and keep RAW originals until the job is fully closed (imagic).
Three details separate a real backup from a hopeful one:
- Back up the catalog as well as the images. An editing database alone is not a copy of the photos, and the images alone lose your keywords and rights fields (SendPhoto).
- Keep one copy offline. CISA advises organizations to keep offline, encrypted backups and to test recovery regularly, because many ransomware variants look for and delete backups they can reach (CISA).
- Restore a real job. Periodically pick a finished project, restore it to a clean machine, and check the source files, catalog links and delivered versions (SendPhoto).
On event shoots the same logic applies in the field. Our piece on onsite event editing and the 3, 2, 1 backup rule shows how we protect files before the crew leaves the venue.
Share without losing control
Once the archive is solid, sharing is where it leaks. Editors, agencies and event teams need images fast, and the lazy answer is an email attachment or a shared drive open to everyone.
Better practice is per-link permissions, passwords and expiry dates, with external collaborators given access only to the specific projects, folders or files they need, and an audit trail to see who accessed what (Aspect). Keep RAW files in internal storage and upload only culled photos to the client gallery (picdrop).
Two more rules protect you:
- Hand off with documentation. A delivery note should list the approved files, the version or approval date, and any usage, territory, license or expiry limits attached (Content Cloud).
- Keep the master record. When a gallery is updated or retired, the authoritative record stays in your archive system (Framesora).
If your assets are tied to events, partners or sponsors, index by rights boundary too: owner, event, territory, rights window, partner segment, sponsor package or approved collection (Vector Methods). That makes the question “can the sponsor use this in Germany next spring?” answerable in seconds.
Keep it clean: a yearly upkeep routine
An archive decays unless someone maintains it. Duplicates pile up, drafts get mistaken for finals, and licenses quietly expire. Deduplication is an ongoing process, not a one-time job, and you should have a backup before you delete anything (The Family Archivists).
A routine that fits a small team:
| When | Task |
|---|---|
| At every ingest | Apply the metadata preset, assign the project ID, rename in batch |
| At job close | Mark the final status, archive the delivery note, remove rejected duplicates from selects |
| Quarterly | Run a duplicate check on the working areas, fix files with missing metadata |
| Yearly | Review rights expiry dates, retire expired assets, restore-test one project, check the naming rule still fits |
A few judgment calls help. Never delete originals just because a duplicate exists in an export folder; the export is a derivative. Mark expired assets “retired” instead of deleting them, so the history of what ran where stays intact. And when the structure no longer fits, change it once, document it and migrate, rather than letting two systems coexist.
Our perspective
We shoot for outdoor brands, editors and event organizers, and the archive problem usually shows up on the day after a shoot, not before it. A mountain bike campaign can produce thousands of frames in a few days, in several locations, for more than one channel. If the project ID, naming rule and delivery notes are agreed in the brief, the archive almost organizes itself. If they are not, someone spends weeks reconstructing what was shot, what was approved and what the license allows.
Our advice is plain. Decide the rules before the shoot, tell every contributor, and make the photographer’s delivery match your structure. Keep the rights information inside the files. And treat the original capture as the asset you are protecting, with everything else derived from it. A simple system that everyone follows beats a sophisticated one that only its designer understands.
— Martin
Getting shoots that arrive archive-ready
A good archive starts with how images are commissioned and delivered. If you are planning outdoor or adventure content, we can brief, shoot and deliver in your structure, with captions, metadata and clear usage terms. See our commercial photography services, or get in touch through our main site to discuss your project. For marketing teams preparing a shoot, the corporate photography checklist is a good place to start.
FAQ
What is the best folder structure for a brand photo archive?
Organize from the broad to the specific: brand or business unit, year and season, campaign, asset type, status and channel. Inside each campaign, separate originals, selects, edits and approved exports. Keep it only as deep as your team will actually follow.
Should I rely on folders or metadata to find images?
Use both, for different jobs. Folders give you reliable storage and a predictable place for each project. Metadata, such as keywords, project ID and usage terms, is what makes search flexible, since one image can belong to several campaigns or themes.
How many backups does a photo archive need?
Follow the 3-2-1 rule: three copies, on two types of media, with one offsite. Back up the catalog as well as the images, keep one copy offline, and restore a real project from time to time to prove the backup works.
How often should I review my brand photo archive?
Light checks belong at every ingest and job close. Run a duplicate check quarterly, and do a fuller review once a year to retire expired licenses, test a restore and confirm your naming rules still fit how the team works.
Sources
- How to Organize a Searchable Commercial Photo Library, Framesora
- Visual Content Library Management, Phil Halfmann
- How to Organize Photos: From Originals to Client Galleries, SendPhoto
- How to Organise Your Photography Archive, The Societies
- Naming Conventions and Folder Structures, Image Science
- Digital Photography Guide, ASMP
- Advanced metadata actions in Lightroom Classic, Adobe
- Media Rights and Licensing Workflow, Vector Methods
- Data Backup Options, CISA
- CISA MS-ISAC Ransomware Guide
- Photographer’s Guide to RAW File Management, imagic
- Share and Present, Aspect
- How to Manage a Large Client Photo Gallery, picdrop
- Creative Asset Management for Agencies, Content Cloud
- Deduplication: Streamlining Your Digital Photo Collection, The Family Archivists
- How to Optimize Images for SEO, Babylovegrowth
