Seconds: - | Milliseconds: -
The copy button copies the current millisecond timestamp.
Current seconds and milliseconds, shown in the selected IANA timezone.
Both directions use the selected timezone. Changing the timezone refreshes the last valid conversion.
Offsets come from the browser Intl timezone data, including fractional-hour and historical second-level offsets.
Seconds accept up to 3 decimal places; milliseconds accept integers. Digit length is not used to guess the unit.
Selected-zone time, UTC, ISO 8601 with offset, date, exact seconds and integer milliseconds.
Conversion inputs stay in the browser. The page still loads analytics and libraries; no conversion backend is used.
The live clock shows the current timestamp in seconds and milliseconds. The copy button copies milliseconds.
Choose seconds or milliseconds, enter a timestamp in that unit, and submit. Seconds support up to 3 decimal places; the result uses the selected timezone.
Enter the wall-clock time in the selected timezone and a millisecond value from 000 to 999, then submit.
If a time occurs twice, choose the earlier or later instant. If a time is skipped by the clock, enter a time that exists.
| Timestamp | Date (UTC) | Significance |
|---|---|---|
| 0 | Jan 1, 1970 00:00:00 | Unix Epoch — the starting point |
| 946684800 | Jan 1, 2000 00:00:00 | Y2K / Millennium |
| 1000000000 | Sep 9, 2001 01:46:40 | First 10-digit timestamp |
| 1234567890 | Feb 13, 2009 23:31:30 | Sequential digits milestone |
| 1700000000 | Nov 14, 2023 22:13:20 | Recent major milestone |
| 2000000000 | May 18, 2033 03:33:20 | Next major milestone |
| 2147483647 | Jan 19, 2038 03:14:07 | Y2K38 — 32-bit overflow |
Convert Unix timestamps to human-readable dates and vice versa online free with FreeToolBox. Unix timestamps (also called epoch time or POSIX time) count the seconds elapsed since January 1, 1970 00:00:00 UTC and are the universal time representation in computing. Every programming language, database, log file, and API uses timestamps. Developers constantly need to convert them when debugging API responses, analyzing server logs, querying databases, or coordinating events across timezones.
This converter uses explicit seconds or milliseconds; it does not guess the unit from digit length. Seconds accept integers or up to three decimal places, so copied seconds such as -0.001 can be pasted back; milliseconds accept integers only. A single IANA timezone selector controls the live clock and both conversions. Results include selected-zone time, UTC, ISO 8601 with offset, exact seconds and integer milliseconds. Conversion inputs stay in the browser; the page still loads analytics and libraries.
Use Timestamp Converter when you need to translate epoch values into human-readable dates or back again. If your next step is validating or formatting a JSON payload containing those timestamps, pair it with JSON Formatter. If the timestamp is inside an encoded URL or query string, pair it with URL Encoder/Decoder.
No-upload workflow: logs, payloads, and schedule data stay in your browser while you convert and inspect time values.
Choose seconds or milliseconds explicitly. Seconds accept integers or 0–3 decimal places (for example -0.001 or 1735689600.123); milliseconds accept integers only. Trailing zeros do not change the value. Exponents, hex, separators and more than 3 decimal places are rejected.
Spring-forward gaps are rejected instead of silently changing the hour. Fall-back overlaps show the possible UTC instants and require an explicit choice. Offsets are derived from the browser Intl timezone data, not from a fixed hourly assumption.
Integer milliseconds are kept exactly within the JavaScript Date range, from -8640000000000000 to 8640000000000000. Seconds input and output support up to 3 decimal places and can be copied back without rounding. Years beyond 2038 are supported within that range; values outside it are rejected.
A Unix timestamp is the number of seconds that have elapsed since January 1, 1970, at UTC — the so-called epoch. It is a fixed, timezone-independent point in time, which makes it convenient for machines but opaque to humans. Because it is defined at UTC, a given timestamp does not have a time zone of its own; the same number refers to the same instant everywhere. When you convert it to a human-readable date, the time zone you apply changes the displayed local time but not the underlying instant.
Many systems store timestamps in milliseconds rather than seconds, and mixing the two is an extremely common bug. A value like 1,700,000,000 can be interpreted as a date in 2023 if it is seconds, or as a date in 1970 if it is mistakenly read as seconds when it was actually milliseconds. When a timestamp converts to a wildly wrong date, the first thing to check is the unit. Some libraries default to milliseconds and some to seconds, so know which one your source uses before you convert.
Because a timestamp is timezone-independent, the only place a time zone enters is when you format the date for a person. To convert properly, decide on the target time zone first, then apply it to the timestamp. Do not add or subtract hours to a timestamp to "adjust" it — the timestamp itself never changes; only its representation does. A reliable conversion gives you the UTC time as the ground truth and lets you choose the display zone separately, rather than baking a time zone into the stored number.