Time zones and daylight saving: how to get them right
UTC, offsets, daylight saving and timestamps: what you need to schedule meetings and calculate dates without mistakes.
Convert timestamps in seconds or milliseconds to dates.
Runs in your browser
Current timestamp (seconds)
—
Read as seconds (10 digits for current dates).
| Your time (UTC) | Thursday, 1 January 2026 at 00:00:00 UTC |
|---|---|
| UTC | Thursday, 1 January 2026 at 00:00:00 UTC |
| ISO 8601 | 2026-01-01T00:00:00.000Z |
| Relative to now | 10 months ago |
| Seconds | 1767225600 |
| Milliseconds | 1767225600000 |
A Unix timestamp is the number of seconds (or milliseconds) since 1 January 1970 at 00:00 UTC. It's how many databases, APIs and logs store dates.
This tool converts it to a readable date in UTC and in your time zone, and back again. It tells seconds and milliseconds apart to avoid the classic mistake of getting dates in 1970 or the year 50,000.
1767225600 → 1 January 2026, 00:00:00 UTC.
1767225600000 is the same moment in milliseconds, as returned by Date.now() in JavaScript.
For current dates, 10 digits means seconds and 13 digits means milliseconds.
No. Unix time ignores them by definition, and so does this tool.
Yes, using negative timestamps.
UTC, offsets, daylight saving and timestamps: what you need to schedule meetings and calculate dates without mistakes.