LOCAL FILES. CLEAR RESULTS.

Unix Timestamp Converter

Convert Unix timestamps to readable dates and back. Auto-detects seconds vs. milliseconds, shows UTC and local time — free, no sign-up.

What a Unix timestamp is

A Unix timestamp counts seconds since 1970-01-01 00:00:00 UTC — the Unix epoch. 1700000000 is not an arbitrary number; it is 2023-11-14 22:13:20 UTC. APIs, databases, JWT tokens, and log files prefer this format because a single integer sidesteps every timezone and formatting disagreement. When you are debugging and staring at a ten-digit number, this converter turns it back into a date instantly.

Seconds vs. milliseconds

The most common timestamp mistake is mixing up the two units. Classic Unix timestamps are seconds (10 digits today); JavaScript's Date.now(), Java, and many modern APIs use milliseconds (13 digits). A millisecond value read as seconds lands you tens of thousands of years in the future — a classic debugging head-scratcher. Auto-detect mode counts the digits for you (10 → seconds, 13 → milliseconds), and you can pin the unit explicitly when dealing with unusual values. For the epoch-millis perspective specifically, see our epoch converter page.

Converting in both directions

Paste a timestamp to get the date, or paste a date to get the timestamp — for scheduling a cron job, computing an expiry, or generating test fixtures. The "use current time" button fills in right now, handy for "what is the timestamp for this moment?" questions during debugging.

UTC and local time, side by side

Every result shows the ISO 8601 string, the UTC rendering, and your browser's local time together. That trio eliminates the usual follow-up question ("wait, which timezone was that?") when you paste a converted time into a ticket or a chat.

Private by design

Timestamps often come from internal logs and production data. Conversion runs entirely in your browser — pasted values never leave the tab.

Frequently asked questions

What is a Unix timestamp?

The number of seconds (or milliseconds) since 1970-01-01 00:00:00 UTC — the "Unix epoch". APIs, databases, and log files store times this way because a single number is unambiguous and easy to compare.

How do I know if my timestamp is in seconds or milliseconds?

Count the digits: 10 digits means seconds (e.g. 1700000000), 13 means milliseconds (e.g. 1700000000000). Auto-detect mode applies exactly this rule; set the unit manually for unusual values.

Which timezone are the results in?

Both: every conversion shows UTC and your browser's local time side by side, plus ISO 8601, so there is no ambiguity to resolve later.

Can it convert dates before 1970?

Yes. Dates before the epoch become negative timestamps and convert correctly within the representable range.

What date formats can I convert from?

Anything JavaScript parses reliably: YYYY-MM-DD, YYYY-MM-DD HH:MM, and full ISO 8601 strings.

Related tools