SharePoint Naming Conventions: A Plain-English Guide
How files are named affects how findable they are — by humans, search, and Copilot. Naming conventions turn random into intentional.
What it is
A naming convention is a written rule about how files should be named. The same convention applied across a team means files are predictable: same format, same date style, same component order. The difference between a library that’s a pleasure to navigate and one that’s a horror show often comes down to whether anyone agreed on naming.
What goes in a good convention? Usually a combination of: relevant date (in YYYY-MM-DD format so it sorts correctly), document type or category, distinctive label (project name, client, subject), and version notation (though SharePoint version history makes this less important). The exact components depend on the library — what works for project files won’t work for invoices.
The biggest single rule: dates first, in YYYY-MM-DD format. This single decision means files sort chronologically without any extra effort. Add document type after the date, distinctive label after that, and you have a consistent, sortable, scannable library that users actually enjoy navigating.
Names are read by Copilot too
Filenames are part of what Copilot reads when answering questions about your content. A file called ‘Document1.docx’ tells Copilot nothing. A file called ‘2026-04-15_Marketing-Strategy_FY26.docx’ tells Copilot what it is, when it’s from, and what it covers. Good names aren’t just for humans — they’re a key signal for AI.
When to use this
- Whenever you set up a new library and want it to scale.
- When existing libraries are filling with inconsistent filenames.
- When new team members need clear guidance on how to name files.
- When you’re preparing libraries for Copilot — clean names improve accuracy.
How to do it
- Decide what info should be in the name (date, project, type, version).
- Choose a separator (underscore _ or hyphen -, pick one and stick with it).
- Use YYYY-MM-DD for dates so they sort chronologically.
- Document the convention in the library’s description or in a one-page guide.
- Train your team on the convention.
- Audit existing files and rename where practical.
- Make adherence visible — flag non-conforming names.
Best practices
- Always use YYYY-MM-DD for dates. Sorts correctly, no ambiguity, works internationally.
- Avoid generic names. ‘Document1.docx’, ‘Scan_001.pdf’, ‘Untitled.docx’ tell nobody anything.
- The name should describe what the file is without opening it. If you have to open it to know what it is, the name failed.
- Combine naming with metadata. Don’t rely on names alone — pair with Document Type, Department, Status columns.
Common mistakes
- No agreed convention. Every user names files differently. Library becomes unfindable.
- DD-MM-YY or MM-DD-YY dates. Don’t sort correctly. Use YYYY-MM-DD always.
- Names that include version numbers. SharePoint version history handles versioning. Don’t put ‘v3’ in filenames.
The File Sanity Kit gives you the Container Method™ — audit, restructure, and future-proof SharePoint without IT admin. The complete methodology, full workbook, and 8-tab Excel planner.
Get the File Sanity Kit — $27 →FAQ
Why don’t traditional SharePoint naming conventions work?
Because they try to do metadata’s job through filenames. A name like HR-POL-2026-Q1-Remote-Work-v3.docx packs department, document type, year, quarter, topic, and version into one string — which means filtering by any one of those requires text parsing. Make those attributes proper metadata columns and the filename can be human-readable instead of a code.
Do I need naming conventions in SharePoint at all?
Yes — but lightweight ones. Names still matter for human scannability and Copilot input. The rule is: name files so a new starter can understand them without a decoder ring. ‘Remote Work Policy’ is a good filename; ‘HR-POL-2026-RW-v3’ is not. Push the structural data into metadata columns where it belongs.
What’s wrong with using underscores in SharePoint filenames?
Underscores are technically fine, but they make names harder to read and skim. Spaces are universally supported in SharePoint and Microsoft 365, render cleanly in all interfaces, and Copilot parses them better. Use spaces in titles for humans; reserve underscores or hyphens for technical IDs only.
Does Copilot read SharePoint filenames?
Yes — filenames are part of what Copilot uses to understand context. A descriptive plain-language filename (‘2026 Remote Work Policy’) feeds Copilot a strong signal. An abbreviated coded filename (‘HR-POL-2026-RW-v3’) feeds it noise. Naming with humans in mind also serves Copilot — the two goals reinforce each other.