Ad Naming Convention Generator
Build a token-based naming convention, preview the exact ad name for every creative, and export the whole batch as a CSV. Free, no signup, no email gate.
Naming tokens (drag order = name order)
Filename
The creative filename, cleaned
File type
Image or Video, from the file
ID
A unique number per ad in the launch
Naming pattern
<filename> | <filetype> | <id>Generated ad names (5 names)
| Source filename | Generated ad name |
|---|---|
| acme_spring-ugc-hook-a_9x16.mp4 | acme_spring-ugc-hook-a | Video | 1 |
| acme_spring-ugc-hook-b_9x16.mp4 | acme_spring-ugc-hook-b | Video | 2 |
| acme_spring-static-testimonial_1x1.jpg | acme_spring-static-testimonial | Image | 3 |
| acme_spring-carousel-bundle_4x5.jpg | acme_spring-carousel-bundle | Image | 4 |
| acme_summer-promo-demo_16x9.mp4 | acme_summer-promo-demo | Video | 5 |
One pattern, every ad. This is the exact engine uplads applies at launch: set the convention once and every creative in a bulk launch is named the same way, with the ID token keeping each ad unique. No find-and-replace, no drift.
How to use this ad naming convention generator
Start with the tokens. Each token is one piece of the final ad name: Filename (your creative concept, cleaned up), File type (Image or Video, read from the file), ID (a unique number so two ads never share a name), Date (the launch date in the format you pick), and Custom text (a literal like a brand code or quarter). Reorder them with the arrows, pick one separator, then paste your real exported creative filenames into the box. The table shows the final name for every creative and the Download CSV button gives you a source_filename, ad_name sheet you can keep next to your assets.
What is an ad naming convention?
An ad naming convention is a fixed pattern: the same tokens, in the same order, with the same separator, applied to every ad without exception. The point is not the format itself but the consistency. A consistent name string is what lets you filter Ads Manager to one creative concept across every ad set, compare video against static at a glance, and tell iteration three of a hook apart from iteration one six weeks later. An inconsistent one quietly makes a whole report impossible to pivot. This is why the durable rule is the same as it is for UTM parameters: names should be generated, never typed.
Ad names, ad sets, and campaign names
Most free generators on the market are built for the campaign name: one standardized string per campaign. That layer matters, but the layer that actually breaks reporting is one level down, at the ad. You can have a perfectly standardized campaign name and still be unable to answer "which hook is winning" because every ad inside it is called final_v2. This generator is deliberately ad-level: the tokens resolve per creative, the ID keeps every ad in every ad set distinct, and the result is a name string you can group and filter on in Ads Manager reporting. Standardize the campaign name however your team already does; let the pattern below own the ad name, which is the part that scales badly by hand.
The token approach beats free-text naming
Most teams start with free text: someone types spring video v2 FINAL into the ad name field. It works for one ad. It collapses the week a test ships forty creatives, because no two people abbreviate the same way and nobody is consistent at 5pm on a launch day. A token pattern removes the typing entirely. The concept comes from the filename you already named when you exported the creative, the file type is detected, and the ID is auto-incremented so duplicate concepts never collide. The human decides the pattern once; the machine fills it in every time after that. For the full reasoning and team-tested patterns, see the pillar guide on Facebook ads naming conventions.
Cleanup options: remove dimensions and strip brand name
Exported creatives carry noise that does not belong in an ad name. Remove dimensions strips trailing size tokens like 9x16, 4x5, or 1x1 from the filename, because the file type and placement already tell you the format and the dimension just bloats the string. Strip brand name drops the first segment of the filename up to the first separator, useful when every file is prefixed with the same brand or client code that adds no signal inside a single account. Both run on the filename token only, so your custom tokens and IDs are untouched. These are the same two cleanup switches uplads exposes on its account-level naming settings.
Why a convention is only as good as its enforcement
Here is the gap every naming generator on the market leaves open: they stop at the clipboard. You build a beautiful pattern, copy a string, and then a human still has to apply it to every ad by hand at launch. That manual step is exactly where the convention you just designed starts to drift, because copy-paste under deadline is how inconsistency gets reintroduced. uplads was built inside an Austrian performance marketing agency where every launch day meant naming dozens of new variants per client, and the shape of that work, renaming creatives and applying the same template over and over, is what the product removes. The naming convention is stored once at the ad-account level, and the same engine this tool runs is applied to every creative in a bulk launch automatically, with the ID token keeping each ad unique. The pattern you preview here is the name the product would produce: there is no second, divergent implementation.
One pattern, every ad in a launch
The behaviour worth internalising: a naming convention is not fifty decisions, it is one decision applied fifty times. Define the tokens once. Every creative in the launch flows through the same pattern, the filename token carries the concept, the ID token guarantees uniqueness, and the output is a set of names that sort and filter cleanly in Ads Manager from day one. That is the difference between a spreadsheet of naming rules nobody follows and a convention that actually holds. Pair this with the UTM builder so the names and the tracking are both generated rather than typed.
Frequently asked questions
What is an ad naming convention?
An ad naming convention is a fixed pattern of tokens (for example filename, file type, ID, and date) joined by a separator, applied to every ad the same way. Instead of typing 'video test final v2' by hand, the name is generated from the creative's own metadata so it is consistent, sortable, and filterable in Ads Manager. A good convention is machine-built, not typed, because anything typed under deadline drifts.
How do you create a naming convention for Facebook ads?
Decide which pieces of information every ad name must carry: usually the creative concept (from the filename), the format or file type, a unique ID, and often a launch date. Order those tokens, pick one separator, and apply it to every ad without exception. The generator above does this: arrange the tokens, choose the separator, paste your creative filenames, and it produces the final ad name for each one plus a downloadable CSV.
Is there a free ad naming convention generator?
Yes. This one is free, needs no signup or email, and runs entirely in your browser. Unlike generic name builders that output a single string, it generates a name for a whole batch of creatives at once and exports them as a CSV, because real ad ops names dozens of creatives per launch, not one.
What tokens should an ad name include?
At minimum a concept identifier (the cleaned filename), a unique ID so duplicate concepts never collide, and the file type so you can filter video against static. Many teams add a date token for the launch week and a custom token for the brand or quarter. Avoid encoding anything Meta already reports natively, such as placement, unless you specifically need it in the name string itself.
Why does a naming convention break down at scale?
A convention written in a spreadsheet only holds if a human applies it perfectly to every ad, every launch. The moment a creative test ships 30 to 50 ads in one sitting, naming is the first thing rushed or skipped, and one inconsistent name makes a whole report unsortable. The fix is to generate names from a pattern instead of typing them, then apply that pattern automatically at launch rather than copying names by hand.
How do I apply one naming convention across 50 ads at once?
Define the token pattern once, then let the launch tool resolve it per creative so every ad gets a consistent name with a unique ID. uplads stores the naming convention at the ad-account level and applies that exact pattern (the same buildAdName engine this tool uses) to every creative in a bulk launch, so a 50-ad creative test ships correctly named in one pass instead of 50 manual edits.
Apply one naming convention to every ad
A naming pattern only holds if it actually reaches every ad. uplads stores your convention once and applies this exact engine to every creative in a bulk launch, with a unique ID per ad, so a 50-creative test ships correctly named in a single pass instead of 50 manual edits. Save the hours a week that hand-naming eats.