Windows
Yes, OneDrive files stored locally on your computer take up space when synced to the 'Files On-Drive' folder, but files saved only to OneDrive’s cloud or marked 'Online Only' won’t occupy your hard drive. You can adjust sync settings in the OneDrive app to manage what stays offline.
OneDrive’s storage behavior depends entirely on how you set up syncing.
Files in the 'Files On-Drive' folder mirror your cloud storage locally, which means they eat up your hard drive space just like any other file. 💻 However, when you save files directly to OneDrive’s cloud or mark them as 'Online Only,' they only appear when you open them—no local copies mean no storage impact.
I’ve seen people accidentally fill up their drives by syncing entire photo libraries or large project files without realizing it. The key is checking your OneDrive settings regularly to clean up what you don’t need offline.
💡 In This Article
- How OneDrive Sync Settings Affect Local Storage
- Freeing Up Space When OneDrive Files Clutter Your PC
How OneDrive sync settings affect local storage
OneDrive uses three core sync modes that dramatically impact your hard drive space: 'Files On-Drive', 'Online Only', and 'Save to Device'.
When you enable 'Files On-Drive', OneDrive creates complete local copies of all files in your cloud storage, mirroring them in a dedicated folder on your PC. This means a 50GB photo library in the cloud will occupy the same 50GB on your hard drive.
The sync process uses Windows' background intelligence to prioritize active files while maintaining a full offline copy.
Here's where it gets technical: OneDrive maintains a file versioning cache that stores previous versions of documents for up to 30 days (configurable). Each version creates additional hidden files in your OneDrive folder, adding 10-20% extra storage beyond your original files.
For example, a 1GB Word document with 5 versions might actually consume 1.5GB locally. The system uses Windows Indexing Service to track these versions, which also consumes minimal system resources but adds to the overall footprint.
The 'Online Only' mode changes everything by creating only a placeholder file (typically 4KB) that launches the full file from the cloud when opened. This is perfect for large files you rarely need offline, like 4K video projects or multi-gigabyte datasets.
What's fascinating is how OneDrive handles these placeholders: they appear as regular files in File Explorer but have a distinctive cloud icon and zero disk usage until opened. This mode is particularly useful for Windows 10/11 users with SSDs, where preserving limited storage is critical.
Windows integrates OneDrive storage with system settings through the 'Storage Sense' feature, which can automatically clean up temporary files including OneDrive cache. However, this often misses versioned files unless you manually adjust the recycle bin settings to 30 days (the default).
The system also reserves 5GB of your hard drive for OneDrive's temporary operations, which can fill up if you're frequently editing large files offline. I've seen this cause issues with users who have 128GB SSDs, where even small cache buildup becomes problematic.
What most people overlook is the 'Save to Device' option, which creates local copies but doesn't sync them to the cloud. This is useful for files you want to keep permanently offline, like large media libraries or local backups. The catch?
These files don't appear in your OneDrive cloud storage at all, creating potential sync conflicts if you later try to access them through the web interface. The system maintains separate metadata for these files, adding another layer of complexity to storage management.
Understanding these mechanics helps explain why some users see their hard drives fill up unexpectedly. For instance, a 1TB external drive connected via OneDrive might appear to have 900GB free in File Explorer, but the actual usable space is less after accounting for OneDrive's hidden files and versioning.
The solution often lies in running OneDrive's built-in storage analyzer tool, which breaks down exactly how your space is being consumed across sync modes.
