SharePoint hides more file and folder metadata than the default list view ever shows you. Every item in a document library carries dozens of properties: system columns, content type identifiers, sync tokens, retention labels, and internal IDs, and most of them are switched off in the view you look at every day. Some can be turned on in a few clicks. Others were never designed to appear as a column at all.
What counts as a "hidden" property
Two different things get lumped together under "hidden properties," and the distinction matters for how you get at them. The first is a hidden column: a field that exists in the library's schema, was created automatically when the library was provisioned or a feature was enabled, but is switched off in every view by default. The second is a hidden property in the stricter sense: metadata stored against the item at the platform level, such as an internal unique identifier or a client-side sync token, that was never intended to be exposed as an addable column in the first place.
Knowing which category you're dealing with saves time. If it's a hidden column, library settings will get you there in under five minutes. If it's a true hidden property, you need a tool that reads the underlying item object rather than the list view.
Reveal hidden columns through library settings
Most of what people mean by "hidden metadata" is actually sitting in the schema already, just switched off.
Turn on the hidden system columns
- Open the document library and click the gear icon, then Library settings.
- Under Columns, click Add from existing site columns.
- Change the "Select site columns from" dropdown to All Groups. This surfaces columns that live in groups such as "Base Columns," "Content Feed Columns," and "_Hidden" that don't show up in the default group filter.
- Select the columns you want and add them to the library.
Add them to your current view
- Once a column exists on the library, it still won't render anywhere until it's added to a view.
- Open the view (or create a new one), and under "Columns" tick the box for each newly added field.
- Save the view. The properties now render as visible fields against every item.
Properties no view will ever show you
A second tier of metadata never appears in the "Add from existing site columns" list, no matter how you filter it. This includes the item's internal unique identifier (a GUID assigned at creation and used internally by SharePoint to track the item across renames and moves), certain workflow instance data left over from classic SharePoint workflows, client-side sync tokens used by the OneDrive sync client, and some retention and compliance metadata attached by Microsoft Purview policies. These properties exist. They are readable. They simply were never wired into the "add as a column" mechanism, because Microsoft never intended for a typical user to browse them from a list view.
For most day-to-day admin work this doesn't matter. It becomes relevant during forensic investigations (working out exactly when an item's unique identifier changed after a restore), migration planning (confirming whether metadata will carry across a cross-tenant move), and troubleshooting sync issues where the sync client and the server disagree about an item's state.
Seeing everything at once with Explore Master
Rather than toggling column settings library by library and still coming up short on the properties that never surface as columns, ShareMaster's Explore Master reads the underlying item and file objects directly. It surfaces the full property set, hidden columns and true hidden properties alike, in a single browsable view per file or folder, without needing PowerShell or repeated trips into library settings across dozens of libraries.
This matters most when you're auditing a small number of specific items in detail (a legal hold candidate, a file with a suspicious modification history, an item behaving oddly during sync) rather than trying to build a report across an entire tenant, which is a job better suited to Report Master's Excel exports.
Common hidden SharePoint properties worth knowing
| Property | What it stores | Why it matters |
|---|---|---|
| UniqueId | Internal GUID assigned to the item at creation | Used to track an item across renames, moves, and restores; useful when diagnosing orphaned-file or duplicate-item issues |
| ContentTypeId | Hierarchical identifier for the item's content type | Determines which columns and workflows apply; relevant when auditing content type inheritance |
| _UIVersionString | Current major.minor version number as text | Not always visible by default; useful alongside version count when planning a version trim |
| vti_synccontenttag | Sync token used by the OneDrive sync client | Changes when the item is modified; useful when troubleshooting sync loops or stuck uploads |
| _ModerationStatus | Content approval status for libraries with approval enabled | Explains why a file is invisible to some users despite existing in the library |
| ParentUniqueId | Unique identifier of the containing folder | Useful for rebuilding a file's location history after a move or bulk reorganisation |
Frequently Asked Questions
Why can't I see all SharePoint file properties in the default view?
SharePoint creates dozens of system columns automatically when a library is provisioned, but only shows a small subset in the default view to keep the interface simple. The rest exist in the list schema and can be added to a view, though some internal properties are never exposed as addable columns at all.
Can I see hidden SharePoint properties without PowerShell?
Yes. Library settings expose most hidden columns through the "Add from existing site columns" screen with the group filter set to All Groups. For properties that never surface as columns, a property explorer tool reads them directly rather than requiring a PowerShell script.
What is the difference between a hidden column and a hidden property?
A hidden column is a field that exists in the list schema and can be surfaced through view settings. A hidden property, such as an internal unique identifier or a sync token, is stored against the item but was never designed to be shown as a column in a list view at all.
Summary
Most hidden SharePoint metadata is a few clicks away in library settings once you know to change the site columns filter to All Groups. What's left over, the identifiers and sync tokens that never surface as addable columns, needs a tool that reads the item directly. Between the two approaches, there's very little about a SharePoint file or folder that stays genuinely out of reach.