What is the difference between created, uploaded, modified and synchronised times?¶
They mark different stages in a file's history. None should be treated as a universal “date of the file”, because each belongs to a defined event and system.
Four common stages¶
- Created: the local item or provider object first came into existence in that system.
- Uploaded: content was transferred into the cloud service.
- Modified: content or recorded metadata changed.
- Synchronised: a client and provider exchanged or reconciled state.
A document might be created on Monday, uploaded on Tuesday, edited online on Wednesday and downloaded to another device on Thursday. That second device may record Thursday as its local creation time.
Copying can start a new clock history¶
Moving content between accounts, exporting it, restoring a backup or converting format may create a new object with new timestamps while preserving older internal metadata. Conversely, a rename may leave the provider object ID and version history intact.
The label alone is not enough. Confirm which object or copy it describes, the field definition, time zone and source system.
Reconstruct rather than choose¶
Where timing matters, place the relevant values into one sequence and explain the mechanism connecting them. Cloud and device metadata can differ legitimately; a mismatch may identify when a copy arrived or when delayed synchronisation occurred.
The earliest timestamp does not necessarily identify authorship. It may be copied from a template, imported from another file or generated by a clock that was wrong.
Dave creates briefing.docx locally at 08:40. OneDrive accepts upload UP-204 as object OBJ-4407 at 09:05, Word for the web saves version V-19 at 10:12, and sync client OD-77 reconciles that state to Priya's laptop at 10:15. The sequence establishes four stages; no single value is the universal date of the document.
The next useful comparison is each object's stable ID and timestamp definition against upload, version, sync and device records, with time zones and clock accuracy preserved.
Current Microsoft file-time example - checked 3 September 2026
Microsoft Graph currently documents service-level creation and modification times for drive resources and separate local file times in fileSystemInfo. The provider-neutral rule is to keep every timestamp attached to its object, source and event.
The point to remember
Created, uploaded, modified and synchronised times describe separate events. Keep their objects and sources attached, then use the sequence to explain the file's journey.