A digital asset manager, or DAM, is software a company uses to store its finished, approved assets — logos, packaging art, product photography, marketing video — in one place, with rules about who can see, edit or publish each one. It is built around control: version history, approval stages, usage rights and a permission system that keeps a contractor from touching a brand asset a legal team hasn't cleared.
What a DAM is actually solving
The job a DAM exists for only shows up once more than one person is responsible for the same library:
- Who is allowed to do what. A photographer can upload; a brand manager approves; a partner agency can view but not download the unwatermarked original.
- Which version is the current one. A DAM tracks that a logo went through four revisions and makes sure nobody downloads revision two by accident.
- What an asset is licensed for. Stock photography, client-supplied video and commissioned artwork often carry usage terms that expire or apply only to certain markets, and a DAM is where that gets attached to the file itself.
- A record of where an asset has been used, so a company can answer "is this still live anywhere" when a license lapses.
None of that is about finding a picture you remember seeing — it's about governing assets other people are allowed to touch.
What that costs, and why it's worth it for a team
Enterprise DAM platforms are priced and built for that governance job: per-seat licensing, admin consoles, integrations with a company's other publishing tools, and often a dedicated onboarding process before a team's existing library gets migrated in. None of that is padding — a brand team answerable for who published what genuinely needs an audit trail, and a per-seat cost is how that gets paid for. It's also why a DAM is the wrong tool to reach for before that need exists: the same features that make it answerable also make it slower to search and heavier to set up than something built around one person finding one file.
Where it differs from a reference library
A reference manager solves a narrower, more personal problem: one person (or a small team with no need for approval gates) collecting images and video for research and inspiration, and needing to find the right one again by what it shows. There's no publishing step, no legal clearance, and usually no second person whose access needs limiting.
~/Pictures/Reference- Competitor packaging
- Lighting studies
- coii-thumbnailswritten by Coii Ref
- coii-proxieswritten by Coii Ref
- coii.dbwritten by Coii Ref
Coii Ref sits on that side of the line. It reads the files already on disk, keeps its database inside the folder you point it at, and never asks who is allowed to open which image — because the entire point is that it's your folder, not a shared one with rules attached.
When the DAM label actually applies
If the honest answer to "who else needs to be stopped from changing this" is nobody, the tool being described is not a DAM regardless of how large the library gets. Scale alone doesn't make something enterprise software; a governance requirement does. The difference matters enough to lay out on its own page if you're trying to work out which category actually fits what you need — or see how Coii Ref's version of a personal library looks in practice, no account or approval step involved, free to try for 30 days.