Guide
Timestamp and Timezone Checklist for Logs and Reports
A practical checklist for converting seconds, milliseconds, ISO dates, UTC, and local time without confusing event order.
Identify the timestamp unit first
Many systems store Unix time in seconds, while browsers and some APIs use milliseconds. A value that is off by a factor of 1000 can point to the wrong year, so confirm the unit before interpreting the result.
Use UTC for cross-system comparison
Server logs, databases, analytics exports, and API events may come from different regions. Convert to UTC when you need to compare order, latency, or incident timelines across systems.
Use local time for human communication
After the technical timeline is clear, convert key moments into the reader's local time. This helps support teams, customers, and operators understand when something happened without changing the source-of-record timestamp.
Watch daylight saving changes
Historical and scheduled times can shift around daylight saving transitions. If the exact local time matters, verify the timezone name and date rather than relying only on a short abbreviation.
Keep the original value in notes
When documenting an incident or report, keep the original timestamp next to the converted value. This makes later review easier if another tool or timezone setting produces a different display.