Developer Tools

Unix Timestamp Converter

Convert Unix timestamps to human-readable dates and back. Handles seconds and milliseconds, local time and UTC, and shows the ISO 8601 string plus relative time like '3 days ago'.

Free, no sign-upRuns in your browserNothing uploaded

Timestamp or date string

Accepts Unix seconds, Unix milliseconds, or any date format this browser can parse. Seconds and milliseconds are detected automatically.

UTC

2026-10-17 21:46:35 UTC

Your local time

Saturday, October 17, 2026 at 9:46:35 PM

Weekendnowin the pastTimezone offset UTC+0

The same instant in every format

Unix seconds1792273595

Unix milliseconds1792273595000

ISO 8601 (UTC)2026-10-17T21:46:35.000Z

ISO 8601 (local)2026-10-17T21:46:35

RFC 2822Sat, 17 Oct 2026 21:46:35 GMT

SQL (UTC)2026-10-17 21:46:35

Human readableSat, 17 Oct 2026 21:46:35 GMT

Detected input as seconds. Values below 100,000,000,000 are read as seconds; anything larger as milliseconds.

Reference points

Now: 1792273595
Start of today (UTC): 1792195200
Start of this week (UTC, Monday): 1791763200
In one hour: 1792277195
In one day: 1792359995
Unix epoch (1970-01-01): 0

A Unix timestamp is the number of seconds since 1 January 1970 00:00:00 UTC. It is how most systems store time: databases as an integer column, JavaScript's Date objects internally, log lines, file metadata and API payloads. It is unambiguous, sorts correctly as a string, and costs very little space, which is why it is everywhere.

Paste a timestamp and you get the readable date in UTC and in your own timezone, the ISO 8601 string, the day of week, and a relative description like '3 days ago'. Paste a date in almost any common format and you get the timestamp back in seconds and milliseconds. This matters because milliseconds versus seconds is the single most common bug in this area - a value like 1760000000000 is milliseconds and Date.now() gives milliseconds, while most database columns and shell date output use seconds.

Note that a timestamp is always UTC. It is not a time zone and it does not know about daylight saving. '23:30' is different on the day the clocks change, which is precisely why you should store timestamps and convert to a local time at the point of display.

Unix Timestamp Converter features

Automatic seconds or milliseconds detection

Any value below 100000000000 is treated as seconds and anything above as milliseconds, which covers every realistic date.

UTC and local time side by side

Both interpretations plus the numeric offset, so there is no guessing about which one you are looking at.

ISO 8601 output

The format every API expects, including the trailing Z for UTC, ready to paste.

Relative time

'3 days from now' or 'in 2 hours', which is far easier to sanity-check than a raw number.

Reverse conversion

Dates to timestamps, with your local input and the corresponding UTC instant both shown.

Common formats at a glance

Unix seconds, milliseconds, ISO 8601, RFC 2822, SQL datetime and a human-readable string, all at once.

This week at a glance

A rolling list of recent and upcoming reference points such as the start of the day, the week and the Unix epoch itself.

How to use the Unix Timestamp Converter

Paste a timestamp
Seconds or milliseconds are detected automatically, so 1760000000 and 1760000000000 both work. You can also start from the current time.
Read both interpretations
The date is shown in UTC and in your browser's local timezone, plus the ISO 8601 string and a relative form such as '2 hours ago'.
Go the other way
Type a date and time in the date field, or paste any format a parser recognises, and the Unix seconds and milliseconds appear. The UTC equivalent of your local input is shown so you can see the offset being applied.
Copy what you need
Copy the Unix seconds, the milliseconds, the ISO string or the SQL-compatible UTC literal.

Frequently asked questions

What is the Unix epoch?

1 January 1970 at 00:00:00 UTC. Unix timestamps count seconds from that instant, which is why 0 means the epoch. It was chosen because it was close to the time the first Unix systems were built; nothing about it is a technical requirement.

Should I use seconds or milliseconds?

Match your system. JavaScript's Date.now() and Unix() return milliseconds; most database timestamp columns and the shell date command use seconds. Mixing them is the classic cause of a date landing in the year 56000 or 1970.

How do I tell which one I have?

By magnitude. Any value under 100000000000 (1e11) is seconds, which covers dates up to the year 5138. Anything larger is milliseconds. This tool does that detection for you and shows both readings so you can confirm.

Is a Unix timestamp the same everywhere in the world?

Yes, and that is the point. A timestamp identifies one absolute instant, so it is identical regardless of the reader's timezone. Local time and daylight saving are applied only when you convert it for display, which is why you should never store a pre-formatted local date string.

What does 2038 mean for timestamps?

It is the 32-bit signed integer overflow point, 19 January 2038 at 03:14:07 UTC. Code that stores seconds in a 32-bit integer breaks then. 64-bit integers are unaffected, which is why the 2038 problem is a property of the old type rather than of Unix time itself.

Can I convert a date like '2026-03-14 09:30:00'?

Yes. The reverse converter accepts common date and datetime formats and shows both how it was interpreted in your local timezone and the resulting UTC instant, so you can confirm the offset before you use the number.

JSON Formatter & ValidatorFormat, minify and validate JSON with exact line and column errors.Open UUID GeneratorGenerate cryptographically secure UUID v4 or time-ordered v7 in bulk.Open JWT Decoder & InspectorInspect JWT headers, claims and expiry locally. The token never leaves your device.Open

Every tool, in one place

ToolForge has unix timestamp converter plus a growing set of image, colour and developer tools. All of them run locally in your browser, free and without an account.

Browse all tools

UTC