What’s 1705276800 in human time?
Monday, January 15, 2024. You’d never know that by looking at the number, but that’s how computers store time, seconds since January 1, 1970 00:00:00 UTC, a reference point called the Unix epoch.
Timestamps show up in database columns, API responses, JWT claims (exp, iat), log files, file metadata, and basically anywhere machines need to record when something happened. This tool converts them to dates you can actually read, and goes the other direction too.
There’s a live-updating current timestamp at the top of the page, which is surprisingly useful when you need to set an exp claim to “30 minutes from now” and need to know what the current epoch value is.
Seconds or milliseconds?
Two formats exist in the wild. 10-digit timestamps are seconds, the standard used by most Unix systems, PHP, Python’s time.time(), MySQL, and PostgreSQL. 13-digit timestamps are milliseconds, used by JavaScript (Date.now()), Java (System.currentTimeMillis()), many REST APIs, and Elasticsearch.
The tool detects the format by digit count, but you can also explicitly select which one you mean.
Timestamps you might recognize
0, January 1, 1970. The epoch itself.
1000000000, September 9, 2001. The “billennium.”
2147483647, January 19, 2038. The Y2K38 problem, max value of a signed 32-bit integer. Systems still using 32-bit timestamps will overflow on this date.
Both directions
Timestamp to date: paste 1705276800, get “Monday, January 15, 2024” in both local and UTC.
Date to timestamp: type 2024-01-15 or Jan 15, 2024 12:00 and get the epoch value. The tool accepts ISO 8601, natural language dates, and various date-time combinations.
For cron schedule debugging, the Cron Parser is also useful alongside timestamps.
FAQ
Seconds vs milliseconds, how do I tell?
Count the digits. 10 digits = seconds. 13 digits = milliseconds. The tool auto-detects.
What date formats work?
ISO 8601 (2024-01-15), natural language (Jan 15, 2024), date-time combos (2024-01-15T12:00:00). JavaScript’s Date parser handles most reasonable formats.
Negative timestamps?
They represent dates before 1970. -86400 is December 31, 1969. Support depends on the browser’s Date implementation.
What’s the Y2K38 problem?
On January 19, 2038, the Unix timestamp exceeds the maximum signed 32-bit integer. Systems using 32-bit timestamps will overflow. Most modern systems use 64-bit timestamps, which won’t overflow for billions of years.
Client-side?
Yes, all conversions happen in your browser using native JavaScript Date functions.