File Naming Conventions for Designers
Professional file naming strategies that save time and prevent confusion
Why File Naming Matters
Poor file naming leads to wasted time, confusion, and errors. A good naming convention helps you and your team find files quickly, understand versions at a glance, and maintain organized project folders.
Core Principles
1. Be Descriptive but Concise
File names should clearly indicate content without being unnecessarily long.
- Good: logo-acme-corp-horizontal-blue.svg
- Bad: final-version-2-updated-new.svg
2. Use Lowercase
Lowercase names prevent issues with case-sensitive systems and are easier to type.
- Good: header-background.jpg
- Bad: Header-Background.jpg
3. Use Hyphens, Not Spaces
Spaces in filenames can cause problems in URLs and command-line tools. Use hyphens instead.
- Good: product-hero-image.png
- Bad: product hero image.png
4. Include Dates When Relevant
Use ISO 8601 format (YYYY-MM-DD) for dates so files sort chronologically.
- Good: 2025-01-15-newsletter-design.pdf
- Bad: newsletter-design-1-15-25.pdf
Recommended Naming Structure
A consistent structure makes files predictable and easy to find:
[project]-[category]-[description]-[version].[extension]
Examples:
- acme-logo-horizontal-v2.svg
- website-hero-background-final.jpg
- app-icon-ios-1024px.png
- brochure-cover-draft-v3.pdf
Version Control
Clear versioning prevents confusion about which file is current:
- v1, v2, v3: For major versions
- v1.1, v1.2: For minor revisions
- draft, review, final: For workflow stages
- approved: For client-approved versions
Version Examples:
- logo-concept-v1.ai
- logo-concept-v2-revised.ai
- logo-concept-v3-final.ai
- logo-concept-v3-final-approved.ai
Category Prefixes
Use prefixes to group related files:
- icon-: icon-home.svg, icon-search.svg
- img-: img-hero-banner.jpg, img-product-photo.jpg
- bg-: bg-texture-paper.png, bg-gradient-blue.png
- logo-: logo-primary.svg, logo-white.svg
- font-: font-heading-bold.woff2, font-body-regular.woff2
Dimension and Format Indicators
Include size or format information when you have multiple versions:
- app-icon-ios-1024px.png
- app-icon-android-512px.png
- banner-desktop-1920x1080.jpg
- banner-mobile-750x1334.jpg
- logo-horizontal-color.svg
- logo-stacked-monochrome.svg
Project-Specific Conventions
Web Projects:
- homepage-hero-desktop.jpg
- homepage-hero-mobile.jpg
- about-team-photo-01.jpg
- product-thumbnail-blue-widget.png
Print Projects:
- brochure-cover-cmyk-300dpi.pdf
- business-card-front-bleed.pdf
- poster-a3-portrait-final.pdf
Social Media:
- instagram-post-2025-01-15-promo.jpg
- facebook-cover-spring-campaign.jpg
- twitter-header-brand-refresh.jpg
Characters to Avoid
These characters can cause problems in different systems:
- Spaces (use hyphens instead)
- Special characters: / \ : * ? " < > |
- Periods (except before file extension)
- Accented characters (use ASCII equivalents)
Folder Organization
Complement your naming convention with a logical folder structure:
project-name/ ├── 01-research/ ├── 02-concepts/ ├── 03-drafts/ ├── 04-finals/ ├── assets/ │ ├── fonts/ │ ├── images/ │ └── icons/ └── exports/
Team Collaboration Tips
- Document your naming convention in a shared style guide
- Use templates with pre-named layers and artboards
- Set up automated renaming scripts for batch operations
- Review and clean up file names before sharing with clients
- Use version control systems (Git) for code and design files
Tools and Automation
Several tools can help enforce naming conventions:
- Bulk Rename Utility: Batch rename files on Windows
- Renamer: Mac app for batch renaming
- Adobe Bridge: Batch rename with metadata
- Figma plugins: Auto-name layers and exports
- Custom scripts: Automate naming with Python or JavaScript
Quick Reference Checklist
- ✓ Use lowercase letters
- ✓ Replace spaces with hyphens
- ✓ Be descriptive but concise
- ✓ Include version numbers
- ✓ Use consistent date format (YYYY-MM-DD)
- ✓ Add dimensions when relevant
- ✓ Avoid special characters
- ✓ Use category prefixes
- ✓ Document your system
- ✓ Stay consistent across projects
Conclusion
A solid file naming convention is a simple habit that pays dividends throughout your career. Start implementing these practices today, and you'll save countless hours searching for files and avoid confusion in collaborative projects. Your future self (and your teammates) will thank you!