Creative asset validation before campaign handoff.

Validate coverage and file quality together.

Creative asset validation checks whether every required campaign variant exists and whether each delivered file obeys its technical rules. A folder can contain valid images and still be incomplete; it can also cover every placement while containing the wrong dimensions, format, filename, or byte size.

• Coverage across markets, locales, channels, and placements
• Required width, height, file type, and maximum size
• Filename tokens for campaign, market, language, and version
• Empty files, exact duplicates, and unexpected package entries

Start from an explicit requirement matrix.

One row should describe one expected variant: campaign, market, locale, channel, format, dimensions, accepted file types, byte limit, naming convention, and whether the variant is required. This turns subjective review into a repeatable contract and prevents a folder listing from becoming the source of truth.

Download the campaign matrix template · Read the matching methodology

Inspect files without creating a new data risk.

A preflight tool only needs local file access to inspect names, dimensions, media types, hashes, and ZIP structure. Keeping raw creative in the browser reduces transfer time, avoids another asset repository, and preserves the existing source-of-truth workflow.

Keep uncertainty visible and reviewable.

Filename matching should expose its evidence. When two requirements are plausible, route the file to a review queue with both candidates and their scores. Never convert a close guess into a silent pass: the cost of one human decision is lower than an incorrect campaign handoff.

Finish with evidence, not a verbal confirmation.

A complete preflight should produce a coverage view, prioritized correction list, review decisions, rename map, campaign manifest, and delivery receipt. These artifacts let creative operations, media teams, agencies, and clients see the same readiness state without reopening the entire folder.