How it works
A Unix timestamp counts the seconds since 1 January 1970, 00:00:00 UTC. Paste one to see the date and time in any time zone, in UTC and in ISO 8601 format, plus how long ago or how far ahead it is. Switch direction to turn a local date and time back into a timestamp; daylight saving time is handled for the zone you pick.
1767225600 = 2026-01-01 00:00:00 UTC = 2026-01-01 09:00 in Seoul
Seconds, milliseconds or microseconds?
- 10 digits: seconds — Unix, PHP, Python time.time() and most APIs.
- 13 digits: milliseconds — JavaScript Date.now() and Java.
- 16 digits: microseconds — some databases and logs.
Tips
- Timestamps have no time zone; the zone only changes how the moment is displayed.
- Negative values are dates before 1970.
- The time zone list comes from your browser's up-to-date time zone database.
Standards and sources
- Unix time as defined in POSIX (IEEE Std 1003.1)
- Date format ISO 8601; time zones from the IANA Time Zone Database
Last reviewed October 7, 2026
Frequently asked questions
What is a Unix timestamp?
The number of seconds since 00:00:00 UTC on 1 January 1970, also called epoch time. It is the same everywhere in the world.
How do I know if a timestamp is in seconds or milliseconds?
Current timestamps in seconds have 10 digits and in milliseconds 13 digits. The converter detects this automatically.
Does it handle daylight saving time?
Yes. Conversions use the IANA time zone database built into your browser, including daylight saving changes.
What is the year 2038 problem?
Systems that store seconds as a signed 32-bit number overflow on 19 January 2038. This converter uses 64-bit numbers and is not affected.
Can I get the current timestamp?
Yes. Tap "Now" to fill in the current time.