Convert Unix timestamps to dates and back, in seconds, milliseconds, microseconds or nanoseconds, across every IANA timezone.
The unit is detected automatically. You can also force seconds, milliseconds, microseconds or nanoseconds.
Examples: 1786435200 · 1786435200000 · 2026-08-11 · 2026-08-11 10:00 · 2026-08-11T08:00:00Z
Conversion happens locally in your browser. Values are never sent to a server.
The answer you came for is first; the technical formats are grouped below it.
—
—
—
—
—
Enter a timestamp or a date on the left and the conversion appears here. Nothing is sent anywhere: it all happens in this browser tab.
Work out the gap between two moments without a separate calculator. Useful for logs, TTLs, caches and tokens. Both fields accept the same formats as the converter above.
Paste up to 500 entries, one per line. Timestamps and dates can be mixed; each line is detected on its own.
The examples follow the converter. Pick a language and copy the snippet, with the sub-second part handled the way each runtime actually handles it.
Each snippet is generated for the unit shown above it, so a millisecond value is never quietly multiplied by a thousand again.
What actually matters, in a form you can scan rather than a wall of text.
Unix time counts the seconds elapsed since 1 January 1970 at 00:00:00 UTC, an instant known as the epoch. One integer, no calendar rules, no locale, no timezone: that is why almost every log file, database and API uses it internally and only converts to a readable date at the edge.
A current timestamp is 10 digits in seconds and 13 in milliseconds, which is where the rule of thumb comes from. It is only a rule of thumb: the digit count depends on the date, negative values break it, and microseconds and nanoseconds add three more digits each. This converter reads the size of the value instead, tells you what it decided, and lets you say otherwise.
A timestamp identifies one instant everywhere in the world. The timezone only decides how that instant is written down, which is why 1786435200 is 09:00 in London and 17:00 in Tokyo on the same day. Daylight saving is part of the writing-down step too, so this tool takes every offset from the IANA database in your browser rather than calculating one.
A signed 32-bit integer holds Unix seconds only up to 2147483647, which is 19 January 2038 at 03:14:07 UTC. One second later it wraps to 1901. This concerns that one storage choice, not Unix time itself: 64-bit systems and every current mainstream language are fine. Where it still bites is 32-bit embedded firmware, fixed-width binary formats and old integer columns that were never widened.
The Unix epoch is 1 January 1970 at 00:00:00 UTC. A Unix timestamp counts how many seconds have elapsed since that instant, so it is a single number that identifies a moment in time without needing a calendar, a locale or a timezone.
A Unix timestamp is an offset from a fixed instant, so it is not "in" any timezone at all. It is usually described as UTC because the epoch itself is defined in UTC. Timezones only matter when you turn the number into a readable date, which is why the same timestamp shows a different wall clock in Warsaw and in Tokyo.
Almost certainly because it is in milliseconds. JavaScript, Java and most JSON APIs count milliseconds, which multiplies the value by a thousand and adds three digits. Digit count is a good clue, not a rule: this converter picks a unit from the size of the value and lets you override it.
Only the resolution. 1786435200 and 1786435200000 are the same instant; the second one can also express fractions of a second. Mixing them up is the most common timestamp bug there is, and it is easy to spot: read as seconds the value lands in 2026, and the same digits read as milliseconds land in January 1970.
Yes, as negative numbers. -86400 is 31 December 1969. Some older systems and databases store the value as an unsigned integer and refuse negatives, so a pre-1970 date can survive one system and break the next.
No. That is a feature, not a gap: storing an instant and formatting it per user is what keeps a log readable across regions. If you need the original local time as well, store the IANA zone identifier next to the timestamp.
In a shell, date +%s. In JavaScript, Math.floor(Date.now() / 1000). In Python, int(time.time()). In PHP, time(). In SQL, EXTRACT(EPOCH FROM NOW()) on PostgreSQL or UNIX_TIMESTAMP() on MySQL. The live value at the top of this page is the same number.
A Unix timestamp stored in a signed 32-bit integer runs out of room on 19 January 2038 at 03:14:07 UTC, and the next second overflows into 1901. Modern 64-bit systems and languages are not affected, but embedded firmware, old file formats and 32-bit database columns can still be.
Every conversion runs in your browser. No timestamp, date or pasted list is ever sent to a server.
Lodash is one of the most widely used utility libraries in the JavaScript ecosystem, especially in older and enterprise codebases. es-toolkit is a modern alternative built around TypeScript, ES modules, tree-shaking, and smaller bundles. The question is not whether Lodash still works. It does. The better question is whether your project still needs the weight and legacy patterns that come with it, or whether a leaner, type-first option fits your stack better in 2026.
Axios became the default HTTP client for many JavaScript teams because it offered a clean API before Fetch became the standard browser primitive. Today, many teams can use native Fetch directly or pick Ky, a small wrapper that adds convenience without the full weight of Axios. The right choice depends on whether you actually need Axios-specific features such as interceptors and existing wrappers, or whether a lighter, more modern request layer fits your app better.
Moment.js was once the default date library for JavaScript applications, but modern frontend stacks usually need smaller, more modular, and more tree-shakeable tools. date-fns provides date utilities as independent functions, which makes it a better fit for many modern apps. The decision is usually straightforward for new projects: Moment.js may remain in legacy code, but date-fns is often a better choice for new development.