OneDrive Files On-Demand Trims 80 GB of Synced Photos From a Surface Laptop

OneDrive Files On-Demand keeps a placeholder on the local NTFS volume in place of the full byte content. The placeholder carries the file name, file size, thumbnail, and metadata, and it registers with the Windows Cloud Files API as a reparse point. File Explorer reads that reparse point and displays the item as though the whole file were sitting on the drive.

When an application opens the file, the OneDrive sync engine handles the read request and downloads the content at that moment. On the Surface Laptop in this case, roughly 80 GB of camera-roll uploads had accumulated since 2020. Dehydrating those files returned the allocated block space to the SSD while leaving the folder layout and cloud copies unchanged.

Converting the Pictures folder to placeholders

Windows 11 ships with Files On-Demand enabled, although that setting alone does not convert files that have already been downloaded. Existing files remain fully present on disk until a folder or file is told to give up its local copy.

Open the OneDrive activity center from the system tray. Select the gear icon, choose Settings, then go to Sync and backup. Under Advanced settings, the Files On-Demand control should show Free up disk space as available. If the setting already appears active, the per-folder conversion still has to happen separately.

File Explorer is the quickest route. Go to the OneDrive root, right-click the Pictures folder, and choose Free up space. The status icon changes from a green circle with a white check to a blue cloud outline. In OneDrive’s icon language, the green check means locally available, while the blue cloud means online-only.

The reported size can look contradictory immediately afterward. The size-on-disk value drops because NTFS releases the data clusters as the files are dehydrated. The logical file size in Properties stays the same, since the placeholder still represents the full photo. A folder can therefore appear unchanged by logical size while its allocated footprint has collapsed.

Files marked Always keep on this device carry a solid green circle. Those files will not dehydrate through repeated Free up space commands until the pin is removed. Clear that pin from the same right-click menu, then run Free up space again.

On managed Surface devices, Group Policy or Intune can pin whole libraries centrally. When that policy is in force, the local right-click option can be greyed out. The status icon then reflects a policy decision rather than a folder setting chosen by the person using the laptop.

The operation does not compress the photos. It removes the local byte content and leaves behind a cloud-file placeholder that can be hydrated later. The folder tree, file names, thumbnails, and metadata remain visible, which is why a photo archive can still feel locally present after the SSD has been given back most of the space.

Checking the 80 GB reclaim with WizTree

WizTree reads the NTFS Master File Table directly. On a 256 GB SSD, a full scan finishes in two to three seconds because the program is not walking the directory tree file by file.

Run a scan of the C: volume before dehydrating the OneDrive Pictures folder. Run the scan again after Free up space completes, then compare the Users\<name>\OneDrive branch. A dehydrated placeholder reports an allocated size near zero while its logical size remains whole.

Enable both Size and Allocated columns in WizTree. The Size column reflects the represented file size, while Allocated shows the space actually reserved on the SSD. Files On-Demand creates a large gap between those columns for online-only photos.

Storage Sense gives a less direct view. It reports storage by category, and its readout can trail actual cluster deallocation by a full sync cycle. WizTree shows the byte change as soon as the reparse points are written, so the roughly 80 GB result can be checked against the disk itself.

That difference also explains why Properties can mislead during a quick inspection. A logical size that still reads like a full camera archive is compatible with a tiny allocated size on disk. The cloud placeholder is representing the file, while NTFS is no longer reserving the photo’s full data clusters locally.

Image backups store the placeholder

A local image backup taken while a file is dehydrated captures the reparse point. The photo bytes are absent from that image, so a bare-metal restore brings back stubs that re-download only after signing into the same OneDrive account.

What changes when a photo is opened

Every dehydrated photo depends on the network at the point of use. Opening an online-only image while offline returns a file-not-available error until connectivity comes back. On a slow connection, a 40 MB RAW file produces a visible wait before the application can read the full content.

The 80 GB gain on the Surface Laptop assumes ordinary broadband use. Under that condition, typical image files re-download with latency under a second, so the placeholder model feels close to having the photos stored locally. The same archive behaves differently away from a dependable connection.

A photographer preparing to cull a shoot during a flight has to hydrate the working set ahead of time. That means selecting the relevant folders and marking them Always keep on this device the night before. The solid green circle returns for those files, and the SSD space for that folder is consumed again while the pin remains.

The setting can move both ways at any time. Free up space dehydrates a folder back to online-only, while Always keep on this device hydrates and pins it locally. The visible folder structure survives either state, which makes the storage tradeoff easy to miss unless the Allocated column is being checked.

Files On-Demand changes where the bytes live while File Explorer continues to show the same photo library. The remaining choice sits at folder level: which photo sets should keep a solid green circle when free space starts shrinking again?