How to Create a Document Library in SharePoint
Document libraries are where files actually live in SharePoint. A well-designed library is the foundation of everything else. A badly-designed one creates years of mess.
What it is
A document library is SharePoint’s container for files. Every SharePoint site has at least one (typically called ‘Documents’); most sites have several. Inside a library, you have files and folders, but you also have metadata columns, views, permissions, versioning settings, approvals, and lifecycle rules. A library isn’t just a folder — it’s a structured space with its own policies.
Most users only ever see the default ‘Documents’ library that comes with a new site. That’s fine for very simple cases, but it’s also where most SharePoint mess accumulates. Multiple libraries — one per major content type or process — give you cleaner organisation, better permissions control, and the ability to apply different rules to different content.
Creating a library is straightforward in the interface. The hard part isn’t the technical creation — it’s designing the library well. Good libraries have a clear purpose, sensible metadata columns, useful views, considered permissions, and a maintenance owner. Bad libraries have none of these and become ‘a place where files go to die’.
When to use this
- When you’re setting up a new site and need to plan its content structure.
- When you’ve outgrown a single ‘Documents’ library and need to split content.
- When you have a specific document type that needs its own metadata and rules.
- When you’re separating draft, review, and published content into different libraries.
How to do it
- Open the SharePoint site.
- Click + New → Document library.
- Name it clearly (e.g. ‘Policies’ not ‘Documents 2’).
- Add a description so users know what belongs there.
- Configure versioning settings (major/minor, version limits, content approval if needed).
- Set permissions if they should differ from the site (e.g. read-only for most users).
- Add metadata columns for the structure you need (document type, owner, status).
- Create useful views (default view, group-by-type, missing-metadata, etc.).
- Document the library’s purpose for users and future admins.
Best practices
- One library per content type or major process. Don’t try to fit everything in ‘Documents’.
- Plan metadata before uploading content. Adding columns later requires backfilling.
- Set permissions at library level. Avoid file-level permissions where possible.
- Assign a library owner. Someone accountable for keeping it organised.
Common mistakes
- Creating libraries as if they were folders. Library = significant content type. Folder = organisation within a library.
- Library sprawl. Creating new libraries for every minor variation. Often a content type or metadata column is the right answer.
- Forgetting governance. Library settings (versioning, retention, permissions) need to match the content’s importance.
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
How do I create a new SharePoint document library?
From the site home, click + New -> Document library. Give it a name (plain English, no abbreviations). Click Create. The library appears with default settings. Spend the next 10 minutes on the columns, views, and permissions — that’s what makes the library work long-term.
What should I do after creating a SharePoint library?
Five things: (1) add a clear description; (2) define the metadata columns the library needs (Document Type, Department, Status are common); (3) build at least one filtered view that hides clutter; (4) set permissions narrower than default if needed; (5) consider versioning settings before users start uploading.
Should I use a library or a folder structure in SharePoint?
Libraries are the right answer almost always. A library with metadata columns scales to thousands of files without performance issues; a deep folder structure breaks down past a few hundred. Treat libraries as the unit of organisation; use metadata, not folders, to categorise within.
What’s the difference between a SharePoint library and a folder?
A library is the top-level container with its own permissions, columns, views, and settings. A folder is a sub-container inside a library — limited to organising content, no independent settings. Libraries are designed for scale; folders are designed to organise small groups of related files within a library.