Every brand accumulates an asset library. Logos at different sizes. Photos shot for specific campaigns. Templates for various channels. Slide decks. Email banners. Within months, the library is a chaos of files with names like `Logo Final.png` and `logo final v2 FINAL.svg` and `LOGO-actual-final-USE-THIS.png`.
The cost of this chaos isn't immediately visible. It shows up as the 4 minutes you spend looking for the right logo file every time you need one. The contractor who emails you asking "which version is current?" The team member who uses an outdated logo on a partner deck because the file in the folder said "FINAL." Multiply across years and the cost is significant. Easily 100 hours of cumulative time wasted searching, double-checking, and fixing wrong-file mistakes.
The fix is a file-naming convention. Established once, followed consistently, saves the cumulative hours forever after.
The naming convention that scales
The convention that works for solo founders through 50-person teams:
[category]_[subject]_[variant]_[size-or-context]_[date].extensionExample file names:
logo_primary_light_1024px_2026-05.svglogo_primary_dark_512px_2026-05.pnglogo_favicon_simplified_64px_2026-05.svgphoto_hero_homepage_3000px_2026-06.jpgtemplate_instagram_post_square_2026-07.figemail_signature_personal_2026-08.png
This looks verbose. Once you use it for a week, it becomes second nature. The verbose-ness is the feature. Every file's purpose is visible in its name, and you never have to open a file to know what it is.
The principles behind the convention
1. Most-general to most-specific, left to right. Category first (logo, photo, template, etc.), then subject (primary, hero, square), then variant (light, dark, simplified), then size or context, then date. This means files sort meaningfully alphabetically. All the logos cluster together, all the photos cluster together.
2. Underscores, not spaces. Spaces in filenames create problems on the web (URL-encoded as %20), in command-line tools, and in some software. Underscores are safe everywhere.
3. Lowercase throughout. Capitalization issues bite you when you sync across operating systems with different case-sensitivity rules. Lowercase universally.
4. Date in ISO format (YYYY-MM). Year-month-day or year-month gives you alphabetical sorting that matches chronological sorting. "2026-11" sorts before "2026-12" naturally. "Nov2026" doesn't.
5. No special characters. Avoid &, *, /, \, ', ", and other characters that cause problems in URLs or different filesystems. Stick to letters, numbers, underscores, hyphens, periods.
6. No "FINAL" in filenames. Every file you save thinks it's final. Use the date instead. The most recent date is the most current version.
The folder structure that complements the naming
File naming alone helps. Combined with folder structure, it transforms the asset library. The structure that works:
brand-assets/
├── 1-logos/
│ ├── primary/
│ ├── favicon/
│ └── archive/ (old versions kept for reference)
├── 2-typography/
│ └── font-files/
├── 3-colors/
│ └── palette-swatches/
├── 4-photography/
│ ├── hero/
│ ├── product/
│ └── lifestyle/
├── 5-templates/
│ ├── instagram/
│ ├── linkedin/
│ ├── email/
│ └── presentations/
├── 6-icons/
└── 7-archive/ (anything no longer in active use)The numbered prefixes (1-, 2-, etc.) force a specific order in file browsers. The most-used folders sort to the top. Archive folders are clearly separated from active assets.
The version control question
Should every file revision get a new file with a new date, or should you overwrite the old one? Three approaches, each with trade-offs:
Approach 1: Overwrite, archive monthly. Files keep their names; revisions overwrite. Once a month, you snapshot the entire folder into an archive. This is the simplest approach. Downside: no easy access to historical versions between snapshots.
Approach 2: Date in every filename. Each save creates a new file with the new date in the name. Old versions stay. This produces clarity at the cost of growing folder size. Best for teams where multiple people might need access to specific historical versions.
Approach 3: Version control system. Use Git or a design-versioning tool (Figma's version history, Frame.io for video). The tool maintains the history; the live files are always the current version. This is the most professional but requires tool adoption.
For a solo founder, Approach 1 (overwrite, monthly snapshot to archive) is usually sufficient. For a team, Approach 2 or 3.
The migration plan if your current naming is chaos
If your existing brand asset library is the kind of chaos this post describes, don't try to rename everything in one weekend. Migrate gradually:
Step 1: Define your naming convention and write it down. One page. Pin it somewhere your team can find.
Step 2: Set up the new folder structure. Empty folders, ready for files.
Step 3: Migrate the 10 files you use most often. These are the ones whose rename you'll notice immediately. Logos, primary brand colors, your most-used photos and templates.
Step 4: Rename files as you touch them. Each time you open a file from the old system to use it, rename it to the new convention while you have it open. Within 3 months, most active files will be migrated organically.
Step 5: Archive the unmigrated old files. After 3-6 months of organic migration, anything that hasn't been touched probably isn't in active use. Move it to an archive folder. If you need it again later, rename it then.
The system maintains itself once it's running. New files are named correctly because that's the habit. Old files migrate as they're used. Eventually the asset library is clean.
The compound effect
The 4 minutes you save every time you find a file is small. The cost of a wrong-file mistake (using an outdated logo on a partner deck, sending a contractor an old brand color hex) is large but rare. The cumulative time from never being uncertain about which file is current is the part that compounds.
Founders who set this up in their first year operate from a clean asset library forever. Founders who don't either spend an annual weekend reorganizing or live with the chaos permanently. The 30 minutes of setup is one of those small operational investments that pays back across years of work.
Your brand kit, ready in 10 minutes.
Five quick taps. Free preview before you pay.
Start building free →