Ad Creative File Naming: A Small Handoff System That Prevents Wrong Uploads

Name an ad creative so someone can identify its product, concept, language, format and revision after it leaves your project folder. Keep a short delivery note that identifies the selected file and destination. The filename helps people find the asset; the note explains which version to use and why it exists.

For a small creative team, this can be a folder and a text document. You do not need a new asset-management platform to stop a square draft from being mistaken for the portrait campaign approved for launch.

Choose fields that distinguish real decisions

Use names that describe the work, rather than every detail of the production process. For the fictional Roam travel-cup campaign, a useful pattern is:

roam_commute_en_3x4_v03.png
roam_commute_zh_3x4_v03.png
roam_desk_en_1x1_v01.png

The example assumes those are actual PNG exports. Preserve the real file extension; renaming a JPEG does not convert it. `3x4` and `1x1` describe the intended proportions, while the delivery note records the actual pixel dimensions after checking the file.

If your campaign has several products with similar names, use an established product identifier. If it has only one language, keeping the language field can still help when you add a translation later. Make the convention readable to the person uploading the ad, not just its creator.

Separate the concept from its revisions

A commute scene and a desk scene may represent different advertising ideas. A corrected headline within the commute scene is a revision of that idea. Keep those differences visible in the name.

For this suggested convention, increase the revision when you hand a changed export to someone else. Keep one selected file in the delivery folder and older candidates in an archive. Avoid names such as `final-final-new.png`, which stop explaining anything as soon as the next change arrives.

The convention is an editorial recommendation, not a requirement of an advertising platform. Adapt it to an existing team system if that system already identifies the correct asset reliably.

Deliver a short manifest with the files

A filename cannot tell the next person what changed or where to upload it. Include a small note with the selected asset, destination, actual dimensions, language and a concise description of the concept.

Campaign: Roam commute
Selected file: roam_commute_en_3x4_v03.png
Actual dimensions: record after inspecting the export
Destination: record the agreed placement and product-page URL
Concept: a travel cup moving from desk to train
Change from v02: closing invitation enlarged; product shape retained
Copy: paste the exact words visible in the delivered image
Image description: include the final accessible description
Previous versions: archived; do not upload

Fill the placeholders before delivery. They are prompts for your team, not values to leave in a finished handoff. If the destination changes, recheck the composition and update the note rather than changing only the filename.

Do not confuse cloud history with a portable version label

Cloud storage may retain previous file versions. Dropbox's version-history documentation explains its recovery controls and that available history depends on the plan. Use your service's actual retention behavior when deciding how much history it provides.

A downloaded attachment still needs an understandable name. The recipient may not have access to the original cloud history, and two files downloaded from different shared links may look equally current. Keep the selected-file note beside the exports so the handoff carries its own context.

Avoid reorganizing old shared folders casually. Moving or renaming assets can disrupt references in other people's workflows. Apply the agreed pattern to new deliveries, and migrate an older campaign only when you can check its dependent links.

Make the last check resemble the real upload

Open the selected export from the delivery folder, not from the creative application's recent-files menu. Verify the product, language, composition and exact copy. Then open the destination link from the manifest.

This catches a common handoff mistake: the design is correct in the workspace, but an older download is the one ready to upload. It also reveals when the selected image's caption or accessible description still belongs to a previous scene.

In Panelly Studio, keep the product brief and selected creative version together while refining the ad. After downloading the chosen image, apply your delivery naming convention and record the exact project or version reference you used. This article does not imply that Panelly automatically creates a manifest or manages your advertising-platform uploads.

FAQ

Should the filename include every dimension and platform?

Include the fields that prevent confusion in your workflow. Put longer destination details in the manifest so the filename remains readable.

Can the same image have different filenames for different clients?

Yes, but keep a record of which source version each delivery used. Otherwise, feedback on one copy can become detached from the actual creative you need to change.

Do I need a separate file for the CTA?

No. A complete ad image can contain its headline and CTA. Naming and handoff notes identify that finished asset without introducing additional text-layer management.

What should I do with rejected concepts?

Keep them outside the selected delivery folder with their original concept names. They remain useful creative history without becoming accidental launch candidates.

Sources and further reading

• Dropbox's version-history documentation