Timestamp Converter

Convert Unix timestamps to human-readable dates and back, across any time zone — with batch conversion, world clocks, time difference math, custom formats, and a timestamp generator, all local to your browser.

Loading tool…

What is a Unix timestamp?

A Unix timestamp is the number of seconds elapsed since 00:00:00 UTC on 1 January 1970, a moment known as the epoch. It is how computers store time almost everywhere: in databases, log files, API payloads, JWT expiry claims, and file metadata. One integer, no time zone, no ambiguity about date formats — which is exactly why it is used, and exactly why humans cannot read it.

Two details matter in practice. Some systems store seconds and others milliseconds, so a value with thirteen digits is a millisecond timestamp and ten digits is seconds; mixing them up puts you off by a factor of a thousand. And a timestamp is always UTC, so converting it for a human means applying a time zone — the same instant is a different wall-clock time in Amman, London, and New York.

Why we built this tool

You reach for this while reading logs, correlating events across services, checking when a token expires, or working out whether a record was written before or after an incident.

The values themselves are rarely secret, but they arrive glued to log lines and payloads that very much are. A converter that keeps everything local means you can paste a whole line without thinking about what else is in it. Ours runs entirely in the browser using the JavaScript date API, so no request is made and nothing is stored. It also works offline, which matters when you are deep in an incident and would rather not be relying on someone else's uptime.

Tips and common mistakes

  • Ten digits mean seconds, thirteen mean milliseconds — count before you convert.
  • Timestamps are always UTC; the local time you see depends on your device's time zone setting.
  • Daylight saving transitions make some local times ambiguous or non-existent, which is exactly why systems store UTC.
  • Negative timestamps are valid and represent dates before 1970.

Open Timestamp Converter with a link

Assistants and scripts can open Timestamp Converter with its input already in the link, after the #, which never leaves your device:

  • #text= — the text to work on

Example: https://mygadgets.ink/tools/timestamp-converter/#text=... · also compressed gz fields and ?url=. How tool links work

Quick start: using Timestamp Converter

  1. Paste a Unix timestamp to convert it into a readable date, or enter a date to get the timestamp.
  2. Check whether your value is in seconds or milliseconds — count the digits.
  3. Read the result in both UTC and your local time zone.
  4. Use the current-time option when you need a timestamp for right now.
  5. Copy whichever representation you need.

Reading token expiry? JWT Decoder shows the claim; this tool turns it into a date. For age arithmetic in human terms, see Age Calculator.

What a Unix timestamp is

A Unix timestamp counts the seconds elapsed since the "epoch" — midnight UTC on January 1, 1970. It is a single integer with no time zone, no formatting, and no ambiguity, which is exactly why systems love it. 0 is the epoch itself; 1721390400 is a moment in July 2024. Humans cannot read it at a glance, hence the need to convert.

The seconds vs. milliseconds trap

This catches everyone at least once. Unix timestamps come in two flavors:

  • Seconds — the classic form, 10 digits for current dates (e.g. 1721390400).
  • Milliseconds — used by JavaScript and many APIs, 13 digits (e.g. 1721390400000).

Feed a milliseconds value into a seconds parser and you land thousands of years in the future; do the reverse and you land in 1970. If a converted date looks absurd, you almost certainly mixed up the units — check the digit count.

Time zones matter

The timestamp itself is always UTC, but you usually want to see the date in a specific time zone. The same instant is a different wall-clock time in London, New York, and Tokyo. When converting, be clear whether you are reading the result as UTC or your local time, especially when comparing timestamps from systems in different regions.

Common uses

  • Read timestamps in logs to see when an event happened.
  • Decode a JWT's exp claim to check token expiry — pair with JWT Decoder.
  • Debug scheduling by converting stored times to readable dates.
  • Set a specific time by finding its timestamp for a config or test.

Related Developer Tools

Browse all Developer Tools →