Current Time

Unix Timestamp (Seconds)

ISO 8601

Converter

Unix Timestamp

↔

Local Date

ISO / UTC

Relative

Date → Timestamp

Real input and output

Seconds since epoch

Input

1767225600

Output

2026-01-01 00:00:00 UTC

A millisecond value

Input

1767225600000

Output

2026-01-01 00:00:00 UTC

Ten digits means seconds, thirteen means milliseconds. Check the digit count first.

Errors you will hit

The date comes out as 1970

A millisecond value was read as seconds, or the reverse. The factor of 1000 puts milliseconds-as-seconds tens of thousands of years out, and seconds-as-milliseconds back in early 1970.

The result is off by a fixed number of hours

Epoch values are always UTC. Display applies your local timezone. When comparing logs, confirm which basis each side recorded.

The year 2038 problem

Storing seconds in a signed 32-bit integer overflows on 19 January 2038. When touching legacy systems or database column types, confirm the field is 64-bit.

Tools that pair well

Why timestamp conversion shows up so often

Check JWT expiry values

Turn iat, exp, and nbf numbers into readable dates when debugging auth flows.

Interpret logs faster

Compare epoch values against both local time and UTC so incident timelines line up with alerts, dashboards, and user reports.

Review schedules safely

Move between seconds and milliseconds when checking campaigns, scheduled jobs, or delayed message sends.

Practical questions teams ask a lot

How do I tell seconds from milliseconds?

Ten digits usually means seconds and thirteen usually means milliseconds, but the safest check is always the source system documentation.

Why keep both local time and UTC?

Local time is easier for people, while UTC is the safer reference for systems, logs, and cross-region debugging.

Does the page send date values anywhere?

The conversion runs in the browser. You should still account for your own device, extensions, and operational security policies.