Unix Timestamp Converter
A Unix timestamp is the number of seconds elapsed since 1970-01-01 00:00:00 UTC — right now it is 1787525040. Paste any timestamp below to convert it to ISO 8601 and human-readable dates in both UTC and your local timezone; seconds, milliseconds and microseconds are detected automatically.
Current Unix time
1787525040
2026-08-23T22:44:00.293Z
How epoch conversion works
Unix time counts unbounded integer ticks from the epoch instant 1970-01-01T00:00:00Z, deliberately ignoring leap seconds — every day is exactly 86,400 ticks. Because the count is timezone-free, one timestamp maps to exactly one instant worldwide; formatting it into a calendar requires choosing a zone afterwards (UTC here, plus your browser's zone when JavaScript runs).
Magnitude auto-detection rules
| Digits (approx.) | Unit | Example | Represents |
|---|---|---|---|
| ≤ 11 | seconds | 1779000000 | 2026-05-15T04:00:00Z-ish era |
| 12–14 | milliseconds | 1779000000000 | Java/JavaScript defaults |
| 15–16 | microseconds | 1779000000000000 | Python time.time_ns()//1000, DB logs |
The boundaries come from magnitude alone: second-based times stay under 1011 until year 5138, while real millisecond times crossed 1011 in 1973 and stay under 1014 until year 33658. Microsecond values simply exceed that. Sub-millisecond precision is preserved in the ISO output's fractional part.
Scheduling jobs around these instants? The cron expression generator turns wall-clock rules into crontab syntax; identifiers you log alongside timestamps can be minted with the UUID v4 generator; secrets used by logging pipelines should come from the password generator; and TCP/UDP port numbers referenced by syslog filters live in the common ports cheat sheet.
Frequently asked questions
What is a Unix timestamp?
An integer count of seconds since 1970-01-01 00:00:00 UTC (the 'epoch'), ignoring leap seconds. It is the standard way computers store absolute points in time because arithmetic on integers beats calendar math.
How do I convert a Unix timestamp to a date?
Paste it above. The rule everywhere: treat the number as UTC ticks, build an instant, then format that instant in whichever timezone you need. In JavaScript, new Date(1779000000 * 1000).toISOString(); in PowerShell, [DateTimeOffset]::FromUnixTimeSeconds(1779000000).
Why does my timestamp convert to January 1970?
You almost certainly fed milliseconds into a seconds parser (or vice versa). Values near 1.7 billion are seconds; near 1.7 trillion are milliseconds. This tool auto-detects the unit by digit count so the mistake can't happen here.
How do I get the current Unix timestamp?
In a terminal: date +%s (Linux/macOS), [int][double]::Parse((Get-Date -AsUTC -Format o)) or simply [DateTimeOffset]::Now.ToUnixTimeSeconds() in PowerShell. JavaScript: Math.floor(Date.now() / 1000). The box above updates every quarter-second.
Is the Unix timestamp affected by time zones or DST?
No. A timestamp is one absolute instant; time zones only affect how humans format it. 2026-08-23 04:05:06 in Berlin and 2026-08-22 22:05:06 in New York are the same timestamp.
Will Unix timestamps break in 2038?
Only 32-bit signed implementations break, at 2147483647 seconds (2038-01-19 03:14:07 UTC). Modern 64-bit systems — including every current phone, server and this website — are unaffected and remain valid for roughly 292 billion years.