Why UTC matters here
Unix timestamps are easiest to reason about when converted to UTC first. That removes local daylight saving ambiguity before you render a user-facing local time.
Unix time explained
What Unix or Epoch time means and how to convert timestamps to human-readable values.
Answer first
Unix time counts elapsed seconds from the Unix epoch.
Unix time is a machine-friendly representation of time that counts forward from 1970-01-01 00:00:00 UTC.
It is useful because it is compact and comparable, but humans still need to convert it into readable local or UTC times to reason about events.
Epoch start
1970-01-01 00:00:00 UTC
Best display reference
UTC first, local second
Human readable by default
No
Useful for sorting and storage
Yes
guide-unix-time-explained
728x90
Common mistakes
Developers mix milliseconds and seconds, assume a local time zone during conversion, or display a local time without labeling the zone.
- Confusing seconds with milliseconds
- Assuming server local time
- Dropping the time-zone label in UI output
Frequently asked questions
Is Unix time always UTC-based?
Yes. The Unix epoch reference is UTC-based, even if you later display a converted local time.
Why do some timestamps look too large?
Many systems store milliseconds instead of seconds, which makes the number three digits longer.