Date & time · Unix epoch
Year 2038 problem checker.
Enter a Unix timestamp or a UTC date and see whether it fits in a signed 32-bit integer, what it becomes if it overflows, and how long is left until 2038-01-19 03:14:07 UTC.
Check a value
Result
Enter a timestamp in seconds, or choose a UTC date.
The limits that matter
Unix time was historically stored in a signed 32-bit integer. The largest value is 231 − 1. One second later the counter wraps to the most negative value, which software reads as a date in 1901.
| Limit | Seconds | UTC |
|---|---|---|
| Signed 32-bit minimum | -2147483648 | 1901-12-13T20:45:52Z |
| Signed 32-bit maximum | 2147483647 | 2038-01-19T03:14:07Z |
| Unsigned 32-bit maximum | 4294967295 | 2106-02-07T06:28:15Z |
Who is affected?
Anything that keeps seconds since 1970 in a 32-bit signed field: embedded devices, old file formats and database columns, network protocols and 32-bit builds of C code using a 32-bit time_t. Platforms with a 64-bit time_t are good for roughly 292 billion years. The Linux kernel documentation records that the old 32-bit tv_sec overflows in 2038 and that interfaces using it have been replaced. To fix your own code, store timestamps in 64 bits or as an ISO 8601 string, and test with a date after 2038-01-19.
FAQ
What is the year 2038 problem?
A signed 32-bit integer tops out at 2,147,483,647 seconds, which is 2038-01-19T03:14:07Z. One second later it wraps to -2,147,483,648, which reads as 1901-12-13T20:45:52Z. The Linux kernel documentation notes that the 32-bit tv_sec member overflows in 2038. Systems that store time in 64 bits are not affected. Check a value for 32-bit overflow.
What is the exact moment of the 2038 problem?
Second 2,147,483,647 is 2038-01-19T03:14:07Z. A signed 32-bit counter cannot hold the next second, 2,147,483,648.
Does the year 2038 problem affect my phone or laptop?
Modern 64-bit operating systems and current phones store time in 64 bits. The risk is in older or embedded 32-bit systems and in software or databases that keep a timestamp in a 32-bit field.
What about unsigned 32-bit timestamps?
An unsigned 32-bit counter reaches 4,294,967,295, which is 2106-02-07T06:28:15Z, but it cannot store dates before 1970.
What is Unix epoch time?
Unix time counts seconds since 00:00:00 UTC on 1 January 1970, the Unix epoch. POSIX defines it so that every day is exactly 86,400 seconds, which is why 1970-01-02T00:00:00Z is 86400.
Does Unix time include leap seconds?
No. POSIX counts each day as exactly 86,400 seconds, so a leap second is not a separate value: the timestamp repeats or is smeared by the system clock, and 2017-01-01T00:00:00Z is 1483228800 even though UTC itself had a leap second added at the end of 2016. IERS Bulletin C 72 (July 2026) announced that no leap second will be introduced at the end of December 2026.
Is my data sent anywhere?
No. The conversion runs in your browser and nothing you type is uploaded or stored.
Sources (each opened 2026-10): POSIX.1-2017 Base Definitions, 4.16 Seconds Since the Epoch; Linux kernel documentation, Timekeeping; ECMAScript Language Specification, Time Values and Time Range; IERS Bulletin C 72 (leap second announcement, July 2026).