Understand the number
A Unix timestamp is one moment, shown without a timezone
Unix time counts elapsed units from 00:00:00 UTC on January 1, 1970. The number itself does not belong to Bangkok, London, or New York. A timezone matters only when that moment is formatted for a person to read. This is why one timestamp can produce different-looking local times without representing different moments.
How to convert a timestamp
- 1
Paste the number
Enter a numeric epoch value. A negative value can represent a date before 1970.
- 2
Check the detected unit
The badge reports seconds, milliseconds, microseconds, or nanoseconds.
- 3
Choose an output
Copy ISO for systems, UTC for a neutral reference, or local time for your screen.
Seconds or milliseconds? Count the scale, not just the digits
APIs and databases do not all store Unix time at the same precision. These four values point to the same example moment: 2025-07-02T08:01:26Z.
| Unit | Example value | Where it often appears |
|---|---|---|
| Seconds | 1751443286 | Unix commands, many backend APIs |
| Milliseconds | 1751443286000 | JavaScript dates, browser applications |
| Microseconds | 1751443286000000 | Logs and higher-resolution databases |
| Nanoseconds | 1751443286000000000 | Tracing and high-resolution system clocks |
What each result is useful for
ISO 8601
2025-07-02T08:01:26.000ZA compact, sortable format for APIs, logs, databases, and bug reports. The ending Z means UTC.
UTC string
Wed, 02 Jul 2025 08:01:26 GMTA human-readable neutral reference that is helpful when people are working across timezones.
Local time
Shown in your device timezoneThe same moment adjusted for the timezone configured in your browser or operating system.
Relative time
2 hours agoA quick sense of recency. It changes as the current time moves, so do not store it as a permanent date.
Why local time may surprise you
Local time uses the timezone and daylight-saving rules available to your device. Two colleagues can convert the same value and see different clock times. Compare their ISO or UTC results to confirm whether the underlying moment is identical.
A note about very precise values
Browser numbers cannot preserve every final digit of very large microsecond or nanosecond timestamps. This converter is suitable for finding the corresponding date and time, but it should not be used for lossless nanosecond arithmetic or ordering events that differ only in their smallest digits.
Common conversion checks
- A date near 1970: the source may be seconds that were mistakenly treated as milliseconds.
- A far-future date: the source may be milliseconds that were mistakenly treated as seconds.
- An invalid result: confirm the input contains only a valid number and represents a date supported by the browser.
- A timezone disagreement: compare ISO or UTC output before changing the original timestamp.
Up to ten recent conversions are stored in this browser for convenient reuse. The timestamp you enter and its history are not uploaded to JustUtils.