Short answer
Faceted search lets users narrow results by selecting values in several independent metadata fields at once. Facets replace folder browsing as the main way to find assets. Faceted search works only when facet fields use controlled vocabularies, because free-text values split one concept into many separate filter entries.
How faceted search works in a DAM
Faceted search works by turning metadata fields into filters that users combine in any order. Each facet shows its values with a count of matching assets, and the counts update after every click.
Four rules govern most DAM faceted search:
- Values within one facet combine with OR, so Web plus App returns assets for either channel.
- Facets combine with AND, so Brand A plus Packshot returns only Brand A packshots.
- Date and number facets use ranges, such as a shoot date within the last 12 months.
- Permissions apply to the counts, so external users see only the assets they may access.
Facets work alongside keyword and semantic search. A user types a query, then narrows the result with facets until a short list remains.
Example of faceted search
Worked example: a marketplace manager needs a current packshot of one product in WebP. She types the product name, then selects Brand, Asset type: Packshot, Year: 2026 and Channel: Marketplace.
Four clicks narrow the result to the approved images for that product. In a folder structure, the same manager would open the brand folder, the season folder and the product folder, then check file names one by one.
Faceted search in a DAM selection
Faceted search is proven at Checkpoint 5: Test, the stage where this glossary term sits on the Selection Route. DAMSelection assessment: generic vendor demos carry no selection value, because a demo library with perfect metadata makes every facet look fast.
Load your own assets with your own metadata into each demo, then test:
- Find a named asset within three filters, timed with a real user.
- Add a facet on one of your custom fields without vendor engineering.
- Show different facets per asset type, such as video duration for video only.
- Log in as an external user and confirm the counts hide restricted assets.
- Combine a facet with a semantic search query in one result.
The demo script generator builds these tasks into a scripted scenario. The demo script guide explains timing and scoring.
Common faceted search mistakes
The most common faceted search mistake is building facets on free-text fields. Other recurring errors:
- Showing 15 facets on one screen, which users stop scanning.
- Ignoring metadata completeness, so assets with empty fields drop out of every filter.
- Testing on the vendor's sample library, which hides the gaps in your own metadata.
- Facets that mirror internal team names that external users do not recognise.
Related terms: Taxonomy, Semantic search.
Frequently asked
What is the difference between faceted search and semantic search?
Faceted search filters assets on exact metadata values, such as brand or year. Semantic search ranks assets by meaning and visual similarity to a query. Most DAM users combine both: a semantic query finds candidates, and facets enforce brand, rights and channel rules.
How many facets should a DAM show?
A DAM should show the facets each user group needs, usually per asset type and per role. DAMSelection rule of thumb: show five to eight facets by default and hide the rest behind a 'more filters' option. Review facet use in search analytics after go-live.