Custom metadata is descriptive metadata an end-user adds to an asset after it is created, specific to how the organization searches and uses its assets. It is not the same as embedded metadata, which the creating software writes automatically; custom metadata is the deliberate, organization-specific layer.
Why it matters
Custom metadata is what makes assets findable in the language a team actually uses. Embedded metadata describes the file technically; custom metadata describes what the file is to the business, the campaign, the product, the approved channels, the rights terms. It is the layer that turns a generic file into a findable asset.
How it shows up in practice
A retailer adds location and subject to product photography, plus the channels each image is approved for and its licensing terms. A sports team adds the opponent, the play, and the player. Because users can add almost anything, custom metadata only works when it is governed by a taxonomy and a controlled vocabulary; applied ad hoc, it produces disorganized results that need cleanup. It is usually added by the creator, a librarian, or at ingestion, and increasingly proposed by AI and confirmed by a human.
Common mistakes
- Letting users invent fields and terms instead of governing them with a taxonomy.
- Adding it after assets are published, so it does not embed on the file.
- Capturing too much, so uploaders skip fields and accuracy drops.
- Failing to map custom fields to a standard like IPTC for portability.
Stacks covers it alongside embedded metadata in embedded vs. custom metadata.