What is the Content Created timestamp?

The Content Created timestamp (also called Date Created, Capture Time, or Date Taken) represents the moment the image content was originally recorded—i.e. when the camera captured the photo.

It is stored in image metadata (e.g. EXIF, IPTC, XMP) and describes a real-world event, independent of the file’s lifecycle on a computer.

Difference from File Timestamps

Content Created vs. File Created

• Content Created: When the photo was taken.
• File Created: When the file instance was created on a specific filesystem.

Key point: Copying or downloading a file changes File Created, but not Content Created.

Content Created vs. File Modified

• Content Created: Original capture time (stable).
• File Modified: Last time the file’s data changed (e.g. edits, metadata updates).

Key point: Editing metadata may update File Modified without affecting Content Created.

Types of Content Created Timestamps

1. Timezone-Aware (Absolute Time)

These timestamps define an exact moment in global time.

2024-03-10T14:32:05+01:00

• Include a UTC offset (e.g. +01:00)
• Can be converted unambiguously to UTC
• Represent the same instant worldwide

2. Wallclock (Naive Local Time)

These timestamps represent local clock time without timezone context.

2024:03:10 14:32:05

• No timezone information
• Reflect the camera’s displayed time
• Cannot be mapped to a unique global instant without assumptions

Absolute Offsets vs. Geopolitical Timezones

1. Absolute UTC Offset (e.g. +01:00)

• Fixed offset from UTC
• No daylight saving rules
• Precise for a specific instant, but no location context

2. Geopolitical Timezone (e.g. Europe/Berlin)

• Region-based identifier
• Includes Daylight Saving Time (DST) and historical rules
• Offset depends on the date (e.g. UTC+1 in winter, UTC+2 in summer)

Key Difference

Aspect	UTC Offset (+01:00)	Geopolitical Timezone (Europe/Berlin)
Encodes location	No	Yes
Handles DST	No	Yes
Changes over time	No	Yes (based on rules)

Summary

• Content Created describes when the image was actually captured.
• It is independent of filesystem timestamps like File Created and File Modified.
• It may be stored as:
  • Timezone-aware timestamps (precise, globally comparable)
  • Wallclock timestamps (local, ambiguous)
• Timezone-aware values may use:
  • UTC offsets (simple, fixed)
  • Geopolitical timezones (location-aware, DST-sensitive)

Important practical note:
Photo metadata standards generally do not provide a standardized way to store full geopolitical timezone identifiers (e.g. Europe/Berlin). As a result, timezone information is typically stored as an absolute UTC offset (e.g. +01:00 or +02:00).

This means:

• The original geopolitical timezone context is usually lost.
• The same location can produce different stored offsets depending on the date (due to Daylight Saving Time).
• Example:
  • Winter: +01:00
  • Summer: +02:00

For accurate interpretation, both the timestamp and its offset must be considered together.

Photo Date Adjustator will convert geopolitical timeszones into their respective absolute offset information when saving adjustments. Nevertheless, it makes sense to use geopolitical timezones over absolute timezone offsets in the application as it will allow you consistently shift photos between timezones, accurately representing daylight savings times, and only when persisting changes to the photo file, convert the timestamps accordingly to absolute timezone offsets.