Home / Data Merge Production / Data Merge Image Asset Matcher
Variable print · source preparation
Data Merge Image Asset Matcher
Reconcile image references before a merge: distinguish an exact file path from a case-only match, an ambiguous selection or a genuinely missing asset.
Files stay on this device. No upload or account required.
What this calculator solves
Variable-image jobs fail when the source table and asset delivery describe different files. A CSV may reference an old directory, the wrong capitalization or a filename that occurs in several subfolders. This matcher compares the selected image column with an explicitly supplied path manifest. It reports which records require attention before the compositor starts. Use it on product cards, event badges, school photographs and other jobs where several images share one artwork template. It is not a photo viewer, image converter or automatic relinking script.
How to choose the inputs
Choose the exact image header from the exported source, commonly @Image. Select the asset folder when the browser supports directory selection, or paste one relative asset path per line. Selecting a folder uses paths relative to that selected root: choosing a job folder containing photos/A.jpg produces photos/A.jpg, not the job-folder name. A file-only selection supplies basenames. For absolute CSV paths, enter the exact common root to remove, such as C:/Jobs/Badges. Manifest names are not trimmed or URL-decoded because those transformations could select a different real file.
How the calculation works
Backslashes are normalized to forward slashes, a leading ./ is removed, and repeated path separators are collapsed for comparison. The optional exact root prefix is then removed from CSV references. The matcher first seeks an exact relative-path match. Multiple candidates are ambiguous. With no exact candidate, a case-insensitive comparison identifies case-only or ambiguous candidates without approving them. Blank references receive their own status. Only exact matches mark an asset as used, so the unused report deliberately includes assets referenced only by uncertain case-only matches.
Worked production example
The sample manifest contains photos/A.jpg, photos/B.jpg and photos/unused.jpg. Record 1 references photos/A.jpg and matches exactly. Record 2 references photos/b.jpg and is case-only, not automatically approved. Record 3 references photos/missing.jpg and is missing. Two selected asset paths are not used by an exact match: B.jpg and unused.jpg. If a CSV instead contains C:/Jobs/Badges/photos/A.jpg, entering C:/Jobs/Badges as the root resolves the same relative path. Selecting only A.jpg without its photos directory does not justify silently matching photos/A.jpg.
How to interpret the result
Resolve missing and ambiguous rows with the data owner. For case-only results, test the exact production file system and repair the source or delivered name explicitly rather than relying on the current computer's behavior. Download the per-record report to document approved corrections and the unused-path list for packaging review. Unused does not mean safe to delete: an asset may belong to another job version or a variable field not checked in this run. Repeat for every image field and then preview actual linked images in the layout application.
Common production mistakes
Searching only by basename can attach the wrong portrait when two folders both contain 001.jpg. Stripping a CSV path until something happens to match hides an incorrect release package. A URL such as https://example.invalid/a.jpg is not a local relative asset path, and this tool does not fetch it. Spaces, percent-encoded names and accented characters can be meaningful filename differences. A literal apostrophe before @ in the exported header is not equivalent to the spreadsheet's editing convention. Do not treat exact filename matching as proof that the file contains the correct person's image.
Production assumptions and limitations
No selected image contents are uploaded or decoded; only names and relative paths are compared. At most ten thousand asset paths are accepted, and CSV processing is limited to 2 MiB, twenty thousand records and one hundred fields. Folder access depends on browser support and the files the user explicitly selects. The checker cannot inspect hidden remote directories, resolve aliases, verify permissions, identify corrupt images, check image resolution or guarantee that InDesign interprets a path identically. Reports neutralize formula-like text for diagnostic spreadsheet use; they do not rewrite the production source.
Related production workflow and sources
Check field structure with Data Merge CSV Preflight, screen variable names with Variable Text Fit, and use DPI / Print Size separately for pixel requirements. Read Adobe's content-placement options and the production guide before approving a merge. Last reviewed: 2026-10-26.