Timestamp Converter

Converts Unix timestamps to human-readable dates and back. 1722211200 becomes a date and time in your zone; a date becomes the seconds-since-1970 integer that logs, APIs and databases speak.

How to use

1. Paste a timestamp to read it as a date — or enter a date to get its timestamp.
2. Check whether your number is seconds (10 digits) or milliseconds (13 digits).
3. Copy the converted value.
4. Mind the timezone: the same instant prints as different wall-clock times per zone.

When you actually need this

• Reading the created_at integers in logs, API responses and database rows.
• Producing timestamp bounds for a query's time range.
• Checking token expiry times issued as epoch seconds.
• Converting an incident's wall-clock time into the epoch range to grep logs by.

Epoch, milliseconds, and the 2038 footnote

Unix time counts seconds since 1970-01-01 00:00 UTC — one universal integer per instant, no timezone baked in, which is exactly why systems exchange time this way and render it locally at the edges. The commonest bug is a factor of a thousand: JavaScript's Date.now() returns milliseconds while most Unix tools use seconds, so a mistaken 13-digit value read as seconds lands "53,000 years away" — digit count is the tell. Timestamps are typically UTC-based, so a date that looks a day off usually reflects timezone rendering, not a wrong value. The old 32-bit signed-integer limit overflows in January 2038; modern 64-bit systems have already moved past it.

Related tools

FAQ

Does Timestamp Converter send my input to a server?

No. The conversion runs in JavaScript inside the page, so API keys, tokens, config files and any other sensitive text stay on your machine. You can verify this by opening your browser's network tab while you use the tool.

Does Timestamp Converter handle Unicode and non-ASCII characters?

Yes. Text is processed as UTF-8, so accented Latin, Korean, Japanese, Chinese, Cyrillic, Arabic and emoji all round-trip correctly rather than turning into question marks.

Can I use the output in production code?

Yes — the output follows the relevant standard exactly and is safe to paste into your project. As with any tool, run your own tests before shipping anything that depends on it.