Unix Timestamp Converter
Convert a Unix timestamp to a human-readable date, or a date and time back to a timestamp — instantly, in your browser.
Date
10/17/2026, 4:48:48 PM
UTC: Sat, 17 Oct 2026 16:48:48 GMT · ISO: 2026-10-17T16:48:48.000Z
- Free — No signup required
- Instant — Results update as you type
- Private — Processed in your browser
Unix time counts seconds since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. It is the format of most log lines, token expiry claims, database columns and API fields, and it is unreadable without conversion. This tool goes from a timestamp to a date and back, showing the result in your local zone, in UTC and in ISO 8601 at the same time.
How it works
In Timestamp → Date mode, enter a number and pick whether it is in seconds or milliseconds. The tool multiplies seconds by 1,000, builds a JavaScript Date, and prints three renderings: your browser's local date and time, the same instant in UTC, and the ISO 8601 string ending in Z. Copy puts the ISO form on the clipboard, since that is the one other systems parse unambiguously. Use now fills in the current time in the selected unit.
In Date → Timestamp mode, pick a date and time with the browser's picker. The value is interpreted in your local time zone, converted to milliseconds since the epoch, and shown both as whole seconds (rounded down) and as milliseconds.
Everything runs locally. The local rendering depends on your device's time zone and locale settings, so two people converting the same number can see different wall-clock times; the UTC and ISO lines are the same for everyone.
Seconds, milliseconds and beyond
A ten-digit number is seconds and a thirteen-digit number is milliseconds for any date in the current era. If the converted date lands in 1970 or in the far future, you almost certainly picked the wrong unit. Java's System.currentTimeMillis(), JavaScript's Date.now() and most JSON APIs use milliseconds; POSIX tools, JWT claims and many databases use seconds.
Sixteen-digit values are microseconds and nineteen-digit values are nanoseconds, which some tracing and metrics systems emit. The tool does not offer those units; divide by 1,000 or 1,000,000 first. Fractional seconds are accepted in the input and appear in the ISO output down to the millisecond, which is the precision of a JavaScript Date.
Negative timestamps are valid and denote dates before 1970. The representable range is about ±273,000 years around the epoch, which is wider than any real data.
Time zones and daylight saving
A Unix timestamp has no time zone; it identifies an instant. The zone only matters when you turn that instant into a calendar date, which is why the tool shows local and UTC side by side. When a log entry seems an hour off, the usual cause is that the writer stamped local time and the reader assumed UTC, or a daylight-saving change fell between the two.
The date-to-timestamp direction is where ambiguity creeps in. During the hour that repeats when clocks go back, a local wall-clock time corresponds to two instants, and the browser picks one. If precision at that level matters, work in UTC and convert with a proper library rather than a date picker.
Command-line equivalent
GNU date converts in both directions:
date -u -d @1700000000 # Tue Nov 14 22:13:20 UTC 2023
date +%s # current Unix time in seconds
date -d '2024-03-01T09:00:00Z' +%s # ISO string to seconds
On macOS the syntax is date -r 1700000000 for the first form.
The year 2038
Systems that store Unix time in a signed 32-bit integer overflow at 03:14:07 UTC on 19 January 2038. Modern operating systems and languages use 64 bits, but embedded devices, old file formats and some database schemas do not. If you are designing storage today, use a 64-bit integer or a proper timestamp type.
Learn more
Java's java.time package models this distinction directly: Instant is the timestamp, ZonedDateTime is the instant plus a zone, and LocalDateTime is a wall-clock time with no zone at all. The guide to Optional and the java.time API explains which to use where and how to convert between them safely. The exp and iat claims you see in the JWT decoder are Unix seconds, and the age calculator handles the calendar arithmetic once you have a date.
FAQ
- What is a Unix timestamp?
- A Unix timestamp is the number of seconds (or milliseconds) that have elapsed since January 1, 1970, 00:00:00 UTC — also called the Unix epoch.
- How do I know if my timestamp is in seconds or milliseconds?
- Seconds-based timestamps for recent dates are typically 10 digits long; millisecond-based timestamps are 13 digits. Switch the unit selector if the resulting date looks wrong.
- Is my data sent to a server?
- No. All conversion happens locally in your browser.