Use the converter to move between epoch seconds, milliseconds, ISO 8601 and readable local time. The timezone view shows the same instant in several zones at once, and the reference pages explain the language-specific snippets and the 2038 boundary.
Timestamp & Epoch
A Unix timestamp is a single number: seconds since 1 January 1970 at 00:00 UTC, not counting leap seconds. It is unambiguous and sortable, which is why APIs and databases prefer it. It becomes confusing the moment a value has thirteen digits instead of ten, or a date string has no timezone at all.
What people use these for
- Check whether an API returned seconds or milliseconds before writing it to the database.
- Turn a log timestamp into the local time of the user who reported the bug.
- Generate the exact ISO string a scheduled job or JWT claim expects.
- Understand why a date input shifted by one day after a timezone change.
Tools in this family
8 interactiveCurrent Timestamp
See the current Unix timestamp in seconds and milliseconds, updating live, with UTC, ISO 8601 and local time alongside.
Timestamp Converter
Convert between Unix timestamps and human dates in both directions. Auto-detects seconds versus milliseconds and shows UTC, ISO 8601 and local formats.
Epoch to Date
Convert a Unix epoch value into UTC, ISO 8601, RFC 2822 and local dates. Works with seconds and milliseconds, including values before 1970.
Date to Epoch
Turn a local date and time into Unix seconds or milliseconds. Handles timezones and dates before 1970.
Timestamp in Milliseconds
Convert millisecond timestamps to dates and back. See how ms differ from seconds, and where the 13-digit format is used in JavaScript and APIs.
ISO 8601 Converter
Convert ISO 8601 date strings to Unix timestamps and back. Handles Z, offsets, fractional seconds and date-only strings.
Timestamp Timezone Converter
View the same Unix timestamp in UTC and major IANA timezones at once, including offsets and daylight saving status.
Relative Time Calculator
Convert relative phrases like 3 days ago, 2 hours from now or last Monday into exact dates and Unix timestamps.
Guides and reference
4 pagesTimestamp in Code
Copy-ready snippets for getting, converting and formatting Unix timestamps in JavaScript, Python, Java, Go, PHP and SQL.
Timestamp Formats
Compare Unix seconds, milliseconds, ISO 8601, RFC 2822, RFC 3339 and SQL timestamp formats with examples and the right use case for each.
What Is Epoch Time
Unix epoch time counts seconds since 1970-01-01T00:00:00 UTC. Learn why it exists, how it handles leap seconds, and where it breaks.
Year 2038 Problem
The Year 2038 problem affects 32-bit Unix timestamps. Learn the exact overflow moment, which systems are at risk, and how to audit your stack.
Seconds, milliseconds, and the ten-digit test
Unix time is traditionally measured in seconds, but JavaScript's `Date.now()` returns milliseconds. A ten-digit value is almost always seconds; a thirteen-digit value is milliseconds. A quick sanity check: 1,700,000,000 seconds is November 2023, while 1,700,000,000,000 milliseconds is the same instant. If a converted date lands in 1970 or in the year 50,000, the unit is wrong.
ISO 8601 and the missing timezone
`2026-11-18T09:00:00Z` is an instant. `2026-11-18T09:00:00` is a wall-clock time with no offset, and every consumer is free to interpret it differently. When a date crosses a system boundary, keep the offset or store UTC. Formatting for display can happen at the edge, after the instant is fixed.
Frequently asked questions
Is Unix time UTC?
Yes. The number represents an instant; the display timezone is a separate choice. Two people in different zones see different clock times for the same timestamp.
What is the 2038 problem?
Systems storing Unix seconds in a signed 32-bit integer overflow on 19 January 2038. Use 64-bit integers or another representation for long-lived data.
Why does a timestamp show the wrong day?
Usually a unit mismatch (seconds treated as milliseconds) or a wall-clock string interpreted in the wrong zone. Check both before changing the value.