How do you tell seconds apart from milliseconds?

By the length of the number. A 10-digit value is treated as seconds, while a 13-digit value is treated as milliseconds. The tool shows which unit it detected so you can confirm it read your value the way you intended.

Is my data sent anywhere?

No. Every conversion happens locally in your browser using the built-in JavaScript Date object. Nothing is uploaded, logged or stored, and the tool keeps working offline once the page has loaded.

Unix Timestamp Converter — Epoch to Date, Both Ways (No Upload)

Q: What is a Unix timestamp?

A Unix timestamp is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970, known as the Unix epoch. It is a simple, timezone-independent way to store a moment in time and is used throughout databases, APIs and log files.

Unix Timestamp Converter

Convert a Unix (epoch) timestamp into a readable date — and turn any date back into a timestamp — in both directions, live. It auto-detects seconds vs milliseconds and shows local, UTC and ISO time. Free and 100% in your browser.

Timestamp → date

Unix timestamp

Detected unit: — (10 digits = seconds, 13 digits = milliseconds)

Your local time

UTC

ISO 8601

Relative

Date → timestamp

Pick a date and time

The date you pick is read in your local timezone.

Seconds

Milliseconds

UTC

🔒 100% private — runs in your browser, never uploaded.

How to use the timestamp converter

Paste a Unix timestamp into the top box — for example 1750684800 — or click Now to drop in the current time.
Read the result as your local time, UTC, ISO 8601 and a friendly relative string like “2 hours ago”.
Going the other way? Pick a date and time in the lower section and read the matching timestamp in seconds and milliseconds.
Copy any value with the button beside it — handy for pasting into code, configs or a database query.

What is a Unix timestamp?

A Unix timestamp counts the number of seconds since the Unix epoch — midnight UTC on 1 January 1970. Because it is just a single integer measured against a fixed point in UTC, it sidesteps the messiness of timezones, daylight saving and date formats, which is exactly why it shows up everywhere: in created_at database columns, JSON API responses, JWTexp claims, server logs and cron systems. Many platforms instead store milliseconds since the epoch (JavaScript’s Date.now() being the classic example), which is why a value can be 10 or 13 digits long.

This converter reads either form automatically. A 10-digit number is interpreted as seconds and a 13-digit number as milliseconds, and the tool tells you which unit it picked so you are never guessing. It then re-expresses that exact instant in your own timezone, in UTC and in machine-friendly ISO 8601, so the same moment is easy for both humans and code to read.

Is it private?

Yes. The conversion runs entirely on your device using the browser’s built-in Date object — there is no server round-trip, no logging and nothing is uploaded. You can use it offline once the page has loaded, which makes it safe for working with timestamps pulled from internal logs, production databases or anything you would rather not paste into a remote website.

Frequently asked questions

Why does the local time differ from UTC?

Your local time is shifted from UTC by your timezone offset (and daylight saving, if it applies). Both rows describe the very same instant — they are just two ways of labelling it. The ISO 8601 row is always shown in UTC, marked with a trailing Z.

Does the “Date → timestamp” section use my timezone?

Yes. The date and time you pick are read in your local timezone, then converted to a timezone-independent Unix timestamp. The UTC row below the result shows the same moment expressed in UTC so you can double-check it.

What range of dates is supported?

It relies on the standard JavaScript date range, which spans roughly 271,821 BC to 275,760 AD — far more than enough for any real timestamp. Values outside that range, or non-numeric input, are flagged with a clear error instead of a wrong answer.