Unix Timestamp Converter Online

Local processing

Convert Unix timestamps in seconds, milliseconds, microseconds, or nanoseconds and parse ISO 8601 dates. Inputs without an offset use UTC.

Multi-row timestamp converter

Compare timestamps and ISO 8601 dates. Inputs without an offset use UTC.

Row 1Timestamp -> Date
11/14/2023, 10:13:20 PM
ISO: 2023-11-14T22:13:20.000ZSeconds: 1700000000Milliseconds: 1700000000000

Unix time guide

How to convert Unix timestamps

Convert Unix time in seconds or milliseconds, plus common 16-digit microseconds and 19-digit nanoseconds, to a readable date, or turn an ISO 8601 date into a Unix timestamp. VetaTool keeps the original high-precision value visible while showing the millisecond-precision date locally in your browser. This tool is free to use. No account or payment is required.

Last updated

What you can do here

  • Unix seconds, milliseconds, microseconds, and nanoseconds conversion
  • ISO 8601 date parsing
  • Explicit UTC and timezone offset details
  • Multi-row timestamp comparison
  • Browser-local processing

How to use

  1. Choose Timestamp to Date or Date to Timestamp.
  2. Enter Unix time, an ISO 8601 date, or a supported calendar date.
  3. Review the local display, ISO value, seconds, milliseconds, and timezone details.
  4. Add rows to compare several timestamps, then copy the results you need.

Seconds versus milliseconds

Unix timestamps count elapsed time from 1970-01-01T00:00:00Z. Ten-digit values commonly represent seconds, while thirteen-digit values commonly represent milliseconds.

The converter recognizes common 16-digit microsecond and 19-digit nanosecond inputs before applying the existing seconds-versus-milliseconds magnitude heuristic. JavaScript dates have millisecond precision, so sub-millisecond digits are preserved in the original-value detail while the readable date is truncated to milliseconds.

Timezone handling is explicit

ISO 8601 values ending in Z use UTC, while values with an offset such as +09:00 preserve that offset during parsing. Calendar inputs without an offset are interpreted as UTC rather than silently using the browser timezone.

  • 2026-08-03T10:00:00Z explicitly uses UTC.
  • 2026-08-03T19:00:00+09:00 identifies a UTC+09:00 offset.
  • 2026-08-03 10:00:00 is treated as UTC because no offset is present.

Compare multiple dates and timestamps

Add multiple rows when you need to inspect log events, API expiry times, database values, or dates from different systems. Each row can use its own conversion direction and can be copied independently.

Unix timestamp conversion example

The Unix value 1700000000 represents seconds and converts to a stable UTC ISO date.

Timestamp input

1700000000

Converted output

ISO: 2023-11-14T22:13:20.000Z
Seconds: 1700000000
Milliseconds: 1700000000000

Common questions

Frequently asked questions

How does the converter detect timestamp units?

Common 16-digit integers are interpreted as microseconds and 19-digit integers as nanoseconds. Other numeric values keep the existing rule: absolute values of at least 100,000,000,000 are milliseconds and smaller values are seconds.

What timezone is used when a date has no offset?

Supported calendar and date-time inputs without an explicit offset are interpreted as UTC.

Can I convert dates before 1970?

Yes. Negative Unix timestamps are accepted when they produce a valid JavaScript date.

Are timestamps sent to a server?

No. Date parsing and timestamp conversion run locally in your browser.

Looking for broader references? Browse all developer guides.

Debugging a specific Timestamp issue? Browse Timestamp troubleshooting.