Unix Timestamp Converter
Convert between Unix timestamps and human-readable dates, in either direction. Runs entirely in your browser.
Current Unix timestamp: 1793685192
Tue, 03 Nov 2026 05:53:12 GMT
1793685192
How it works
The first field turns a Unix timestamp — seconds since 1 January 1970 00:00:00 UTC — into a readable date, always shown in UTC. The second field turns a date and time in your own time zone into a timestamp in whole seconds. A live counter shows the current timestamp.
Example
1700000000 is Tuesday 14 November 2023, 22:13:20 UTC, and 0 is 1 January 1970 00:00:00 UTC. Negative timestamps work and give dates before 1970.
Edge cases
A value with 16 digits is probably in microseconds, but any number of 13 or more digits is read as milliseconds, so it will show a date thousands of years ahead — divide it by 1,000 first. Because the date-to-timestamp side uses your browser's local time zone while the timestamp-to-date side uses UTC, the same wall-clock time gives different timestamps in different zones. Fractions of a second are dropped.
More reference points
1000000000 is Sunday 9 September 2001, 01:46:40 UTC. 1735689600 is exactly 1 January 2025, 00:00:00 UTC. 2147483647, the largest value a signed 32-bit integer can hold, is Tuesday 19 January 2038, 03:14:07 UTC. Each day always counts as exactly 86,400 seconds, because Unix time ignores leap seconds.
Where you will meet timestamps
- Token claims such as exp and iat in a JWT, which are in seconds.
- JavaScript's Date.now() and Java's currentTimeMillis(), which are in milliseconds.
- Database columns, server logs, API responses and file metadata, where the unit has to be checked against the documentation.
The year 2038 problem
Systems that store the timestamp in a signed 32-bit integer overflow after 19 January 2038 and wrap to a date in 1901. Modern software uses 64-bit values, which are good for billions of years, but old embedded devices, file formats and databases may still use 32 bits. If a converted date looks like 1901, this is the usual cause.
A timestamp has no time zone
It names one instant, which is the same everywhere. Only the display changes. 1700000000 is 22:13:20 UTC, 17:13:20 in New York and 03:43:20 the next day in India, so a time zone only matters when you turn a timestamp into a clock time or the other way around.
Guide
- Unix Timestamps and Time Zones: Seconds vs ms — Seconds versus milliseconds, UTC versus local time, and the year 2038 limit, plus the mistakes that produce wrong dates.
Frequently asked questions
Does this handle timestamps in milliseconds?
Yes — a 13-or-more-digit number is treated as milliseconds automatically. Today's timestamp in seconds is 10 digits; it won't even reach 11 digits until the year 2286, let alone 13, so a 13-digit value can only sensibly mean milliseconds.
What is the Year 2038 problem?
A signed 32-bit timestamp runs out at 03:14:07 UTC on 19 January 2038. Software that stores time that way will wrap around to 1901. Systems using 64-bit timestamps are not affected.
Does a Unix timestamp depend on my time zone?
No. A timestamp counts seconds since 1 January 1970 UTC, so it identifies the same moment everywhere. Time zones only come in when you display it as a local date and time.