Modern Niche World MNW

Timestamp Converter

Paste a Unix timestamp to see the date and time in UTC, your time zone and any other, or type a date and time to get its Unix timestamp.

Now

– seconds

Unix time to date

Date to Unix time

Year-month-day and a 24-hour time; seconds and fractions are optional. An ending such as Z or +02:00 sets the offset and overrides the zone.

Worked out on your device with your browser’s own time-zone data. Nothing is sent or saved.

Turn Unix time into a date you can read

Logs, databases and APIs often store time as a Unix timestamp: the number of seconds since midnight UTC on January 1, 1970. It’s easy for software and hard for people. This converter shows what a timestamp means in UTC, in your time zone and in any other, and turns a date back into a timestamp.

How to use it

  1. Paste a timestamp. The unit is guessed from its size; change it if the guess is wrong.
  2. Pick another time zone to compare, such as a server’s or a colleague’s.
  3. Copy the format you need: ISO 8601, RFC 2822, or the same moment in another unit.
  4. To go the other way, type a date and time below and choose its time zone.

The formats

  • ISO 8601, such as 2026-10-20T14:30:00.000Z, is the standard for data and APIs. Z means UTC; an ending like -04:00 gives the offset.
  • RFC 2822, such as Tue, 20 Oct 2026 14:30:00 +0000, is the format of email headers. It has no fractions of a second and covers years from 1900.
  • Units: seconds are classic Unix time; JavaScript and Java use milliseconds; some databases and tracing tools use microseconds or nanoseconds.

Worked examples

  • 1700000000 in seconds is Tuesday, November 14, 2023, 22:13:20 UTC, which was 17:13:20 in New York.
  • 1700000000123 is 123 milliseconds later, written in milliseconds, the form JavaScript’s Date.now() gives.
  • -14182940 is July 20, 1969, 20:17:40 UTC, the moment Apollo 11 landed on the Moon.

Time zones and clock changes

Offsets come from your browser’s time-zone database, so daylight saving time is taken into account for the date shown. When clocks go back, a local time happens twice and both moments are shown. When they go forward, a skipped time is moved forward by the gap, and the tool says so.

Good to know

  • The live readout at the top shows the current Unix time, updated every second; Convert now puts it into both boxes.
  • Leap seconds aren’t counted, by Unix time or by this tool.
  • Range: dates from about 271,821 BC to AD 275,760, the limits of a browser’s dates.
  • Precision: nanosecond timestamps are converted exactly, without rounding.
  • Planning a meeting across zones? The Time Zone Converter helps find a time that suits everyone.

Frequently asked questions

How does it tell seconds from milliseconds?
By the size of the number. A timestamp from this century has 10 digits in seconds, 13 in milliseconds, 16 in microseconds and 19 in nanoseconds. The guess is shown under the box; if it’s wrong, choose the unit yourself.
What about times before 1970?
Use a negative number: -86400 is December 31, 1969, 00:00 UTC. A negative timestamp with a fraction rounds down to the earlier moment, as Unix time does.
What happens to a time that’s skipped or repeated when clocks change?
When clocks go forward, a time such as 02:30 doesn’t exist that night; the tool says so and moves it forward by the gap, as most software does. When clocks go back, a time happens twice; the tool shows both moments.
Does it account for leap seconds?
No, and neither does Unix time: every day counts as exactly 86,400 seconds. That’s why second 60 can’t be converted.

Related tools

Next 10 runs

Cron Expression Explainer

Read a cron schedule in clear words, field by field, and see its next 10 run times in your time zone and UTC.

Open tool
DST-aware

Time Zone Converter

Find a meeting time that isn't 3am for someone. Compare everyone's hours at a glance.

Open tool
Decode only

JWT Decoder

Read a JSON Web Token’s header and claims, with expiry times in your local time. It decodes only and never verifies.

Open tool