Improve Capture One

Request a new feature, or support for a camera/lens that you would like to use in Capture One.

Add a new idea Subscribe
Status Awaiting review
Workspace Feature requests
Categories Capture One Pro
Created by Tim Trautmann
Created on Mar 31, 2026

RELATED IDEAS

XMP-dc:Identifier / ImageUniqueID Support in Metadata Pane and Search

I'm writing to request support for two related metadata fields that are central to a UUID-based photo identification system I've built around Capture One: XMP-dc:Identifier and ImageUniqueID.

Background

I've developed a toolchain that assigns a persistent, globally unique identifier (UUID) to every image in my catalog — both to the RAW/JPEG files via the EXIF ImageUniqueID field and to XMP sidecar files via XMP-dc:Identifier. The same UUID appears in both locations, just formatted differently (550e8400e29b41d4a716446655440000 in EXIF and urn:uuid:550e8400-e29b-41d4-a716-446655440000 in XMP). RAW+JPEG pairs that share a base filename are deliberately assigned the same UUID, and exported derivatives carry that UUID forward — creating a true, durable identity chain from capture to delivery.

Capture One is at the center of this workflow, but currently has no visibility into these fields.

What I'm Requesting

  1. Metadata Pane Display — Expose XMP-dc:Identifier (and ideally ImageUniqueID) as readable fields in the Metadata panel. Read-only display would be sufficient; I'm not asking for Capture One to generate or manage these values — just to surface them so they're visible alongside the rest of a file's metadata.

  2. Search / Filter Support — Allow filtering or searching the catalog by XMP-dc:Identifier or ImageUniqueID value. The primary use case is looking up a specific image by its UUID — for example, when an external system (a website CMS, a licensing database, or a delivery receipt) references a photo by ID and I need to locate the source file in Capture One quickly.

Why This Matters

Both fields are well-established standards. XMP-dc:Identifier is part of the Dublin Core XMP namespace, and ImageUniqueIDis a standard EXIF tag. ExifTool reads and writes them reliably, and many DAM systems support them natively. Adding display and search support in Capture One would make it possible to close the loop between catalog originals and anything downstream — exports, licensed copies, published images — without leaving the application.

This would be particularly valuable for photographers managing large archives or licensing workflows where traceability between source files and derivatives is important.

Thank you for considering this. Capture One is the cornerstone of my imaging workflow, and I'd love to see it grow in this direction.

  • Post comment