Unix Timestamp Converter
Turn a number like 1761200000 from a log, database row or API response into a readable date in your local time zone and UTC. The unit (seconds, milliseconds, microseconds, nanoseconds, Windows FILETIME) is picked from the number of digits and the alternatives are listed too.
Paste a date such as 2026-10-23 12:34 or Fri, 23 Oct 2026 12:34:00 GMT to get the timestamp. Everything runs in your browser.
Paste a string and the result appears here.
Other possible interpretations
What Unix time is
Unix time (epoch time) counts the seconds elapsed since 00:00:00 UTC on 1 January 1970. The same instant has the same value everywhere, which makes it the lingua franca for servers, databases and APIs.
JavaScript's Date.now() and Java's System.currentTimeMillis() use milliseconds (13 digits), Python's time.time() returns seconds with a fraction, and Go's UnixNano() and the Linux kernel use nanoseconds (19 digits).
| Digits | Unit | Example (2025-10-23 06:13:20 UTC) | Typical sources |
|---|---|---|---|
| 10 | seconds | 1761200000 | date +%s, Python, PHP, JWT exp |
| 13 | milliseconds | 1761200000000 | JavaScript, Java, Android, Kafka |
| 16 | microseconds | 1761200000000000 | PostgreSQL internals, some tracing systems |
| 19 | nanoseconds | 1761200000000000000 | Go UnixNano(), Prometheus, Linux kernel |
| 18 | Windows FILETIME | 133752920000000000 | 100 ns intervals since 1601. Registry, Active Directory lastLogon |
Time zones and gotchas
- A timestamp has no time zone; the zone only matters when you format it. This page shows your browser's zone and UTC side by side.
- Dates without an explicit offset are interpreted in your browser's time zone. Add
Zor+02:00to be explicit. - Values near midnight can fall on a different calendar day in UTC. If daily totals are off by one day, this is usually why.
- Daylight saving time shifts local times twice a year; the timestamp itself never jumps, which is why servers store epoch values or UTC.
- 32-bit signed seconds overflow on 19 January 2038 (the "year 2038 problem"). 64-bit integers and millisecond storage are unaffected.
Getting and converting timestamps in code
| Language / tool | Current timestamp | Timestamp → date |
|---|---|---|
| JavaScript | Math.floor(Date.now() / 1000) | new Date(ts * 1000).toISOString() |
| Python | int(time.time()) | datetime.fromtimestamp(ts, tz=timezone.utc) |
| Java / Kotlin | Instant.now().getEpochSecond() | Instant.ofEpochSecond(ts).atZone(ZoneId.of("America/New_York")) |
| MySQL | UNIX_TIMESTAMP() | FROM_UNIXTIME(ts) |
| PostgreSQL | EXTRACT(EPOCH FROM now()) | to_timestamp(ts) |
| Linux / macOS shell | date +%s | date -d @ts (macOS: date -r ts) |
| Excel / Google Sheets | =(NOW()-DATE(1970,1,1))*86400 (UTC sheet) | =ts/86400+DATE(1970,1,1), then apply a date format |
JWT claims such as exp and iat are shown as dates directly by the JWT decoder. To count the days between two dates use the date calculator.
FAQ
My value has 13 digits. Is it seconds?
Almost certainly milliseconds. Read as seconds it would land in the year 57,000. The converter chooses the unit that gives a plausible year (1990–2100) and lists the other readings underneath.
Does it handle negative values or dates before 1970?
Auto-detection is limited to 1990–2100 so that other number formats are not mistaken for timestamps. Dates outside that range are not converted here.
What does the "Now" button insert?
The current time from your device's clock, in seconds. If the clock is wrong, so is the value.
Sources
- Definition of Unix time: POSIX.1 "Seconds Since the Epoch"
- Date and time formats: RFC 3339; time zone data: IANA tz database
- Windows FILETIME: Microsoft Learn
Found this useful? Share it
Only the page link is shared. Your inputs and files are never included.