Current Unix time
1784184539
Thu, 16 Jul 2026 06:48:59 GMT
Unix timestamp → date
UTCThu, 16 Jul 2026 06:48:59 GMT
LocalThu Jul 16 2026 06:48:59 GMT+0000 (Coordinated Universal Time)
ISO 86012026-07-16T06:48:59.000Z
Date → Unix timestamp
Seconds1784184539
Milliseconds1784184539000
How to use
01
Grab the current time
The top card shows live Unix time ticking every second. Copy it in seconds or milliseconds depending on what your API or database column expects.
02
Convert a timestamp to a date
Paste epoch seconds into the Unix timestamp field. You instantly get the UTC string, your local time, and the ISO 8601 form, each with its own copy button.
03
Convert a date to a timestamp
Type an ISO date such as 2026-05-26T12:00:00 into the date field and read off the equivalent value in both seconds and milliseconds.
Why Unix Timestamp Converter
- Two-way conversion in real time.
- Live current time in seconds and milliseconds.
- Detects local timezone for display, keeps stored values in UTC.
Common questions
How do I tell seconds from milliseconds in a timestamp?
Count digits. Current-era epoch values have 10 digits in seconds and 13 in milliseconds. If a conversion lands you in the year 56,000 or so, you fed milliseconds into a seconds field.
Why does a timestamp to date online result differ from my log?
Your log almost certainly printed local time while the epoch value is timezone-free. Compare against the UTC row first, then apply your zone's offset, and the gap should equal that offset exactly.
What date does epoch 0 convert to?
1970-01-01T00:00:00Z, the starting point of Unix time. Every epoch value is just the count of seconds before or after that instant.
Does the epoch to human date conversion respect my timezone?
You get both: a UTC row that's the same for everyone and a Local row rendered in your browser's configured timezone. Comparing the two is a quick way to confirm your machine's offset.
Can I convert dates from before 1970?
Yes. Moments before the epoch are simply negative second counts, and JavaScript's Date type handles them, so a value like -86400 resolves to the last day of 1969.
Is Unix time affected by leap seconds?
No. Unix time pretends every day has exactly 86,400 seconds, which keeps the math simple. The tradeoff is that epoch arithmetic can drift a second from atomic time, which almost no application cares about.
Which timezone do the converted local values use?
Whatever your operating system and browser report. Change your system timezone and reload, and the Local row shifts accordingly while UTC and the epoch value stay fixed.