Unix time zero
0 seconds is 1970-01-01 00:00:00 UTC and 1970-01-01 09:00:00 KST.
Unix timestamp · date conversion
Convert 10-digit seconds, 13-digit milliseconds, microseconds or nanoseconds into readable dates. Compare the same instant in UTC, Korea Standard Time, your device time zone and a selected city.
Digit length is a useful clue near present-day dates, but the documented source unit always takes priority for historical or far-future values.
| Digit guide | Likely unit | Example | What to verify |
|---|---|---|---|
| 1–10 digits | Seconds | 1704067200 | Present-day seconds are usually 10 digits |
| 11–13 digits | Milliseconds | 1704067200000 | Usually 1,000 times the seconds value |
| 14–16 digits | Microseconds | 1704067200000000 | 1,000 times finer than milliseconds |
| 17+ digits | Nanoseconds | 1704067200000000000 | Keep the value as an integer string |
Use boundary values to confirm both the selected unit and the converter output.
0 seconds is 1970-01-01 00:00:00 UTC and 1970-01-01 09:00:00 KST.
946684800 seconds is 2000-01-01 00:00:00 UTC, a convenient test value.
2147483647 seconds is 2038-01-19 03:14:07 UTC. The next second exceeds signed 32-bit storage.
A timestamp identifies one instant regardless of region. Choosing a time zone changes the calendar and clock used to display that instant, not the underlying Unix value.
The global reference used to compare records from different regions.
KST is UTC+09:00 all year and currently has no daylight-saving changes.
New York, London and Sydney follow date-specific regional rules, including seasonal changes.
Display range: extremely large values cannot be represented as ordinary calendar dates. If you see a range error, check whether seconds were interpreted as milliseconds or vice versa.
Regional rules follow the IANA Time Zone Database. The calendar display limit is described in MDN's Date documentation.
Four checks to make when a converted date is not what you expected.
The most common cause is a seconds-versus-milliseconds mismatch. Check whether a 13-digit millisecond value was read as seconds or a 10-digit seconds value was read as milliseconds.
Yes. Seconds can contain up to nine fractional digits, milliseconds up to six and microseconds up to three. Nanoseconds must be entered as an integer.
A negative value represents an instant before 1970-01-01 00:00:00 UTC. For example, -1 second is 1969-12-31 23:59:59 UTC.
Korea Standard Time is nine hours ahead of UTC. A late-afternoon UTC instant can already be the next calendar day in Korea.
Create a timestamp from a date, process many values or validate a date string.
Calculate seconds and milliseconds from a calendar date.
Convert a date →Many valuesTurn multiple numbers into a UTC and KST table.
Convert a batch →String validationCheck the syntax and time-zone offset of a date string.
Validate a format →