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, version strings, approval status 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 column left out of the view: a field that exists in the library's schema, created automatically when the library was provisioned or a feature was enabled, but not ticked in any view by default. The second is a hidden field in the stricter sense: metadata stored against every item, such as its internal unique identifier, that SharePoint flags as hidden so it is never offered as a column in the first place.
Knowing which category you're dealing with saves time. If it's a column left out of the view, the view settings will get you there in under five minutes. If it's a hidden field, you need a tool that reads the underlying item rather than the list view.
Show the system columns through the view settings
Most of what people mean by "hidden metadata" is actually sitting in the schema already, just switched off.
Turn on the built-in columns
- Open the document library. From any column header choose Column settings, then Show/hide columns; or, for the full list, choose Edit current view from the view menu.
- Tick the system columns you need. The list includes fields such as ID, Version, File Size, Content Type, Checked Out To, Item Child Count and Folder Child Count, alongside any columns your organisation added.
- Save the view. The properties now render as visible fields against every item.
Don't use "Add from existing site columns" for this
The Add from existing site columns page in library settings adds a site column to the library as a new, empty column. It does not reveal values the library already holds, and site columns SharePoint marks as hidden are not offered there at all. If a column you expected is missing from the view editor, it is either a hidden field or it has never existed on that library.
Properties no view will ever show you
A second tier of metadata never appears in the view editor, no matter how you filter it. This includes the item's internal unique identifier (a GUID assigned at creation and used to track the item across renames and moves), the identifier of its parent folder, the server-relative path fields, the content type ID and the version string. These fields exist on every item and are readable through the API. They are simply flagged hidden, because Microsoft never intended 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 whether a restored item is the same object or a new one), migration planning (confirming whether metadata will carry across a cross-tenant move), and troubleshooting items that behave differently from their neighbours.
Seeing everything at once with Explore Master
Rather than toggling column settings library by library and still coming up short on the hidden fields, ShareMaster's Explore Master reads the underlying objects directly. For a file, folder or list item it lists every field value stored on the item, hidden fields included, alongside the properties SharePoint returns for the file or folder itself, and it has a tab for the item's version history. No PowerShell, and no 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) 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 and moves; 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 | Useful alongside version count when planning a version trim |
| FileRef and FileDirRef | Server-relative path of the item, and of the folder it sits in | Useful when matching items across an export, or when two files share a name in different folders |
| _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. Many of the rest can be added to a view, but some are flagged hidden and are never offered in the view editor at all.
Can I see hidden SharePoint properties without PowerShell?
Partly. The view's column picker exposes the built-in system columns the default view leaves off. For fields SharePoint flags as hidden, 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 column left out of the default view still exists in the list schema and can be added through the view settings. A hidden field, such as the item's unique identifier, is stored against the item but flagged so that the view editor never offers it as a column.
Summary
Most hidden SharePoint metadata is a few clicks away in the view settings once you know where the column picker is. What's left over, the identifiers and path fields SharePoint flags as hidden, 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.