160
Convert a Unix timestamp to a date
On the default, 1792671060: Thursday, October 22, 2026, 12:11:00 PM UTC. Enter any timestamp below.
FREE TOOL · TIME & DATE
Unix Timestamp Converter
Type any Unix timestamp — 10 digits of seconds or 13 digits of milliseconds — and see the exact date and time in UTC and your local zone, plus how far it sits from the 1970 epoch. Flip the direction to turn any date into a timestamp.
What a Unix timestamp actually is
A Unix timestamp is the number of seconds that have passed since January 1, 1970, 00:00:00 UTC — the “epoch.” One integer counts every second: 0 was the first second of 1970, 1,000,000,000 was September 9, 2001, and as this page was written the counter sat near 1.79 billion. Developers love timestamps because they are a single number: no time zones, no daylight saving, no “is that March 4 or April 3?” — just arithmetic.
Reading a timestamp by hand: the divide trick
Divide the timestamp by 86,400 (seconds per day) and you get days since the epoch: 1792671060 ÷ 86,400 = 20,748.5 days. Day 20,748 after January 1, 1970 is October 22, 2026; the .5 means halfway through the day — about noon UTC. That is all the converter does, except it also names the weekday and shows your local time.
Output · formula · meaning
| Output | Formula | What it means |
|---|---|---|
| UTC date & time | timestamp → days → calendar | Thursday, October 22, 2026, 12:11:00 PM UTC — the same instant everywhere on Earth. |
| Local date & time | UTC ± your zone offset | What your clock shows — 8:11 AM EDT on October 22, 2026, four hours behind UTC. |
| Days since epoch | timestamp ÷ 86,400 | 20,748.5 days — the timestamp expressed as a day count. |
| 32-bit range check | |timestamp| ≤ 2,147,483,647 | Inside: a signed 32-bit integer can hold it. Outside: only 64-bit systems can. |
Seconds vs milliseconds: the ×1,000 trap
Ten digits means seconds (most APIs, PHP, Python’s time.time()); thirteen digits means milliseconds (JavaScript’s Date.now(), MongoDB, many JSON APIs). If your converted “date” lands in January 1970, you fed seconds into a milliseconds field — multiply by 1,000. If it shows the year 50,000-something, you fed milliseconds into a seconds field — divide by 1,000. The unit selector on the converter handles both.
The 2038 problem
Signed 32-bit integers top out at 2,147,483,647 seconds — January 19, 2038, 03:14:07 UTC. Systems still storing time in 32 bits will roll over to December 1901 like a car odometer flipping past 999,999. Modern 64-bit systems push the overflow roughly 292 billion years out, so the industry’s answer was simply “use bigger integers.” The converter flags any timestamp beyond the 32-bit range.
Negative timestamps and leap seconds
Negative timestamps are perfectly valid — they count before the epoch: −1 is the last second of 1969. One wrinkle: Unix time pretends every day is exactly 86,400 seconds, so leap seconds are smeared or skipped depending on the system. Timestamps can’t represent them precisely — fine for everything except high-precision science.
Who uses this
- Backend developers: reading epoch values out of API logs, JWT expiries, and database rows.
- Data analysts: converting epoch columns in CSVs and warehouses into human dates.
- QA engineers: setting cookie and cache expiries a precise number of seconds out.
- Students: the 2038 problem is a classic exam question — this page is the worked example.
Accuracy & limitations
Conversions are exact integer math on the UTC instant — there is no rounding anywhere. The local-time readout uses your browser’s time-zone database, so it matches your device clock. Values far from 1970 (hundreds of thousands of years out) exceed the date range the converter can represent and are rejected. Unix time ignores leap seconds, and so does this tool.
Counting down to a moment instead? The countdown calculator ticks toward any date, the business days calculator skips weekends, and the military time converter reads the 24-hour clock. The full hand method lives in the how to convert a Unix timestamp guide.
Cite this calculatorBright Side Kit. “Unix Timestamp Converter.” brightoolbox.com, 2026.
Bright Side Kit. "Unix Timestamp Converter." https://brightoolbox.com/unix-timestamp-converter/ Accessed October 22, 2026.Frequently asked questions
What is a Unix timestamp?
The number of seconds since January 1, 1970, 00:00:00 UTC (the “epoch”). It is how computers store moments in time: one plain integer, no time zones attached.
How do I convert a Unix timestamp to a date?
Type it into the converter. By hand: divide by 86,400 to get days since January 1, 1970 — 1792671060 ÷ 86,400 = 20,748.5 days, i.e. October 22, 2026, about noon UTC.
Why does my timestamp have 13 digits?
It is in milliseconds, not seconds — JavaScript’s Date.now() and many JSON APIs work this way. Divide by 1,000 (or pick “milliseconds” in the unit selector) to get the normal 10-digit form.
What is the difference between the UTC and local results?
UTC is the universal instant — the same everywhere. Local applies your device’s time zone: 12:11 PM UTC is 8:11 AM EDT in New York (UTC−4) and 1:11 PM BST in London.
What is the 2038 problem?
Signed 32-bit integers max out at 2,147,483,647 seconds — January 19, 2038, 03:14:07 UTC. Old 32-bit systems will wrap around to 1901 at that instant. 64-bit systems are unaffected.
Can a Unix timestamp be negative?
Yes — negative values count before the epoch. −86,400 is December 31, 1969. The converter handles them like any other value.
How do I get the current timestamp in code?
JavaScript: Math.floor(Date.now()/1000) · Python: int(time.time()) · PHP: time(). All three return seconds since the epoch.
Do Unix timestamps account for leap seconds?
No — Unix time defines every day as exactly 86,400 seconds. Leap seconds are handled by smearing or skipping, depending on the system, so sub-second precision around a leap second is approximate.