How to use Unix timestamp converter
- 1
See the current Unix time at the top, in seconds and milliseconds. Copy it with one click.
- 2
Paste a timestamp. Its unit (seconds, milliseconds, microseconds or nanoseconds) is detected from its size, or choose it yourself.
- 3
Read the date in UTC, in your own time zone and in any other time zone you pick, plus ISO 8601, RFC 2822 and relative time.
- 4
To go the other way, enter a date and time, choose the time zone it belongs to, and copy the timestamp.
What this tool does
The converter translates between Unix epoch time and human-readable dates. Use it to read timestamps in logs, API responses, JWT exp and iat claims or database rows, or to create a timestamp for a specific moment in a specific time zone.
Features
- Live current time in seconds and milliseconds.
- Auto-detects the unit, from seconds to nanoseconds, and accepts negative values (dates before 1970) and decimal seconds.
- Many formats at once. Readable date in UTC, your zone and a chosen zone, ISO 8601 with offset, RFC 2822 and "3 hours ago" style relative time.
- Every IANA time zone your browser knows, such as Asia/Karachi, Europe/London or America/New_York, with daylight saving handled.
- Date to timestamp with warnings for skipped and repeated times.
Limits
- Dates are precise to the millisecond. Microsecond and nanosecond digits are shown separately but not included in the date.
- Time zone rules come from your browser's built-in data, so very recent rule changes may be missing in an old browser.
- Unix time ignores leap seconds, as nearly all computer clocks do.
Where your text is processed
This tool works in your browser: what you type or paste is processed on your own device, so it isn't sent to our server for this tool. Some other tools on UtiloNest do use our server, and their pages say so.
Frequently asked questions
What is a Unix timestamp?
It is the number of seconds since 00:00:00 UTC on 1 January 1970, called the Unix epoch, not counting leap seconds. Because it doesn't depend on time zones, it is how most databases, APIs, logs and programming languages store moments in time. JavaScript and Java often use milliseconds instead of seconds.
How does automatic unit detection work?
It looks at the size of the number. Values below 100 billion are read as seconds (this covers dates up to the year 5138). Larger values are read as milliseconds, then microseconds, then nanoseconds, matching the usual 10-, 13-, 16- and 19-digit lengths. If your number is ambiguous, choose the unit from the list.
Why does the same timestamp show different times?
A timestamp is one instant, but the clock time depends on where you are. 1700000000 is 22:13:20 on 14 November 2023 in UTC, but already 03:13:20 on 15 November in Pakistan (UTC+5). Daylight saving time is applied automatically for each zone and date.
What happens with times skipped or repeated by daylight saving?
When clocks spring forward, some times never happen, and when they fall back, some happen twice. The converter warns you in both cases. It uses the time just after the jump for a skipped time, and the first occurrence for a repeated one.
What is the year 2038 problem?
Older systems store Unix time as a signed 32-bit number, which runs out at 03:14:07 UTC on 19 January 2038 (timestamp 2147483647). This converter uses JavaScript dates, which reach about 275,000 years either side of 1970, so it handles 2038 and beyond.