How to override the naming schema for a single launch

Sometimes one launch needs different ad names than the rest — a different field order, an extra token, or a whole different preset. uplads lets you change the naming schema for that single launch without touching the default you saved in Settings. Your account default stays exactly as it was; only this launch uses the override.

If you haven't set up your account-wide template yet, see How to set up a custom ad naming convention first.

Opening the naming schema dialog from the Review step

The naming editor lives on the Review step of the bulk launch wizard, right next to the list of ads it will rename — so you can adjust the schema while looking at the names it produces.

1. Move through the wizard to the Review step.
2. In the Ads card header, click the Naming schema button.
3. The Naming schema for this launch dialog opens.

If you've already changed the schema for this launch, a small modified badge appears on the button so you can tell at a glance that this launch differs from your saved default.

Reorder tokens for this launch only

Every name is built from an ordered list of tokens — Filename, File type, Date, Auto-id, Custom text, and field tokens like Style, Hook, or Audience. The order of the list is the order they appear in the final name.

• Drag to reorder: grab the handle on the left of any token row and drag it up or down. A violet insertion line shows exactly where the token will land before you let go.
• Remove a token: click the X on the right of the row.
• Add a token: in the Add row, pick a kind from the dropdown and click Add. Common fields (Style, Hook, Audience, Offer, and more) are listed under a "Common fields" divider and drop in fully formed with their option lists. Choose Custom text to type a fixed word, or Custom field… to define your own label and options.
• Change the separator: use the Separator dropdown (underscore, hyphen, space, dot, or pipe) to set what joins the tokens.

You can also toggle two cleanups: strip dimensions like 9x16 or 4x5 from the filename token, and strip your brand name from the filename token.

Choosing a naming preset

The Load preset… dropdown gives you a ready-made starting point. Picking one replaces the current token list entirely, so it's the fastest way to start fresh:

• Creative Schema — Style / Asset Type / Length / Creator Age / Hook / Dimensions. A detailed creative-testing schema.
• Performance marketing — Hook / Audience / Offer / Format. A leaner performance-focused schema.

Prefer to build from nothing? Click Start blank and add tokens one at a time.

Seeing the live preview

At the bottom of the dialog, the Preview line shows how your first ad in this launch would actually be named, using its real filename and any field values you've already picked. Every drag, add, preset swap, or separator change updates the preview instantly, so you can dial in the format before committing.

Once a name looks right, click Apply to this launch. To back out without changing anything, click Cancel — your in-progress edits are discarded.

Watching for duplicate names

The dialog itself focuses on the format. Duplicate detection happens on the Review step after you apply: if any proposed name already matches an ad that exists in a target ad set, a Possible duplicate ads warning appears so you can rename before launching. See How to review and edit ad names before launch for handling those and making one-off manual name edits.

How a per-launch override differs from the account default

• Scope: the override applies only to the current launch. Your saved Settings default is untouched, and the next launch starts from that default again.
• What ships: the name shown in Review is byte-for-byte the name created on Meta — the preview and the launched ad always match.
• Field values reset: applying a new schema clears any field values you'd already filled in, because the old schema's fields may not exist in the new one. You'll re-pick values for whatever fields the new schema asks for.
• Make it permanent: if you find yourself applying the same override every time, set it as your account default instead — see How to set up a custom ad naming convention.

For where field values come from automatically, see How naming field values are auto-detected (including AI vision).