Both categories store a lot of images, both let you search and tag, and both get pitched at "creative teams," which is exactly why the two get confused. The test that actually separates them isn't the number of files — it's whether more than one person's access to the same asset needs to be controlled.
What a DAM adds that a reference manager doesn't
A DAM is built around governance: permissions per user or role, an approval stage before something is considered final, version history that survives a revision going out and coming back, and usage-rights tracking for licensed or client-supplied material. Those features exist because more than one person touches the library and somebody has to be answerable for what gets published.
A reference manager has none of that, on purpose. It's built around one job — finding the picture you're thinking of, out of thousands you collected for research rather than for publishing — and adding a permission layer to that job would only slow it down for the one or two people actually using it.
Where the two overlap
Both index large numbers of images. Both let you tag, rate and search rather than scroll a folder. Some reference tools, Eagle among them, even import and manage a library the way a lightweight DAM would — Eagle's own documentation confirms it copies files into a managed library on import, which is closer to DAM behaviour than to indexing folders in place. That's a real design choice worth knowing about before picking a tool, and it's covered in full in the Coii Ref vs Eagle comparison.
A rough guide, not a hard rule
A few signals tend to line up with each category in practice, even though none of them is the actual test on its own:
- Team size. A DAM's permission system has nothing to configure with one user; a reference manager's search has nothing extra to offer once ten people need different access to the same file.
- What happens after the image is found. If finding it is the end of the job — you look at it, you draw from it, you move on — that's reference-manager territory. If finding it is the start of a publishing process someone has to sign off on, that's a DAM's job.
- Who paid for the asset. Licensed stock, client deliverables and commissioned work carry usage terms worth tracking formally. A reference photo you shot yourself or found for study doesn't.
None of these decide it alone — a five-person studio with no approval process is still squarely reference-manager territory, and a solo brand consultant juggling client usage rights might genuinely want a DAM's tracking even working alone.
The question that actually decides it
Not "how many images do I have" but "does anyone other than me need to be stopped from touching one of these." If the answer is no, a reference manager is the right shape of tool regardless of library size — see what one looks like built for a Mac. If the answer is yes, the features that matter are the ones a reference manager deliberately doesn't have, and no amount of tagging will substitute for them. Compare Coii Ref against Eagle directly if Eagle's managed-library approach is the one you're actually weighing, or see what else people move to when Eagle's library stops fitting.