Unix Timestamp Converter
Turn a Unix timestamp into a readable date in UTC and in any time zone, or turn a date and time into a timestamp. The unit is explicit: choose seconds, milliseconds, microseconds or nanoseconds, or let the tool guess from the size of the number and tell you what it guessed. Everything runs in your browser.
Result
Timestamp to date
- ISO 8601 (UTC)
- UTC date and time
- In the chosen time zone
- UTC offset there
- Compared with now
- Day of the week (UTC)
- Day of the year (UTC)
- Leap year (UTC)
- Unit used
Date to timestamp
- ISO 8601 (UTC)
- Seconds
- Milliseconds
- Microseconds
- Nanoseconds
Examples
Reference values you can check against any other tool:
| Seconds | Date and time (UTC) | What it is |
|---|---|---|
0 | 1970-01-01T00:00:00Z | The Unix epoch |
1000000000 | 2001-09-09T01:46:40Z | One billion seconds |
1700000000 | 2023-11-14T22:13:20Z | A recent moment |
2147483647 | 2038-01-19T03:14:07Z | The largest 32-bit signed value (the โyear 2038โ limit) |
Formula & Methodology
A Unix timestamp counts the time elapsed since 1 January 1970 at 00:00:00 UTC (the Unix epoch), ignoring leap seconds. Seconds, milliseconds, microseconds and nanoseconds differ only by a factor of 1,000. The numbers are handled as exact decimals, so nanosecond values are not rounded.
epoch = 1970-01-01T00:00:00Z1 s = 1,000 ms = 1,000,000 ยตs = 1,000,000,000 nsLocal times use the time-zone database built into your browser, which also decides daylight saving time. A local wall-clock time that is skipped or repeated by a clock change is resolved as described in the notes.
Notes and limitations
- Automatic detection is a guess from the size of the number: below 100,000,000,000 it is read as seconds, then milliseconds, microseconds and nanoseconds. Pick the unit yourself if the result looks wrong.
- Unix time ignores leap seconds, so it is not the same as the physical time that elapsed.
- Dates are limited to what a browser can represent (about ยฑ275,760 years from 1970).
- Time-zone results depend on your browserโs IANA database; very old or far-future dates may use simplified rules.
- Only the ISO 8601 style of date input is accepted, because other spellings are ambiguous (is 03/04 March or April?).
How to Use
- To convert a timestamp, paste it in the first box and leave the unit on automatic, or choose the unit.
- Choose the time zone you want local times in. UTC is always shown.
- To convert a date, type it in ISO 8601 form in the second box, or use the current time.
- Read the results: ISO date, local time, relative time and the value in every unit.
- Copy the value you need.
Frequently Asked Questions
What is a Unix timestamp?
It is the number of seconds (or milliseconds, and so on) since 1 January 1970 at 00:00:00 UTC. Because it is a single number that does not depend on a time zone, programs use it to store and compare moments in time.
How do I know whether my timestamp is in seconds or milliseconds?
Todayโs timestamps have 10 digits in seconds (for example 1700000000) and 13 digits in milliseconds (1700000000000). Automatic detection uses this size, and tells you which unit it chose. You can always choose the unit yourself.
Why does the local time differ from UTC?
A timestamp is one moment; each time zone shows it with its own offset from UTC, including daylight saving time where it applies. Choose the zone you need in the time-zone box.
What happens with a time that does not exist or happens twice?
When clocks jump forward, some wall-clock times never occur; the tool moves them forward by the length of the jump. When clocks go back, some times occur twice; the tool uses the first one. A note tells you when this happens.
Is my data sent anywhere?
No. All conversions run in your browser and nothing you enter is uploaded or sent to analytics.
Last updated: