Social media campaign asset naming convention template
Use file names that identify the campaign, actual asset, language and version. Keep status and rights decisions in a shared manifest. A filename should help someone find the right file without exposing client or participant details.
Your working document
Complete the record
| Component | Example | Use |
|---|---|---|
| Campaign | cafe-menu | A stable short identifier shared with the brief |
| Asset | demo | The specific demonstration, not a generic final label |
| Language | en or zh-hk | The actual approved wording version |
| Purpose | vertical or square | The intended export geometry or use |
| Version | v03 | A new identifier after a substantive revision |
Check before sharing
- Use a new version when wording, order or visuals change.
- Maintain the actual approved version in the manifest.
- Keep private participant names out of public filenames.
- Check that the folder structure works for the receiving team.
Use the worksheet in practice
Do not keep renaming a file 'final', 'final-new' and 'final-approved'. A stable asset code plus a version lets the approval record identify the exact reviewed file. An export for a different crop needs its own purpose label even when the underlying edit is the same.
For example, cafe-menu_demo_en_vertical_v03.mp4 and cafe-menu_demo_zh-hk_vertical_v02.mp4 are independent language exports. Their different version numbers do not establish which one is approved; that decision belongs in the manifest.