Guide
What is digital asset management?
A DAM system is where an organisation’s files live: findable, access-controlled and accounted for. This is what one actually does, what it costs, and how to tell whether you need one.
What a DAM system is
Digital asset management is a system for holding an organisation’s files so they can be found, shared under control, and accounted for. Software, plus the conventions you agree to run it by.
The word "asset" is unhelpful — it sounds like finance. In a DAM system an asset is a file: a photograph, a video, a logo, a PDF, a presentation. Most systems accept any file type. What differs is how well each one is handled.
Video needs its own metadata fields, like a shot list. PDFs are worth running through text recognition on upload, so a keyword search reaches inside them. A system that treats every file as an anonymous blob will technically store your archive and practically lose it.
What separates a DAM system from a folder on a shared drive is that it knows things about each file — who is in it, what it may be used for, who may see it, where it has been used — and can answer questions on that basis.
Why it matters
Two reasons, and they pull in different directions.
The first is preservation. An archive is the record of what an organisation did and why, and usually it is the only copy. Hard drives fail, staff leave with the context in their heads, and files scatter across servers, laptops and inboxes until nobody can say what exists. That is what an unmanaged archive actually costs, and a DAM system is where it stops.
The second is that safe storage on its own is worth very little. An archive nobody can search is a cost with no return. The value arrives when somebody looking for one specific photograph finds it in seconds, when the right people can reach it and the wrong ones cannot, and when you can say what happened to a file after it left.
Consent, access control, workflow, collaboration between teams and integration with the systems you already run are all part of the same job — and the things worth pressing a supplier on.
How a DAM organises files
Two mechanisms: structure and indexing. Neither works well without the other.
Structure is hierarchy — libraries, folders, subfolders. It should behave the way folders on a desktop behave, because that is the model everyone already has. Structure gets you to roughly the right place.
Indexing is tagging, and it is what gets you to the exact file. Tags are what a search actually matches on, which makes keywording the least glamorous and most valuable work in an archive. A controlled vocabulary helps: LightRocket ships a thesaurus of 40,000 terms with synonyms and alternate forms, so a batch can be tagged consistently rather than however the person doing it phrased things that day.
AI tagging is genuinely useful and genuinely limited. It reads what is literally in the frame. Shown two children holding hands it offers "children" and "hands"; it does not offer "friendship", and it does not know whether they are siblings. Use it to get a first pass done, not to replace the person who knows what the picture is of.
What the tools do
Inside a DAM system, the tools are the specific things you do to files: adding and editing metadata, tagging, setting who can see what, managing consent, sharing outside the organisation, and reporting on any of it.
On a features page every supplier looks similar. The differences show up in use. Ask how metadata editing works across a batch of a thousand files rather than one. Ask what happens to existing metadata when a change is applied — whether it is added to or overwritten.
Ask what the system integrates with, and be honest about which of those you will actually use. A long list is not the same as the two that matter to you.
A DAM system is usually a decision you live with for years, so how often the supplier ships changes matters about as much as what the system does today.
Keeping an archive secure
Zero risk does not exist. Security is about knowing what you are exposed to and reducing it continuously, because the threats keep changing.
Most DAM suppliers now run on Amazon Web Services, which is designed for eleven nines of object durability — for every ten million objects stored, an average loss of one object every ten thousand years. That covers hardware failure. It does not cover everything, which is why disk snapshots and database backups still matter.
The rest is people and practice: whether the supplier has anyone whose actual job is security, what their record is, and how access, sharing and downloads are controlled and logged inside the system. Most real incidents are about who could reach a file, not about a disk dying — which is why security is a moving target rather than a box you tick once.
What a DAM system costs
Pricing in this market is unusually opaque. Getting to a number is mostly a matter of knowing what to ask.
- Work out what you need. How large is the archive, and what are the files for — brand assets, editorial, campaigns, a permanent record?
- Size the usage. How many people need access, and in what roles? How much new material arrives each month?
- Shortlist three suppliers and compare them on price against your actual scale, not their example one.
- Ask for a live demonstration and a test system. Look at how it behaves with your kind of files, not their showcase.
- Weigh the support. A DAM system is a long relationship, and after-sales service is most of what you are buying.
Two things to watch. Per-user pricing works against the point of the system, which is that the archive is worth more the more of the organisation can reach it. And ask for a written breakdown of what is included — storage, backups, AI features, integrations, support — because that is where the add-ons hide. We put our own pricing next to the market’s if you want a starting point.
Where AI actually helps
Most of what a DAM system holds is a record of something that happened, and those files should not change. Their value is that they are evidence.
AI is useful around the edges of that. Visual search works well. Automatic tagging gets a first pass done on a large batch. Facial recognition, applied carefully, groups every photograph a person appears in — which is what makes consent checking practical at scale rather than theoretical.
What it does not do is understand what a picture means. It reads objects, not symbolism, relationships or context — the limits are worth knowing before you buy on the strength of them. Treat AI as a way to make a person faster, not as a replacement for one, and read the longer argument if you are being sold otherwise.
DAM, MAM, CMS and CRM
Four acronyms that overlap enough to cause trouble.
| System | What it is for | Where it stops |
|---|---|---|
| DAM | Storing, organising and controlling access to files of any type | Not a website, and not a sales tool |
| MAM | The same job, specialised for video, audio and multimedia | Narrower on everything else |
| CMS | Publishing content to a website | Holds the files a page needs, not the archive behind it |
| CRM | Tracking contacts and sales | Not a file system at all |
MAM came out of broadcast, where the problem was moving very large video files through production at speed. DAM systems have since absorbed most of that while handling documents, presentations and images as well, which is why broadcast teams increasingly buy a DAM.
DAM and CMS get confused because both hold content. A CMS pushes pages to the web; it is not built to be the permanent record. The useful arrangement is a DAM that integrates cleanly with your CMS, rather than either pretending to be the other. The same goes for cloud storage, which is a different tool wearing a similar shape.
Within DAM there is a further split. Some systems are really brand asset managers, built around marketing collateral and templates. Those are a poor fit for a large institutional archive that needs careful classification, high-volume ingest and a defensible record of use.
What to look for
Six things worth settling before you sign anything.
How many people can use it
Per-seat pricing works against you: an archive is worth more the more of the organisation can reach it. Check whether users are capped, and what the next tier costs.
How much you can store
Archives grow faster than anyone plans for. Find out what happens when you pass your allowance, and what expanding it costs.
What is not in the price
Ask for the list of what counts as an add-on — storage overage, AI features, integrations, extra support. The fine print is where the surprise lives.
Who builds it
You are buying a relationship as much as software. What is the supplier’s background, how long have they done this, and who answers when something breaks?
Whether the features match your work
Walk through your actual workflow with the supplier rather than reading their features page. If something you need is missing, ask whether they would build it.
What support and training you get
A DAM system takes time to learn properly. Avoid anything sold as plug-and-play, and find out whether support means a person or a ticket number.
There is a longer version of all six in four things to consider when buying a DAM system and in how to choose one that works for you.
Moving an existing archive across
Migration is the part organisations dread, and the part a supplier should absorb. It is less of an ordeal than its reputation suggests.
It starts with an assessment: how much data, which file types, and where it currently sits — hard drives, a server, a previous supplier. Then an audit of what metadata already exists.
If the files carry standard IPTC or XMP metadata, which is what Photoshop, Lightroom and Photo Mechanic write, the move is largely mechanical and the new system reads what is already there. If the metadata is non-standard, it gets mapped from the source fields onto the target ones. Either way that is work the supplier does.
The thing worth insisting on is that nothing is lost in translation. An archive that arrives without its metadata has arrived as a pile of files. The step-by-step version is here.
Who needs one
Any organisation with an archive that has to be kept, found and shared under some degree of control. That is a wider group than it sounds.
Museums, galleries and archives, where the collection is the institution. Schools and universities, where images of students carry consent obligations. NGOs and international bodies, which document their own work and depend on it for communication and fundraising. Photo agencies and broadcasters moving high volumes to deadline.
And most companies that make and sell things: product photography, marketing collateral, images of work in progress, brand assets. The archive exists whether or not anyone is managing it — which is why a DAM is the platform most organisations never knew they needed.
The question is not really whether you have digital assets. It is whether you could produce one particular file, with its permissions, this afternoon.
Where this works in practice
Four archives at very different scales, and what changed once they were governed.
European Broadcasting Union
Powering Eurovision's Media Operations with LightRocket's DAM
See how the EBU used LightRocket's DAM to power secure, real-time media workflows for Eurovision 2025 at massive global scale.
Read the case study
World Health Organization (WHO)
Releasing the Value of a Global Health Archive
By partnering with WHO, LightRocket was quickly able to demonstrate the power & potential of our Digital Asset Management System. Read more in this case study.
Read the case study
SOPA Images
SOPA Images and LightRocket: How This Photo Agency Benefits from Digital Asset Management
LightRocket's digital asset management platform is the perfect fit for photo agencies. Here's how SOPA Images uses our DAM software to power their agency. Read more now.
Read the case study
Common questions
What does a DAM manager do?
They set the protocols the archive runs on: what may be uploaded, what metadata has to accompany it, who has access to what, and where the quality threshold sits. After that it is keeping an eye on incoming material, managing contributors, tracking usage, and being the person everyone asks. An eye for detail and some background in cataloguing or library science goes a long way. The role in more detail.
Is a DAM system different from cloud storage like Dropbox or Google Drive?
Yes, and the difference is not size. Cloud storage holds files and syncs them. A DAM system knows what is in each file, what may be done with it, who may see it and what has been done with it already. One is a place to put things; the other answers questions about them.
Can a DAM system handle files other than images?
It should. Photographs and video are what most archives are mostly made of, but documents, presentations, spreadsheets, audio and design files belong in the same place. Ask specifically how each type is handled rather than whether it is accepted — accepting a file and doing something useful with it are different claims.
How long does it take to get a DAM system running?
The system itself is available immediately; the work is the archive. A straightforward migration with standard metadata can be running in weeks. A large archive with inconsistent or non-standard metadata takes longer, because the mapping has to be got right once rather than fixed afterwards.
Do we need a DAM system if we already have a CMS?
Usually, yes. A CMS holds what your website needs today. It is not built to be the permanent record of everything the organisation has produced, and it has no view on consent, rights or internal access. The two work well together, with the DAM as the source and the CMS as one of the places files go.
Next step
Still working out whether you need one?
Tell us what you have and what you need to do with it, and we will tell you honestly whether we are the right fit.