SharePoint File Naming & Folder Best Practices

Why you need to know this?

SharePoint and OneDrive work great until file names and folders get too long. When that happens, users may see:

• Files that won’t open or sync
• Upload errors
• Sharing links that break
• Problems during migrations later

The Goal: Keep names short, clean, and easy to find.

Keep File Names Short & Clear

• Good:
  • Invoice_2026-01_ACME.pdf
  • HR_Policy_TimeOff.docx
  • ProjectPlan_Q2.docx
• Not good:
  • Invoice FINAL FINAL v3 Approved Copy John's edits.pdf

Rule of thumb: Stay under ~100 characters whenever possible.

Avoid Deep Folder Nesting

• Good:
  • Finance > Invoices > Jan2026 > ACME
• Better:
  • Finance > Invoices > Jan2026
• No Good:
  • Documents > Finance > 2026 > January > Vendors > ACME > Final > Revised

Don’t Put Everything in the Folder Name

• Good:
  • Invoice_2026-01_ACME.pdf
• No Good:
  • Invoices_Approved_2026_January_Final

SharePoint Already Saves Versions - Don’t Rename “Final”

• Avoid:
  • final.docx
  • final2.docx
  • final_reallyfinal.docx
• SharePoint Version History already tracks:
  • Changes
  • Previous drafts
  • Who edited what

Avoid Special Characters

Some symbols cause sync/sharing issues.

• Avoid:
  • * `# % & * { } \ : < > ? / + | "`
• Use:
  • Dashes -
  • Underscores _
• Examples:
  • Good: Budget_2026-Q1.xlsx
  • Not Good:  Budget#2026/Q1.xlsx

Keep Folder Levels Simple

Recommended maximum: No more than 3–4 folder levels deep.

Example:

• Good: Shared Documents > HR > Policies
• Not Good: Shared Documents > HR > Policies > 2026 > Drafts > Archive > Old Versions > Misc