The Locolory toolkit / Developer Utilities
Convert Unix timestamps in seconds, milliseconds, or microseconds to human-readable dates across global timezones—locally and instantly.
What is a Unix epoch timestamp? It is the number of seconds elapsed since 00:00:00 UTC on January 1, 1970, conventionally excluding leap seconds. APIs commonly use seconds or milliseconds.
No API calls. Conversion runs locally with browser Date and Intl APIs.
Detected seconds
2026-11-12T07:35:24.000Z
Browser local
11/12/2026, 7:35:24 AM
Relative
0 minutes ago
Weekday / day of year
Thursday / 316
Unix seconds
1794468924
Unix milliseconds
1794468924000
new Date(1794468924000)A signed 32-bit integer can store at most 2,147,483,647 seconds after the epoch: 03:14:07 UTC on January 19, 2038. Adding one second can overflow legacy implementations.
Modern systems commonly use 64-bit storage, but databases, embedded devices, file formats and integrations should still be audited end to end.
| JavaScript | new Date(1794468924000) |
|---|---|
| Python | datetime.fromtimestamp(1794468924, tz=timezone.utc) |
| Java | Instant.ofEpochMilli(1794468924000L) |
| Go | time.UnixMilli(1794468924000) |
| PHP | (new DateTimeImmutable())->setTimestamp(1794468924) |
Your input shapes the next update
A short note opens in your email app, ready to send to hello@locolory.store.
Contemporary timestamps are often about 10 digits in seconds, 13 in milliseconds, or 16 in microseconds, but digit count changes with dates and signs. This tool detects units by magnitude and shows the detected unit.
No. A Unix timestamp represents one instant relative to the UTC epoch. Timezones only change how that instant is displayed as a calendar date and clock time.
The Unix epoch is 00:00:00 UTC on January 1, 1970. Unix time counts elapsed seconds from that instant and conventionally excludes leap seconds.
A signed 32-bit seconds counter reaches 2,147,483,647 at 03:14:07 UTC on January 19, 2038. Systems using wider integer representations avoid that specific overflow.