Quality · 5 min read

A file naming system for multi-page campaign exports

Make every delivered asset identifiable by campaign, channel, placement, variant, and version without opening the file.

  • Published 2026-08-25
  • Original Retake editorial
Three-panel Northline streetwear story with a forest-green jacket

In this guide

A reviewable path, not a bag of tips.

A technically correct export can still create operational confusion. Stable filenames and a short manifest help teammates match each PNG to the reviewed design and placement.

  1. 01Choose fields that answer operational questions
  2. 02Normalize the filename grammar
  3. 03Prevent accidental overwrite
  4. 04Ship a manifest with the files

Choose fields that answer operational questions

A practical order is campaign, channel, placement, concept or variant, and revision. Avoid internal IDs as the only human-readable signal.

Normalize the filename grammar

Use one separator, predictable lowercase words, and a stable revision format. Do not let each design invent its own abbreviation.

Prevent accidental overwrite

Variant and revision labels must produce distinct paths. Export should warn when two requested designs resolve to the same filename.

Ship a manifest with the files

List design name, width, height, filename, and any delivery note. The manifest describes the export; it does not become another document authority.

Worked example

Name a six-file seasonal campaign delivery

Deliver two creative variants across Feed, Story, and square placements.

  1. 01

    Choose campaign, channel, placement, variant, and revision fields.

  2. 02

    Normalize words to lowercase kebab case.

  3. 03

    Export each design without changing the document.

  4. 04

    Include a manifest that maps design names to filenames and dimensions.

Outcome

Six self-explanatory PNGs that can be routed and reviewed without guesswork.

FAQ

Questions to carry into review.

Should filenames include pixel dimensions?

They can, especially for handoff outside a platform-specific folder. A manifest should still record the exact dimensions.

Is a ZIP manifest the project file?

No. It is human-readable delivery metadata. The editable DesignDocument remains the source authority.