Is a Unix timestamp always UTC?
Yes. A Unix timestamp counts elapsed seconds since 1970-01-01 00:00:00 UTC. Timezone only changes how humans display that instant.
Developer tool
Unix timestamp converter
Convert Unix seconds, milliseconds, ISO 8601 and local date strings. The parser calls out seconds-vs-milliseconds so log timestamps do not silently drift by decades.
Detected: Unix seconds
Quick calculations
1 minute
60 seconds
1 hour
3,600 seconds
1 day
86,400 seconds
30 days
2,592,000 seconds
Common implementation snippets
JavaScript
new Date(1767225600 * 1000).toISOString()Python
datetime.fromtimestamp(1767225600, tz=timezone.utc)Go
time.Unix(1767225600, 0).UTC()Java
Instant.ofEpochSecond(1767225600)PostgreSQL
to_timestamp(1767225600) AT TIME ZONE 'UTC'MySQL
FROM_UNIXTIME(1767225600)Unix timestamp FAQ
Why does JavaScript multiply seconds by 1000?
JavaScript Date uses milliseconds, while many APIs and logs store Unix seconds. Passing seconds directly to new Date() is the most common source of 1970-era bugs.
How do I recognize seconds vs milliseconds?
Current Unix seconds are 10 digits; current Unix milliseconds are 13 digits. This converter auto-detects by digit length and shows the detected mode.
Is RFC 3339 different from ISO 8601?
RFC 3339 is a stricter internet profile of ISO 8601. For API timestamps, an ISO string like 2026-01-01T00:00:00Z is normally safe and RFC3339-compatible.