A collection is a curated grouping of assets that exists independently of where the underlying files are stored. Its members are chosen by hand; the criteria-based counterpart, whose membership is a rule not a choice, is a saved search. The same photo can appear in a campaign collection, a product collection and a press-kit collection at once — without being copied three times, because the collection references the asset rather than holding it.
In plain English
A folder answers the question "where does this file live?" — and a file can only live in one place at a time. A collection answers a different question entirely: "what set of assets belongs together for this purpose?" That's a reference-based grouping layered on top of storage, which is why the same asset can sit in a dozen collections simultaneously without a single duplicate on disk.
This distinction is one of the clearest lines between tools built around folder-thinking and tools built around metadata-thinking. A folder-first tool forces you to either duplicate a file so it appears in two places, or accept that it only lives in one. A collection-first tool lets a single, authoritative master asset be assembled into as many purpose-built groupings as a team needs — which is exactly what a single source of truth requires in practice.
Collections are also frequently the unit that other DAM features operate on. Permissions can be scoped to a collection rather than a folder, so a partner sees exactly one curated set and nothing else. An approval step can gate a whole collection before it goes out. And a share link or branded external portal is very often just a collection, wrapped in a theme and pointed at someone outside the organization.
Why it matters in a DAM
Whether a DAM's collections are genuinely reference-based, or just relabeled folders, determines whether a growing library stays coherent or slowly accumulates near-duplicate copies of the same asset. It also determines how naturally the tool supports the things teams actually do with assets: curating a campaign set, scoping a partner's access, gating a batch through approval, or publishing a press kit.
Buyer’s test: add the same asset to two different collections during a trial, then check the library's total asset count and storage usage. If either goes up, the tool is duplicating the file rather than referencing it — which means "collections" are really just folders under a friendlier name.
Related terms
See it in action
Our best brand portal software ranking tests how tools turn a curated collection into a polished, permission-scoped space for people outside the organization.
FAQ
What is a collection in a DAM?
A collection is a curated grouping of assets that exists independently of where the underlying files are stored. The same photo can appear in a campaign collection, a product collection and a press-kit collection at once, without being copied three times - the collection references the asset rather than holding it. Its members are chosen deliberately, by hand, which is what makes it curation rather than filing.
How is a collection different from a folder?
A folder is where a file physically lives, so an asset sits in exactly one folder. A collection is a reference-based grouping layered on top, so one asset can belong to any number of collections simultaneously. Tools built on folder-thinking rather than collection-thinking force you to duplicate files to appear in two places at once, or to accept that a file lives in one place only. That distinction is one of the clearest lines between storage-first and metadata-first tools.
How is a collection different from a saved search?
Membership. A collection's members are chosen by hand, so it contains exactly what someone put in it and nothing else. A saved search's membership is a rule, evaluated fresh each time, so anything matching the criteria joins automatically and anything that stops matching drops out. Use a collection when the set is an editorial decision - these twelve images for this press kit. Use a saved search when the set is a definition - everything tagged autumn campaign and approved.
Does adding an asset to two collections duplicate the file?
In a properly built tool, no - that is the entire point of a reference-based grouping. It is also easy to verify: add the same asset to two collections during a trial, then check the library's total asset count and storage usage. If either goes up, the tool is copying the file rather than pointing at it, which means its collections are really folders under a friendlier name. Duplication here quietly undermines the single master asset a DAM exists to maintain.
What else do collections get used for besides curation?
Collections are frequently the unit other features operate on. Permissions can be scoped to a collection rather than a folder, so a partner sees exactly one curated set and nothing else in the library. An approval step can gate a whole collection before it goes out, rather than asset by asset. And a share link or a branded external portal is very often just a collection wrapped in a theme and pointed at someone outside the organization. Collection quality shapes more of a DAM than it first appears.