100% client-side · free · no sign-up

Unix Timestamp Converter

Convert Unix timestamps to human-readable dates and back, in seconds or milliseconds, shown in both your local time and UTC.

—

Current timestamp (seconds)

—

Current timestamp (milliseconds)

Timestamp → date

Unix timestamp

Unit

Date → timestamp

Date and time (your local timezone) Interpreted in your device's local timezone; the result below is shown in both units.

This tool runs entirely in your browser. Nothing you type or generate is uploaded, stored or sent anywhere.

How to convert a timestamp

Both directions, one page.

Timestamp to date

Paste the number into the “Unix timestamp” field — the unit is auto-detected, or pick seconds/milliseconds manually.
Convert

Click “Convert to date” to see the instant in your local time, UTC and ISO 8601.
Copy what you need

Use the copy buttons for local, UTC or ISO format.
Date to timestamp

Pick a date and time in the lower panel (interpreted in your timezone) and click “Convert to timestamp” for seconds and milliseconds.

What this tool does

A Unix timestamp is a point in time stored as a single number: seconds (or milliseconds) elapsed since 1 January 1970, 00:00:00 UTC. Logs, databases, APIs and spreadsheets are full of them — and they are unreadable to humans without conversion.

This converter translates in both directions. Paste a timestamp and see the moment in your local timezone, in UTC and in ISO 8601 format; or pick a date and time and get the corresponding timestamp in both seconds and milliseconds. The current time in both units sits at the top of the page for quick reference.

Auto-detect guesses the unit from the number’s length — 13 or more digits means milliseconds — and you can override it when you know better. Everything is computed by your browser’s date engine; nothing is sent anywhere.

Key features

Both directions

Timestamp → date and date → timestamp on the same page, no tab-switching.

Three date formats

Every conversion shows local time, UTC and ISO 8601 — pick whichever your log or API expects.

Seconds and milliseconds

Auto-detected or manually selected, because JavaScript and Unix traditions disagree.

One-click copy

Copy buttons on every result so the value lands in your clipboard exactly as shown.

Completely local

Conversion uses your browser’s built-in date engine — nothing is transmitted.

Practical use cases

Reading server logs — turn log timestamps into local times you can reason about.
Debugging APIs — verify that expires_at or created_at values mean what you think they mean.
Database work — convert stored epochs for reports and spot-checks.
Scheduling checks — confirm a future timestamp lands when intended.
Comparing timezones — the local and UTC rows show the same instant two ways, ending “is that my time or theirs?” confusion.

Limitations and notes

Date → timestamp interprets your pick in your device’s local timezone — check the UTC row if the instant will be used elsewhere.
Auto-detect uses digit length; explicitly select the unit for ambiguous or unusual values.
The tool handles single instants, not durations, ranges or cron expressions.

Frequently asked questions

What is a Unix timestamp?

The number of seconds (or milliseconds) since 1 January 1970, 00:00:00 UTC — the standard way computers store points in time.

Should I use seconds or milliseconds?

Unix time is traditionally in seconds; JavaScript and many APIs use milliseconds. Auto-detect guesses from the number's length (13+ digits ⇒ milliseconds).

Why do local and UTC differ?

A timestamp is an absolute instant; local time renders it in your device's timezone. Both rows describe the same moment.

Why is my timestamp showing a date in 1970?

Almost always a unit mismatch: a seconds value treated as milliseconds lands near 1970, and a milliseconds value treated as seconds lands tens of thousands of years in the future. Set the unit explicitly instead of Auto-detect and convert again.

What is the difference between seconds and milliseconds timestamps?

Same instant, different scale — milliseconds are seconds × 1000. Unix systems traditionally use seconds; JavaScript’s Date and many web APIs use milliseconds. The converter shows both so you can match whatever your system expects.

Does the converter account for daylight saving time?

Yes — the local-time row uses your device’s timezone rules, including DST, for the date being shown. A timestamp is an absolute instant; DST only affects how it is displayed locally.

How do I get the timestamp for a future date?

Use the lower panel: pick the date and time (interpreted in your timezone) and click “Convert to timestamp”. Both the seconds and milliseconds values appear, ready to copy.