Skip to main content
coltool
中文

Unix Timestamp Converter

Convert Unix timestamps to human-readable dates and back, with seconds/milliseconds and time zone support.

Current timestamp

1785405892seconds

Timestamp → Date & time

Date & time → Timestamp

What does this tool do?

Digging through logs, calling APIs or writing SQL, you constantly hit numbers like 1780000000 and need to know the moment they represent — or you need the reverse, turning a date into a timestamp for a request parameter. This page does three things:shows the current timestamp live (switchable between seconds and milliseconds, one click to copy),converts timestamps to dates, andconverts dates to timestamps. Both converters support the full IANA time zone list and default to your browser’s local zone — switch to the server’s zone when reading remote logs.

How to use

  1. Paste a timestamp, pick the unit (10 digits → seconds, 13 → milliseconds), click Convert;
  2. Click “Use current time” to immediately get both the readable date and ISO 8601 output with its time-zone offset;
  3. Or type or paste a date and time in YYYY-MM-DD HH:mm:ss format (optionally with .SSS milliseconds), choose a time zone, and get both timestamp units;
  4. Click any result field to copy it.

FAQ

What is a Unix timestamp?
A Unix timestamp is the amount of time elapsed since January 1, 1970 00:00:00 UTC — 10 digits for seconds, 13 for milliseconds. It is time-zone independent: the same instant has the same timestamp everywhere on Earth.
How do I tell seconds from milliseconds?
Count the digits: a present-day timestamp in seconds has 10 digits (e.g. 1780000000), in milliseconds 13 digits (e.g. 1780000000000). If your result lands near 1970 or far in the future, the unit is probably wrong.
Why does the same timestamp show different dates in different time zones?
A timestamp is an absolute instant with no time zone attached; rendering it as a calendar date requires choosing one. This tool defaults to your browser’s time zone, and you can search for any IANA time zone in the time zone field.
Does the Year 2038 problem affect this tool?
No. The 2038 problem only affects systems storing seconds in a signed 32-bit integer. JavaScript represents time as a double-precision float, which safely covers dates hundreds of thousands of years out.