Unix Timestamp Converter
This Unix timestamp converter turns an epoch value into a readable date — or a date into a timestamp — with seconds and milliseconds detected automatically. See the same instant as ISO 8601, UTC, local time and RFC 2822, plus what the clock says in ten major cities.
How to use Unix Timestamp Converter
- Paste a Unix timestamp; the tool works out whether it is in seconds, milliseconds or microseconds.
- Or switch to date mode and pick a date and time to get the matching epoch value.
- Read the converted instant in ISO 8601, UTC, local time and RFC 2822 format, with relative time alongside.
- Scan the time-zone table to see the same moment in ten major cities around the world.
- Copy the current timestamp straight from the live clock at the top whenever you need “now”.
About Unix Timestamp Converter
Unix time is the closest thing computing has to a universal instant: a single integer counting seconds since the start of 1970 UTC, with no zone, no locale and no ambiguity. Every layer above it — your log aggregator, your database, your JWT expiry, your cron scheduler — either stores that number or converts to it. The trouble is that humans cannot read it, and the conversion is where the bugs live.
This converter handles both directions and, importantly, the unit question. JavaScript reports milliseconds, most back ends report seconds, and some tracing systems report microseconds or nanoseconds; feeding one into a parser expecting another produces a date in 1970 or in the year 54,000. Magnitude detection removes that guesswork and states plainly which unit was assumed. From there the same instant is rendered as ISO 8601, a UTC string, your local time with its real offset, RFC 2822 for email headers, and a relative phrase such as "3 hours ago".
Time zones are the other half of the problem, and they are handled through Intl.DateTimeFormat with IANA zone identifiers rather than fixed offsets. That distinction matters: America/New_York is UTC−5 in January and UTC−4 in July, and a timestamp from six months ago must be converted with the offset that applied then. The world-clock table shows the same instant across ten major zones so you can answer "what time was this for them?" without arithmetic.
Frequently asked questions
What is a Unix timestamp?
The number of seconds elapsed since 00:00:00 UTC on 1 January 1970, known as the Unix epoch. It has no time zone and no daylight-saving rules, which is exactly why systems store instants that way and convert to local time only for display.
Seconds or milliseconds — how do I tell?
By magnitude. Current times in seconds are ten digits; in milliseconds they are thirteen. This converter detects the unit automatically and shows which one it assumed, so a JavaScript Date.now() value is not read as a date in the year 54,000.
Does it handle time zones and daylight saving?
Yes. Local conversions use your device’s IANA time zone through the Intl API, which carries the full daylight-saving history, so a timestamp from last July converts with the offset that was actually in force then rather than today’s.
What is the year 2038 problem?
Systems that store the epoch in a signed 32-bit integer overflow on 19 January 2038, wrapping to 1901. Anything using 64-bit time — which includes JavaScript, modern Linux and every current database — is unaffected. The converter itself has no such limit.
Why does my timestamp show as 1970?
Almost always because a millisecond value was divided, or a seconds value was interpreted as milliseconds, leaving a number close to zero. The other classic cause is a null or empty field defaulting to 0, which is the epoch itself.
What format should I use in an API?
ISO 8601 with an explicit offset — 2026-08-09T14:32:00Z — for anything human-readable or interchange-facing, and integer epoch seconds for internal storage and comparisons. RFC 2822 remains the required format in email headers.
Related tools
- JSON Formatter — Beautify, validate & minify JSON
- Base64 Encoder & Decoder — Text and files to Base64, both ways
- JWT Decoder — Decode and verify JSON Web Tokens
- Regex Tester — Test regular expressions live
- Diff Checker — Compare two texts line by line
- URL Encoder & Decoder — Percent-encode and inspect URLs