A useful social media filename identifies the campaign, creative idea, placement, language, and version without opening the file. Keep the order consistent and store approval status somewhere the whole team can trust.
The best system is one people actually use. A filename with fifteen required fields usually fails as soon as someone needs to export in a hurry.
Start with five useful fields
Try this working pattern:
campaign_concept_placement_language_version.ext
For example:
winter-launch_warmth-demo_story_en-gb_v03.mp4
This tells a teammate what the file belongs to, which idea it contains, where it should run, which language version it is, and which revision they are looking at.
Add dimensions when several exports share a placement name:
winter-launch_warmth-demo_feed-1080x1350_en-gb_v03.jpg
These are suggested conventions, not platform requirements. Adjust them to your team’s work.
Define the vocabulary once
Choose one spelling for each field. If the same placement appears as story, stories, and vertical, searching and sorting become harder.
A small reference table helps:
| Field | Example | Rule |
|---|---|---|
| Campaign | winter-launch | Shared across related assets |
| Concept | warmth-demo | Describes the message or idea |
| Placement | story | Uses an agreed list |
| Language | en-gb | Includes region when it matters |
| Version | v03 | Increases when the content changes |
Use simple characters and predictable separators. Avoid adding personal information or confidential customer details to filenames that may be shared externally.
Separate working files from delivery files
Keep editable projects, review exports, and approved deliveries in distinct folders. A reasonable structure is:
winter-launch/
source/
review/
approved/
archive/
A file moving into approved should have a recorded approval. A folder name alone is not evidence that someone checked the price, copy, or destination.
Keep a short delivery sheet with the filename, intended placement, approval date, and approver. This is especially helpful when a media buyer uploads files produced by another team.
Stop using “final-final”
Use revision numbers instead. If v03 is approved and a price changes, the new file becomes v04 and goes through review again.
Do not overwrite an approved export silently. Someone may already have downloaded or scheduled the older version. Record what changed so the team can find and replace it.
Connect files to campaign reporting
Use the same concept label in your asset sheet and creative report. That makes it easier to compare ideas across different crops and formats.
If you add a creative identifier to a UTM-tagged link, keep it stable enough to match the original asset. Do not rebuild the naming system separately inside each reporting tool.
Try the system on one campaign
Rename a small set, ask another teammate to find a specific asset, and note where they hesitate. Remove fields nobody uses and add only the ones that prevent real mistakes.
Write the final rule in a short shared note with three examples. A clear convention and a clean delivery folder will save more time than a complicated system nobody remembers.