How it works
Inconsistent file naming creates chaos in shared Dropbox folders, Google Drive campaign assets, and design handoffs. The Social Media Asset Naming Tool enforces a consistent naming convention: you input the content type, platform, date, and version, and it generates a standardised filename following your chosen convention — with a batch rename helper for existing files.
Naming convention format: [BRAND]_[PLATFORM]_[FORMAT]_[DATE]_[CAMPAIGN]_[VERSION].[ext]
Example: noxakit_instagram_reel-cover_2025-04-01_spring-launch_v2.jpg
Convention components: - Brand/channel prefix: keeps assets sortable by brand in shared folders - Platform: IG, TT, YT, LI, FB, TW (standardised short codes) - Format: post, story, reel-cover, thumbnail, banner, ad, carousel-1, carousel-2 - Date: ISO 8601 (YYYY-MM-DD) — sorts chronologically in all operating systems - Campaign slug: hyphenated lowercase campaign name - Version: v1, v2, v3 — never "final", "final2", or "ACTUAL_FINAL"
How to use: 1. Select each component from the dropdown menus or type custom values. 2. The standardised filename is generated — copy it for your next saved asset. 3. Paste up to 20 existing filenames into the batch renamer to see their standardised equivalents.
Team tip: export your naming convention rules as a one-page PDF to share with designers, VAs, and freelancers — consistent naming pays dividends immediately in reduced "which file is this?" messages.
Privacy: all processing runs in the browser.
Frequently Asked Questions
- ISO 8601 date format sorts chronologically in every operating system without additional configuration. A folder with files named 2025-01-15_asset.jpg, 2025-03-02_asset.jpg, 2025-11-20_asset.jpg sorts correctly by date when listed alphabetically. By contrast, US date format (01-15-2025) and European format (15-01-2025) both sort incorrectly when listed alphabetically — January and November files appear adjacent to each other.
- These names fail because: (1) there is no shared understanding of what 'final' means — version-controlled names (v1, v2, v3) are unambiguous; (2) 'final' files are routinely superseded, creating 'final_revised', 'final_approved', 'final2' — the naming collapses into chaos; (3) sorted alphabetically, 'final' and 'final_revised' appear nowhere near each other; (4) version numbers enable rollback — you can always return to v2 if v3 has issues.
- Use a sequential suffix: brand_ig_carousel-1_2025-04-01_campaign_v1.jpg, brand_ig_carousel-2_2025-04-01_campaign_v1.jpg, etc. The carousel number (carousel-1, carousel-2) makes the sequence explicit. The campaign slug and version are shared across all images in the carousel — so a revision produces carousel-1_v2, carousel-2_v2, maintaining the relationship between images.
- Only if you regularly create multiple size variants of the same asset. If you create Instagram Story (1080x1920) and Instagram Feed (1080x1080) versions of the same graphic, add the format tag: brand_ig_story_2025-04-01_campaign_v1.jpg vs. brand_ig_feed_2025-04-01_campaign_v1.jpg. If you only ever produce one size per platform/format combination, the format field (story, feed, thumbnail) already implies the dimensions.