Skip to tool
Systems

Unix Time Converter

Convert epochs and ISO dates with explicit units and timezone context.

Input3 characters
Result0 characters
Ready

Prefer a native workflow?

Keep Unix Time Converter one shortcut away.

DevSexy for Mac puts the same private workflow in a focused desktop app, with global shortcuts and no browser tab to manage.

Global shortcutOffline-readyLocal processing
Try the Mac app free

This browser tool remains free.

Timestamp interrogation desk · one number, four possible units

A number is not an instant until its unit is known.

Unix time is timezone-free arithmetic. Civil dates are policy. This converter keeps the unit gate, sub-millisecond remainder, UTC instant, and named-zone display on separate evidence rails.

Unit interrogation railRAW · 1710000000000
s

54,202 CE

unlikely API payload

ms

2024-03-09

common browser clock

µs

1970-01-20

database precision

ns

1970-01-01

system trace precision

Magnitude can suggest a unit; only the producing contract can prove it.

Try a timestamp with a known answer

Use the same instant to compare seconds, milliseconds, and an explicit UTC offset. The nanosecond example shows where the display stops preserving digits.

Loading an example replaces the current input and options. Relative time changes with your clock; the UTC values below stay fixed.

Convert epoch seconds to UTC

To Date · seconds · UTC. Select the unit explicitly instead of relying on digit count.

Input

1710000000

The UTC instant is March 9, 2024 at 16:00. Its millisecond value has three more zeroes.

2024-03-09T16:00:00.000Z
1710000000000

Read a JavaScript millisecond timestamp

To Date · milliseconds · Asia/Shanghai. Only the civil display uses the selected timezone.

Input

1710000000000

UTC stays at 16:00 on March 9; the Shanghai display moves to 00:00 on March 10.

2024-03-09T16:00:00.000Z
1710000000

Preserve a trace timestamp below one millisecond

To Date · nanoseconds · UTC. Keep the input as text so JavaScript number rounding cannot alter it first.

Input

1710000000123456789

The epoch ledger keeps all nine fractional digits. ISO shows .123 milliseconds plus an explicit 456789 ns remainder.

1710000000.123456789
2024-03-09T16:00:00.123Z · plus 456789 ns below the displayed millisecond

Convert an ISO date with an explicit offset

To Epoch · UTC display. The +08:00 in the input identifies the instant.

Input

2024-03-10T00:00:00+08:00

Midnight at +08:00 is 16:00 UTC on the previous day and equals the seconds example.

2024-03-09T16:00:00.000Z
1710000000

Signed epoch-zero axis

< 0

before 1970

0

1970-01-01T00:00:00Z

1,000

+ 16m 40s

now

current observation

future

same signed scale

One-instant ledger

Unix seconds1710000000
Unix milliseconds1710000000000
ISO 8601 UTC2024-03-09T16:00:00.000Z
America/New_YorkMar 9 · 11:00:00
Asia/ShanghaiMar 10 · 00:00:00
Relativederived at observation time

Wall-clock customs

An offset turns a wall clock into an instant.

2026-11-01T01:30AMBIGUOUSDST overlap in some zones
2026-03-08T02:30MAY NOT EXISTDST gap in some zones
2026-08-03T10:00ZEXPLICITUTC instant
2026-08-03T10:00+08:00EXPLICITsame instant as 02:00Z

Precision bridge

1
BigInt intake

integer evidence

2
nanosecond ledger

digits preserved

3
Date boundary

millisecond display

4
IANA formatter

civil-time projection

Incident board

1970 surprise

milliseconds divided twice

far-future date

seconds treated as milliseconds or the inverse

1,000× TTL

unit contract missing at API boundary

shifted meeting

timezone-less ISO parsed by environment

lost trace order

nanoseconds rounded into Date

Leap-second boundary

POSIX seconds are not an astronomical clock.

Unix/POSIX time does not number leap seconds as distinct instants. Use a timescale-aware system when UTC leap events or astronomical time are part of the requirement.

Follow a timestamp to its source

Inspect JWT exp and nbf claims

JWT NumericDate values use epoch seconds. Decode the token first, then convert the individual claim.

Find the timestamp in a JSON payload

Format the surrounding response and check which field and unit the producer documents.

Convert timestamps in the Mac app

Use the local offline toolbox when investigating logs repeatedly.

Direct answer

What is Unix Time Converter?

Convert Unix timestamps online between seconds, milliseconds, microseconds, nanoseconds, ISO 8601, and IANA timezone displays with explicit precision.

What can it do?

  • Now
  • Auto
  • To date
  • To epoch

How to use Unix Time Converter

  1. 01

    Confirm the source unit

    Choose seconds for JWT NumericDate claims, milliseconds for Date.now(), or the unit documented by your log producer. Smart detection is a hint, not a source contract.

  2. 02

    Choose the timezone context

    For an epoch value, the IANA timezone changes only the civil display. For a date without an offset, it determines how the local date resolves; review any DST ambiguity.

  3. 03

    Compare precision before copying

    Check UTC and the epoch ledger together. Numeric nanosecond input retains its remainder; ISO date input goes through Date.parse and has millisecond precision.

Frequently asked questions

Why does my timestamp land in 1970 or far in the future?
Seconds and milliseconds differ by 1,000. Confirm the producing API’s unit, choose it explicitly, and compare 1710000000 seconds with 1710000000000 milliseconds using the examples.
Does changing the timezone change the Unix timestamp?
An existing epoch instant stays the same. The timezone changes its civil display. A date without an offset needs timezone rules to identify an instant and may require a DST overlap or gap choice.
Are nanoseconds preserved when I paste an ISO date?
Numeric epoch input is carried as BigInt nanoseconds. ISO date input is parsed through the browser Date implementation at millisecond precision; adding more fractional digits to an ISO string does not preserve a nanosecond ledger.