Skip to main content
ToolsBay

Runs in your browser — nothing is uploaded · verify

Unix Timestamp Converter — free, and it runs in your browser

Convert between Unix epoch timestamps and human-readable dates.

  • Works in both directions, so one page covers reading a log and writing a query.
  • Seconds and milliseconds are both understood, and told apart automatically.
  • Shows the result in UTC and in your local timezone side by side.

  • 70 tools

    Free, with no account and no watermark

  • 0 bytes

    Of your files or text uploaded — this tool runs in the tab

  • No queue

    The work happens in this tab, not in a line behind other users

Three steps, nothing to install

Unix Timestamp Converter in three steps

  1. TIMESTAMP123456Paste it in — it never leaves the tab

    Paste the timestamp or the date

    A number out of a log, or a date you need as an epoch value. It works in both directions.

  2. TIMESTAMPDATEConverted on your own device

    See it both ways

    The result is shown in UTC and in your own timezone, along with the ISO 8601 form, so you can copy whichever the system you are debugging expects.

  3. Copy DATE

    Copy the value

    In the format you need, ready to paste into a query or a ticket.

Why use Unix Timestamp Converter

  • Seconds or milliseconds, resolved

    Reading a millisecond timestamp as seconds puts the date fifty thousand years out. The magnitude is checked so a log line is interpreted the way its system meant it.

  • UTC and local, together

    Almost every timestamp bug is a timezone bug. Both are shown at once so the offset is visible rather than assumed.

  • Free, with nothing to sign up for

    No account, no watermark, no daily cap and no trial that expires. Every tool on this site behaves the same way.

Frequently asked questions

By magnitude. Anything at or above 100,000,000,000 is treated as milliseconds, because a seconds value that large would be the year 5138. The detected unit is always shown so you can check.

The Unix epoch

A Unix timestamp counts the seconds elapsed since midnight UTC on 1 January 1970. It is a single number with no timezone, no daylight-saving rules and no locale — which is exactly why it is the format systems use to exchange a moment in time.

The confusion is almost always about units. Unix tooling, database EXTRACT(EPOCH …) and JWT exp claims use seconds. JavaScript's Date.now(), Java and most logging systems use milliseconds. Mixing them produces a date in 1970 or one fifty thousand years from now — both obvious once seen, both easy to ship.

The 2038 problem

Systems that store a timestamp in a signed 32-bit integer overflow on 19 January 2038, wrapping to 1901. Anything storing time in 64 bits — which is now the norm — is unaffected for a span far longer than the age of the universe.

Timestamps show up constantly in JWT claims, where exp and iat are seconds since the epoch. For scheduling rather than converting, see the cron expression generator.

Often used alongside

Related guides

More tools

70 tools, none of which want your file

Everything this tool does happens in the page you are looking at. No account, no upload, no watermark.

Browse all toolsRead the guides