Skip to main content

Created Column

The Created column is a read-only date and time stamp that SharePoint writes automatically the moment an item is added to a list or a file is uploaded to a library. It is one of the standard out-of-the-box columns on every list and library. The value is set once at creation and never changes, however often the item is later edited. Its internal name is Created, its type is Date and Time, and the value is stored in UTC then shown in each viewer's regional time zone. You cannot edit it in the browser, only through code during a migration. Use it to sort newest-first, build an audit trail, or drive retention rules.
Related
Created By Column, Date and Time Column, Modified By Column, Modified Column, Retention Labels, Version History
See It In Action

Common Use Cases

  • Newest-first sorting: order a document library or list so the latest additions surface at the top
  • Audit and compliance: prove when a record first entered the system for legal or policy review
  • Retention triggers: drive clean-up or archival rules based on how old an item is
  • New-content rollups: filter a view or Highlighted Content web part to items created in the last 7 or 30 days
  • Onboarding checks: confirm when a policy, form, or file was first published to a site
  • Migration validation: compare original creation dates after moving content between tenants

How It Works

  • Set once, automatically: SharePoint stamps the value at item creation with no user input
  • Never changes: later edits update Modified, not Created
  • Stored in UTC: the underlying value is coordinated universal time, not local time
  • Displayed by locale: each user sees the date in their own regional time zone and format
  • Date and Time type: the column behaves like any other date field for sorting and filtering
  • Internal name Created: referenced as Created in views, JSON formatting, and Power Automate

Benefits

  • Zero setup: the column is already present, so there is nothing to create or configure
  • Tamper-resistant: read-only in the browser, so users cannot backdate their own items
  • Consistent everywhere: the same behavior on every list and library across the tenant
  • Time-zone aware: distributed teams each see a locally correct timestamp
  • Automation-ready: a reliable trigger and filter value for flows and retention
  • Reporting friendly: clean data for grouping content by day, month, or quarter

Limits and Nuances

  • Not editable in the UI: there is no browser control to change the creation date
  • Changeable only by code: PowerShell or the object model can overwrite it, mainly for migrations
  • Distinct from Modified: Created is fixed while Modified moves with every change
  • Copy resets it: copying a file to a new location creates a new item with a new Created value
  • Migration can distort it: poorly configured migrations may stamp the migration date instead of the original
  • UTC vs display confusion: a value near midnight can appear on a different calendar day per time zone

Common Questions About the Created Column

What is the Created column in SharePoint?

The Created column is a built-in, read-only date and time field that SharePoint fills in automatically when an item is added to a list or a file is uploaded to a library. It records the exact moment the item first came into existence and never changes after that. It appears out-of-the-box on every list and library, so you do not create or configure it, and you can add it to any view for sorting, grouping, or filtering.

Can I change the Created date on an item?

Not through the browser. The Created column is read-only in the SharePoint interface, which is deliberate, because a trustworthy creation timestamp underpins audit and retention. The value can be overwritten with PowerShell or the object model, which is normally done only during a content migration to preserve the original creation dates from the source system. For everyday use, treat it as a fixed, tamper-resistant fact.

What is the difference between Created and Modified?

Created records when an item first appeared and never changes. Modified records the most recent change and updates every time someone edits the item or its metadata. Created answers ‘when did this arrive?’ while Modified answers ‘when was this last touched?’. Together with Created By and Modified By, they give you a simple four-column audit trail without any add-ons.

Why does the Created time look wrong to some users?

SharePoint stores the value in UTC and then displays it in each viewer’s regional time zone. Two people in different regions can see different clock times, and an item created near midnight can even appear on a different calendar day for each of them. This is correct behavior, not a bug. Site and personal regional settings control which time zone and date format each person sees.

Does copying or moving a file keep its Created date?

It depends on the action. Moving a file within SharePoint generally preserves the original Created value, while copying creates a brand-new item that gets a fresh Created stamp reflecting the copy time. Downloading and re-uploading always resets it. If preserving original dates matters, plan the operation carefully, because the difference between move and copy can quietly rewrite your audit history.

When should I rely on Created for reporting or retention?

Use it whenever you need a stable anchor for how long content has existed, such as ‘archive anything older than three years’ or ‘show items added this month’. Because it never shifts, it is more reliable than Modified for age-based rules. Greg Zelfond, the consultant behind LookBook 365, designs libraries and retention so these system columns do the heavy lifting, turning out-of-the-box timestamps into clean views, rollups, and governance rather than manual tracking.