
Capture One's Contact Sheets behavior changed between 16.7.3 and 16.7.4. The earlier update retained layout/settings and added branding options; 16.7.4 added persistence for uploaded cover, header and footer images. A remembered grid without its logo can therefore reflect a version boundary rather than a missing photo.
The official Contact Sheets documentation separates those changes. Check the installed version before assuming that every saved presentation setting includes its uploaded image assets.
Distinguish layout state from uploaded artwork
Record what was retained and what was lost. Page size, grid and spacing are layout choices. A cover image, header logo and footer graphic are supplied assets.
For a hypothetical studio proof, the same grid can appear with the wrong client's logo or without any logo at all. Neither state is corrected simply by selecting the photo thumbnails again.
The approved-version handoff guide explains why a reusable layout and a selected deliverable need separate identification. An automatically remembered presentation does not establish that its branding is appropriate for the next job.
Check the version before rebuilding the layout
Confirm the application release. The documented 16.7.4 change concerns keeping cover/header/footer images in place. Do not generalize that improvement into a claim that any external branding file can be recovered after deletion.
Open File > Export to Contact Sheet, or use the image context-menu command. Inspect the branding controls alongside the remembered layout. If the image assets need to be supplied again, use the actual approved artwork rather than trying to recreate it from an earlier proof thumbnail.
When moving between client jobs, inspect the assets even if persistence is working. Retaining yesterday's logo can be just as wrong as forgetting today's.
Proof the complete document
Scroll through the right-side preview, including the cover and later grid pages. Check header/footer placement and whether the selected images have the intended order.
A recognizable filename label can help a client refer to the correct photograph. The identifiable contact-sheet guide addresses that communication requirement in Lightroom; Capture One's branding persistence is a separate feature.
Do not let a polished cover substitute for checking the actual grid. A hypothetical proof can have correct branding and still omit an image, present the wrong sequence or show a misleading rating.
Verify the export rather than only the reopened dialog
Export a sample in the required format and open that artifact independently. Inspect the cover, page branding and image identifiers. Compare it with the declared client and job, not only with your memory of the previous dialog.
If the problem occurs on a release that should retain the assets, record the specific version and which image fields fail to persist. Preserve the supplied artwork while investigating; rebuilding every layout control makes the failure harder to isolate.
This is a version-specific presentation-state check, not a general archive or synchronization guarantee. The accepted result is the current job's correctly branded proof, and its layout and image assets should both be reviewed before sending.
Related tasks
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- Make a Lightroom Contact Sheet That Clients Can Identify
Sources and scope
- Contact Sheets: Selection order determines contact-sheet order;16.7.4 preserves uploaded cover/header/footer images.
Official Capture One documentation was read on October 23, 2026 (Asia/Shanghai). Examples and acceptance procedures are proposed, not hands-on test results. Verify installed-version and camera/edition support where applicable.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Mak Cézar / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.