How to use the unix timestamp converter

1The Current Unix time panel shows the live time in seconds and milliseconds; press Copy seconds or Pause clock.
2Choose your Time zone (it starts with the one your browser reports).
3Under Timestamp → date, type a timestamp or press Now. Unit detects seconds, ms, µs or ns from the digit count; pick one to override. Copy any line of the result.
4Under Date → timestamp, pick a Date and Time (or press Use current date and time) to get seconds and milliseconds for that moment in the chosen zone.
5Use Time between two timestamps for durations, and Batch convert for a list, one value per line.

Example

Input

1700000000

Output

UTC: 2023-11-14T22:13:20Z
Asia/Kolkata: 2023-11-15T03:43:20+05:30
America/New_York: 2023-11-14T17:13:20-05:00

10 digits, so read as seconds. 1700000000000 (13 digits) is read as milliseconds and gives the same moment.

Current Unix time

Unix time counts the seconds since 1 January 1970, 00:00:00 UTC (the "epoch"), ignoring leap seconds. It is the same number everywhere on Earth at a given moment, which is why databases, APIs and log files use it: there is no time zone or daylight saving to get wrong. The live clock shows it from your device's clock, so if your computer's time is off, so is the clock. 1,700,000,000 was reached on 14 November 2023 at 22:13:20 UTC; 2,000,000,000 arrives on 18 May 2033.

Timestamp to date

Paste any timestamp and you get it in UTC as ISO 8601, in your chosen zone with its offset, as readable text, as an HTTP date (RFC 7231, used in Last-Modified headers), and relative to now ("2 years ago"). Negative timestamps are dates before 1970: -86400 is 31 December 1969.

Underscores, commas and spaces are ignored, so 1_700_000_000 works. Fractions such as 1700000000.5 are accepted and kept to the millisecond.

Date to timestamp

Pick a date and a time on the 24-hour clock. It is read as wall-clock time in the selected zone, so 09:00 in Asia/Kolkata and 09:00 in Europe/London give different timestamps. The panel shows the zone's UTC offset on that date.

Daylight-saving changes are handled the way most libraries do: a time that doesn't exist (clocks jump from 02:00 to 03:00) moves forward to the next valid time, and a time that happens twice when clocks go back uses the first occurrence. A note appears in both cases.

Seconds, milliseconds and microseconds

Digits (today)	Unit	Typical source
10	seconds	Unix/Linux `date +%s`, PHP `time()`, most APIs, JWT `exp`
13	milliseconds	JavaScript `Date.now()`, Java `System.currentTimeMillis()`
16	microseconds	Python `time.time_ns() // 1000`, PostgreSQL internals
19	nanoseconds	Go `UnixNano()`, Python `time.time_ns()`

The detector uses these digit counts, which hold for dates between 1973 and 5138. If a timestamp shows a date in 1970 or the year 55,000, it was read with the wrong unit: choose the unit yourself.

Time zones and daylight saving

The zone list is the IANA time zone database built into your browser (Asia/Kolkata, America/New_York, Europe/London), which includes every historical daylight-saving rule. Prefer these names to abbreviations: "IST" means India, Ireland or Israel depending on who you ask, and "EST" doesn't change in summer while New York does.

In Batch convert, dates without an offset, such as 2026-10-05 12:00, are read in your browser's own time zone. Add Z or an offset (2026-10-05T12:00:00+05:30) to be exact.

Code snippets

Language	Current timestamp	Timestamp → date
JavaScript	`Math.floor(Date.now() / 1000)`	`new Date(1700000000 * 1000).toISOString()`
Python	`int(time.time())`	`datetime.fromtimestamp(1700000000, tz=timezone.utc)`
PHP	`time()`	`date('c', 1700000000)`
MySQL	`UNIX_TIMESTAMP()`	`FROM_UNIXTIME(1700000000)`
PostgreSQL	`extract(epoch from now())`	`to_timestamp(1700000000)`
Bash (GNU)	`date +%s`	`date -u -d @1700000000`

JavaScript works in milliseconds, hence the * 1000 and / 1000. Forgetting them is the most common timestamp bug.

Is anything I enter stored?

This tool runs entirely in your browser. Your text is not uploaded to our servers.

Sources

Questions about the unix timestamp converter

What is a Unix timestamp?

The number of seconds since 1 January 1970 00:00:00 UTC, not counting leap seconds. It identifies a moment independently of time zones.

How do I tell if a timestamp is in milliseconds?

Count the digits: for current dates, 10 digits are seconds and 13 are milliseconds. The converter detects this automatically and shows how it read the number.

What happens in 2038?

Systems that store Unix time as a signed 32-bit integer overflow after 2147483647, which is 19 January 2038 at 03:14:07 UTC, and jump back to 1901. 64-bit timestamps, used by modern systems and this tool, last for billions of years.

Unix Timestamp Converter