Should we use folders or metadata in SharePoint?

Key facts

• Folders are familiar and sync well to OneDrive, but each file can live in only one folder.
• Metadata lets one document be found by several attributes through views, filters and search.
• Long, deep folder paths cause sync and path length problems.
• Large libraries work better with indexed columns and filtered views.
• Default column values per folder can tag files automatically, combining both approaches.

The real trade-off

Folders answer one question: where does this file live. Metadata answers many: which client, which document type, what status, which year. A contract can only sit in one folder, but it can carry a client, a contract type, an expiry date and an owner as columns, and appear in every view that needs it.

Users like folders because they know them from file shares, and folders sync predictably to File Explorer through OneDrive. Metadata pays off when people search and filter instead of browse, and when the same documents need to be seen in different ways by different teams.

When folders are the right answer

Folders work well for a small number of top-level groupings people naturally browse, such as one folder per client or per project inside a library. They also help when a set of files needs a different default retention label, or, sparingly, different permissions.

Keep them shallow. Deep trees from file shares create long paths that break sync and make Microsoft 365 limits on URL length a real problem, and they hide files from people who do not know the path.

When metadata is the right answer

Use metadata when people ask for documents by attribute rather than location: all signed contracts expiring this year, every policy owned by HR, all drawings in Approved status. Choice columns, managed metadata from the term store and date columns make these views simple.

Content types bundle a set of columns and a template for a kind of document, such as Contract or Policy. They are worth it for structured, repeatable documents and less so for general team files.

• Keep required columns to the few that matter; every required field is friction.
• Use the term store for shared vocabularies like departments or regions.
• Index columns used in views on large libraries.
• Create views for the top questions people actually ask.

A practical hybrid

Most libraries end up with one or two folder levels and a handful of columns. Column default values can be set per folder, so a file dropped in the Acme folder is tagged with client Acme automatically. Users browse folders as they always have, while views and search can still filter by client, type or status.

Separate libraries are another tool. If documents have a very different structure, audience or retention, a new library is often cleaner than more folders or more columns.

Folders, metadata and Copilot

Microsoft 365 Copilot and SharePoint search respect permissions, so the structure that matters most for safety is who can access each site and library. Metadata and clear titles do help people and search find the right version, and labeling final or approved documents reduces the chance of drafts being used. During a migration, use the move to flatten deep trees and add a few useful columns rather than copying the file share as is.

How Accred Consulting approaches it

Accred Consulting designs library structure as part of SharePoint migrations and governance projects. Discovery maps existing file shares or libraries, path depth, permissions and how teams look for documents, and the proposal sets scope, fixed price and timeline. The US-based specialists assigned to your engagement design sites, libraries, folder levels, columns, content types and views, then migrate content with tools such as Migration Manager or the SharePoint Migration Tool. Handover includes documentation, owner training and knowledge transfer, with optional support retainers.

Track record: 475+ client projects, 2,000+ migration workstreams and 210,000+ users migrated by a US-based team. Company facts · Case studies

Related questions