On this page
How it works
A Unix timestamp counts time from the epoch, 1 January 1970 at 00:00:00 UTC. The converter turns your number into milliseconds, builds a date from it and formats that date with the Intl API of your browser, which carries the official IANA time zone database including daylight saving rules.
Unit detection looks at the number of digits before any decimal point: up to 11 digits is read as seconds, 12 to 14 as milliseconds, 15 to 17 as microseconds and 18 or more as nanoseconds. The detected unit is shown under the field. Choose a unit yourself for dates close to 1970, where the digit count is ambiguous.
For the reverse direction, the date and time you enter is treated as wall clock time in the selected zone, and the tool finds the matching UTC offset for that exact moment, so dates on either side of a daylight saving change convert correctly.
Privacy
All conversions run locally in your browser. Timestamps and dates you enter are not sent to a server or stored, which makes it safe to paste values from production logs and incident timelines.
If you correlate events across systems often, a log management or monitoring and observability platform does this at scale. More utilities are listed under developer tools.
Tips
- JavaScript
Date.now()and JavaSystem.currentTimeMillis()return milliseconds. Unixdate +%s, Pythontime.time()and PHPtime()return seconds. - Store timestamps in UTC and convert only for display. It avoids most daylight saving bugs.
- Spaces, commas and underscores in the number are ignored, so 1_700_000_000 works.
- Pretty printing a JSON log line first makes timestamps easier to spot. Use the JSON formatter.
Limits
- Leap seconds are ignored, as in Unix time itself.
- Dates are shown to the millisecond. Microsecond and nanosecond input is rounded down to whole milliseconds.
- The supported range is about 270,000 years either side of 1970, the range of a JavaScript date.
- A date that does not exist in a zone, such as 02:30 on the night clocks spring forward, is moved by the size of the gap.
Frequently asked questions
What is a Unix timestamp?
It is the number of seconds since 00:00:00 UTC on 1 January 1970, the Unix epoch, not counting leap seconds. The same moment has the same timestamp everywhere, which is why logs, databases and APIs use it instead of local dates.
How do I tell seconds from milliseconds?
Count the digits. Current dates have 10 digits in seconds, 13 in milliseconds, 16 in microseconds and 19 in nanoseconds. The converter applies this rule automatically and shows which unit it picked, and you can override it with the Unit menu.
Which time zone does the converter use?
A timestamp itself has no time zone. The converter always shows UTC and your device time zone, plus any zone you choose from the list. When you convert a date to a timestamp, the date is read as wall clock time in the zone you select.
What is the difference between ISO 8601 and RFC 2822?
ISO 8601 (for example 2026-11-18T09:30:00.000Z) is the format used by JSON APIs and most programming languages. RFC 2822 (for example Wed, 18 Nov 2026 09:30:00 +0000) is the date format of email headers and some HTTP and RSS tooling.
What is the year 2038 problem?
Systems that store timestamps as signed 32 bit integers overflow at 2147483647, which is 03:14:07 UTC on 19 January 2038. Current 64 bit systems are not affected, but old embedded devices and file formats can be. Enter 2147483648 above to see the date just after the limit.
