Unix Timestamp Converter
Convert Unix timestamps to dates and back.
Was this tool helpful?
Thanks for the feedback!
A Unix timestamp counts the seconds since 00:00:00 UTC on 1 January 1970. Paste one into this Unix timestamp converter to see the date and time it stands for, or type a date to get its timestamp; leave the box empty and click Convert to get the current value.
Three things you can enter
- Nothing. The result shows "Now:" with the current Unix time in seconds and the current UTC date.
- A number of 9 to 13 digits. Exactly 13 digits are read as milliseconds, the format JavaScript's
Date.now()and many APIs use; 9 to 12 digits are read as seconds. You get three lines: the UTC date, your local date and time in your browser's time zone and date format, and the ISO 8601 form ending in Z. - A date. Anything the browser's date parser understands, such as
2026-06-11or2026-06-11T10:30:00+05:30. The result gives the Unix time in whole seconds plus the ISO 8601 form in UTC.
Worked example
1750000000 converts to:
Sun, 15 Jun 2025 15:06:40 GMT Local: 15/6/2025, 8:36:40 pm ISO: 2025-06-15T15:06:40.000Z
The local line is what a browser set to Indian English shows in India Standard Time, which runs 5 hours 30 minutes ahead of UTC. Pasting 1750000000000, the same moment in milliseconds, gives an identical result.
How dates without a time zone are read
This is where most conversion mistakes happen, because the browser follows the ECMAScript parsing rules:
| You type | Read as | Unix result |
|---|---|---|
| 2026-06-11 | Midnight UTC | 1781136000 |
| 2026-06-11 10:30 | 10:30 local time | 1781154000 (in IST) |
| 2026-06-11T10:30:00Z | 10:30 UTC | 1781173800 |
Slash dates are the other trap: 11/06/2026 is read the American way, as 6 November rather than 11 June. Stick to year-month-day order, and add an offset such as +05:30 or Z whenever the time zone matters.
Seconds, milliseconds and the 2038 limit
Ten-digit second values cover September 2001 to November 2286, which is why most timestamps you meet today have ten digits. If a date lands in 1970 or thousands of years ahead, seconds and milliseconds have probably been mixed up. Systems that store the value as a signed 32-bit integer run out at 2147483647, shown here as Tue, 19 Jan 2038 03:14:07 GMT; that is the "Year 2038 problem". Unix time also ignores leap seconds, so every day counts as exactly 86,400 seconds.
Limits
Numbers shorter than nine digits (moments before 3 March 1973) and negative values are not treated as timestamps, so they give an error or a meaningless date. When you convert a date, the seconds are rounded down and any milliseconds are dropped. For the gap between two dates, use the Date Difference Calculator.