Fix Stock Metadata CSV Filename Mismatches Before Upload
When a metadata CSV does not apply to the intended asset, check filename matching before rewriting the title or keyword list. Small differences between the final asset folder and the exported rows can break an otherwise useful batch.
Compare the full filename, including extension
Pick one failed row and compare its filename with the actual asset you uploaded. Look for a missing extension, a different extension, leading or trailing spaces, changed punctuation and unintended renaming. Do not rely on a file manager view that hides extensions. Treat matching as exact rather than assuming that every platform normalizes spacing or letter case. Correct the source naming workflow or the CSV deliberately, then test one row before changing the entire batch.
Separate vector assets from preview images
An EPS or AI workflow may create a JPEG preview so a vision model can analyze the artwork. The preview can be useful for generation without becoming the asset a contributor intends to submit. Confirm that the exported row points to the original contributor filename. If you also upload a separate JPEG version, keep its row distinct and review whether its description matches that specific deliverable. Two files with the same basename can still represent different assets.
Check when renaming happened
If you rename files after generating the CSV, its existing filename column can become outdated. Keep a record of any deliberate renaming, re-export metadata using the final names where supported or update the rows carefully. Do not solve a matching error by giving every file the same title-derived basename. Similar assets can generate similar wording, and duplicate output names may overwrite or confuse files in a later step. Keep a reversible source copy until the workflow is verified.
Inspect the CSV as a table and as text
Check whether the filename value sits in the correct column and whether quoted titles or keyword lists caused an accidental column shift. Spreadsheet software can change delimiters or formatting when saving, so inspect the final exported file rather than assuming that the version you first downloaded is still intact. Use the marketplace's current template for its expected headers. Make only the necessary correction and preserve a copy of the original output for comparison.
Verify a small upload before scaling
Upload a small set of known assets and apply the corrected CSV. Confirm that the expected metadata appears on the right files in the contributor account. Only then repeat the process for the remaining batch. CSV Metadata preserves original filenames through supported analysis-preview workflows, but any later file operation can still create a mismatch. The final checkpoint belongs in the receiving platform, with both the visible asset and its applied metadata in view.