Skip to content
Skip to main content
Cloud Services Technical Explainer

What is an offline cloud file?

An offline cloud file is a local working copy that the cloud service keeps available when the device has no network connection. It remains associated with a provider object, but its local content and the provider's current version can temporarily diverge.

Offline availability changes where work can happen

An online-only placeholder normally retrieves content when needed. Marking an item or folder for offline use causes the client to store the full content locally. The user or an administrator may choose that setting, or an application policy may apply it automatically.

While disconnected, the device can open and edit the local copy. The provider cannot record those actions as cloud events at that moment because it has not yet received them. Local application, filesystem and sync-client records may be the only contemporary sources.

Reconnection creates a second event sequence

Time (UTC) State Event
07:40 Connected Version V-12 stored offline on Dave's Surface Laptop
09:18 Offline Dave's local document edited and saved
10:02 Elsewhere Another user creates provider version V-13
11:26 Reconnected Dave's Surface submits its change; service creates V-14 or a conflict copy

The provider's 11:26 event records receipt of the later upload, not necessarily the time the words were written. The local 09:18 activity explains what happened while the service could not see the device.

Reconnect joins two histories; it does not erase either one
EstablishedThe joined histories can establish an offline local edit and the later time the provider accepted or reconciled it.
Still openWho authored the edit and how the service resolved competing content if the detailed record is unavailable.

Conflicts and delayed propagation matter

Services handle competing versions differently. Some preserve both, some merge changes, and some select a winner while retaining version history. A later sync can also propagate deletions or permission changes that occurred while the device was away.

Useful relationships include the provider object and version IDs, the local path, the device or client ID, the last successful sync, queued changes and any conflict record. These place the offline work into the wider synchronisation chain.

Offline status does not prove interaction

The existence of a full offline copy establishes local availability. It does not by itself prove that the user opened or read it; an entire synced folder may have been configured for offline use automatically. Later application and device activity can address actual use.

Current OneDrive offline example - checked 3 September 2026

OneDrive currently lets a user mark files or folders “Always keep on this device”, which downloads content for offline availability. Microsoft also notes that simultaneous or offline edits can lead to sync conflicts. Exact conflict handling and client records vary, so preserve the local write, queued submission, provider version history and reconciliation result rather than inferring edit time from the later cloud event.

The point to remember

An offline cloud file has a local history while disconnected and a provider history when synchronisation resumes. Compare both to distinguish when work occurred from when the service recorded it.

Reference: CLD-059Cloud Services