File naming standards
Use consistent, web friendly file names to ensure assets are easily understood, searchable, and manageable across teams and platforms. Well structured names support accessibility tools, improve SEO performance, streamline asset organization, and make it easier to track versions and updates over time.
General best practices
Applies to all assets:
- Use descriptive names that clearly indicate the asset’s content or purpose
- Avoid generic names like file.pdf or image1.jpg
- Keep it lowercase
- Use hyphens to separate words (avoid spaces or underscores)
- Use all lowercase letters
- Avoid special characters (#, %, &, ?, etc.)
- Add a date or version number for regularly updated assets (e.g., fall-event-flyer-oct-2025.pdf)
- For headshots or visuals, use the person’s full name and context (e.g., jane-smith-headshot.webp)
- Do not repeat the file extension in the name (e.g., avoid guide-pdf.pdf)
File names examples
Use:
- employee-handbook-2025.pdf
- fall-event-flyer-oct.pdf
- brand-and-logo-guidelines.pdf
- flu-vaccine-consent-form-v2.pdf
- jane-smith-headshot.webp
Do not use:
- handbook.pdf
- FallEventFlyer.pdf
- Brand&logo_guidelines.pdf
- Flu_vaccine_consent_form_v2.pdf
- Jane-Smith-Headshot.webp