What is the current Unix timestamp?
The live number above counts elapsed seconds since 1970-01-01 00:00:00 UTC, the Unix epoch. It is independent of a display time zone: one timestamp identifies the same instant everywhere. A time zone matters only when that instant is formatted as a calendar date and clock time.
Browsers expose the device clock in milliseconds. The microsecond and nanosecond rows therefore preserve convenient unit scales, but their extra trailing digits are derived rather than measurements of sub-millisecond precision.
Choose the correct timestamp unit
Contemporary epoch values often have 10 digits in seconds, 13 in milliseconds, 16 in microseconds, or 19 in nanoseconds. That is a useful hint rather than a universal rule: old dates, negative values and far-future dates can have different lengths. The converter shows its choice and lets you override it.
Private, browser-local conversion
Current values, pasted timestamps and local files stay in this browser. The site does not need an account or database to perform these calculations.
How to use this tool
Use the live seconds value for a system that expects Unix seconds. For milliseconds, copy the separately labelled row. The quick converter accepts an existing timestamp; dedicated pages handle date input, CSV lists and two-region clock conversions.
Worked input and output
| Input or setting | Expected result |
|---|---|
1700000000 · s | 2023-11-14T22:13:20Z |
1700000000000 · ms | 2023-11-14T22:13:20Z |
0 · s | 1970-01-01T00:00:00Z |
Checks before using the result
The device supplies the current clock. Changing the display zone does not change the instant, and adding zeros does not add measured precision. Keep the source unit documented. Start with what Unix time means or seconds versus milliseconds when interpreting an unfamiliar value.