How to organize digital assets so teams can find and reuse them
A practical system for agencies, marketing teams, and freelancers to organize files, versions, and rights without losing work.
Founder of Polimake, YouTuber.
An agency delivers a campaign containing 38 assets. Three months later, the client asks for the product photograph with the blue background. The photographer called it “DSC_4837.jpg”, design has a cropped copy on a desktop, and the approved version was shared through an expired transfer link.
The photograph exists, but to the team it may as well not.
A digital asset is not simply a file. It is a file people can find, understand, and legally use when they need it again.
What turns a file into an asset
For that campaign photograph to retain value, it should answer:
- Which client and campaign does it belong to?
- Is it an original, working file, derivative, or final?
- Who created it?
- Which version did the client approve?
- Where and until when can it be used?
- Does it include licensed people, music, fonts, or third-party material?
- Which deliverables and channels used it?
- Where is the master?
Context held only in a producer's memory disappears when they change projects or leave the team.
Folders cannot carry all the context
A client-and-campaign structure is a useful start:
Client / Campaign / 01_Originals / 02_Working / 03_Approved / 04_Deliverables
A photograph can still belong to client A, the summer campaign, the product category, and five published posts. A folder gives it one location. Metadata makes it discoverable through several contexts.
Use folders for broad order and fields or tags for client, campaign, asset type, product, channel, format, approval state, rights expiry, author, language, and market.
Do not add twenty fields on day one. Begin with information that changes a decision.
Use names people can read
Avoid “final_final_really-final_v7.jpg”. A useful name might be:
acme_summer_blue-shoe_feed_1080x1350_v03_approved.jpg
The name helps when files leave the platform. It should not carry every fact; that is what metadata is for.
Define your states as well: work in progress, in review, approved, published, and obsolete. “Final” should have one meaning.
Separate originals, working files, and deliverables
A campaign creates three families:
- Originals: camera footage, audio, illustrations, and received documents.
- Working files: Premiere, After Effects, Photoshop, Figma, or similar sources.
- Deliverables: MP4, JPG, PDF, and channel-ready adaptations.
Keeping only the deliverable makes later changes difficult. Keeping only the working file leaves clients without something usable. Preserve the relationship between all three.
Record rights before reuse
Approval does not automatically grant unlimited reuse. A photograph might be licensed for Spain for one year, music for organic social only, or a model for one campaign.
Record the rights holder, territories, channels, start and end dates, restrictions, and linked agreement. When rights are unknown, the state is not “free to use.” It is “verify before use.”
An example of reuse
A client needs a back-to-school campaign. The team filters last year's library for product “backpacks”, state “approved”, market “Spain”, rights valid after 1 August, and vertical orientation.
It finds 24 photographs and 6 clips that can be used. Design creates new variants without another shoot, and legal can see where every image came from.
That is the return from an asset library: less searching, less repeated production, and lower risk.
Start with one small cleanup
Choose one active client and its latest campaign. Gather originals, working files, and finals. Mark the approved version, add rights and five useful fields, then ask another person to find an asset without your help.
Use what you learn on the next campaign. Keep the context in a shared asset library and connect files to the project where they were requested and approved.
The goal is not to archive more. It is to let finished work keep producing value.