Skip to main content

Unix Timestamp Converter

Convert between Unix timestamps and human-readable dates. Supports seconds and milliseconds precision. ISO 8601 compliant output.

Unix time counts seconds since 1970-01-01 UTC. A value in the 13-digit range is milliseconds, not seconds — mixing the two is the single most common cause of a date decades in the future.

Tool workspace

Current Time

UTC:
—
Local Time:
—
ISO 8601:
—
Precision

Pick an IANA time zone to see the local time and the next DST change there.

No result yet

Enter your input above and the result will appear here.

Seconds

Seconds

Milliseconds

Milliseconds

Timezone

Timezone

Reference: a real run, the parameters, and the failure modes

Worked example

Convert 1700000000 in UTC

Input

Timestamp: 1700000000
Precision: auto (10 digits -> seconds)
Time zone: UTC

Output

2023-11-14T22:13:20.000Z
Tue, 14 Nov 2023 22:13:20 GMT

How to verify: Run `date -u -r 1700000000` on macOS or `date -u -d @1700000000` on GNU; both print the same instant (Tue Nov 14 22:13:20 UTC 2023 on an English locale). The page keeps Unix seconds and milliseconds as separate outputs.

Parameters

Parameters
ParameterValueDefaultBound
InputInteger seconds, milliseconds or ISO 8601AutoDigits 10 or fewer: seconds; 11 or more: milliseconds
Precisionauto, seconds or millisecondsAuto11-12 digits are flagged as ambiguous
Range0 to 8.64e15 milliseconds—Negative values and values above 2^53-1 are rejected
Time zoneLocal, UTC and 8 IANA zonesLocalDST gaps are reported, not shifted
OutputISO 8601, UTC and local text, relative time, Unix seconds and milliseconds—Seconds and milliseconds stay separate
BatchOne value per lineOffInvalid lines are reported individually

Failure checklist

Failure checklist
SymptomLikely causeWhat to do
An 11-digit value lands in 2286.11-12 digits are read as milliseconds and marked ambiguous.Choose seconds explicitly if the value is seconds.
A value is rejected as out of range.It exceeds the ECMAScript Date range of 8.64e15 ms.Check the unit; a 16-digit value is usually microseconds or nanoseconds.
A negative timestamp is rejected.The parser accepts zero or positive integers only.Convert the signed value outside the page or use the ISO input.
A local time in the DST gap is wrong.The selected zone skips that clock time.Pick a time outside the gap; the page reports it instead of shifting.
The result differs from the server.The server uses another time zone or unit.Set the zone explicitly and compare Unix seconds, not formatted text.
How to Convert Unix Timestamps Online

Learn how to convert between Unix timestamps and human-readable dates using a client-side tool.

  1. 1

    Enter timestamp or date

    Input a Unix timestamp or select a date and time.

  2. 2

    Select precision

    Choose between seconds or milliseconds precision.

  3. 3

    Click Convert

    The tool converts between formats instantly in your browser.

  4. 4

    View all formats

    See the result in UTC, local time, ISO 8601, and relative time formats.

Common Use Cases
  • 1Convert Unix timestamps from logs and API responses to readable dates
  • 2Generate the current epoch value for API tests and cron jobs
  • 3Debug timezone problems by comparing UTC and local representations
  • 4Compute expiry times for tokens, caches, and signed URLs

Frequently Asked Questions

Which precisions are supported?

Seconds and milliseconds, plus ISO 8601 strings and local or UTC representations.

Does it work offline?

Yes. All conversions happen in your browser.

Can I convert in both directions?

Yes. Convert a Unix timestamp to a date and a date back to a timestamp, with relative time display.

How are time zones and daylight saving handled?

Conversions use the IANA time zone you select, including daylight-saving transitions. A local time that does not exist during a spring-forward gap is reported instead of being shifted silently.

Which timestamp range is accepted?

Values must be integers within JavaScript's exact integer range. Negative values and values beyond 2^53 are rejected with an explicit message, which avoids rounding a timestamp into a different instant.

Related Guides

Related Tools

Your inputs remain on your device.

You are responsible for key management and output validation.