Unix Timestamp Converter

How to use it

Paste a timestamp or a date. The tool works out what it is:

• 10 digits — seconds (Unix time, used by most Linux tools, JWTs, databases);
• 13 digits — milliseconds (JavaScript, Java, many APIs);
• 16 / 19 digits — microseconds / nanoseconds (some logs, Go, tracing systems);
• a date — 2026-11-02T09:20:00Z, Mon, 02 Nov 2026 09:20:00 GMT and similar.

You get the same moment as Unix seconds and milliseconds, ISO 8601, RFC 2822, in the time zone you choose, and as “3 hours ago”. Now fills in the current time.

On the command line

date +%s                                # now, in seconds
date -u -d @1762075200                  # seconds → date (GNU/Linux)
date -u -r 1762075200                   # the same on macOS / BSD
date -d '2026-11-02 09:20:00 UTC' +%s   # date → seconds

In SQL: to_timestamp(1762075200) in PostgreSQL, FROM_UNIXTIME(1762075200) in MySQL.

FAQ

Why is my date in 1970, or in the year 50000?

The unit is wrong: a timestamp in milliseconds read as seconds lands tens of thousands of years in the future; seconds read as milliseconds land in January 1970.

What is the year 2038 problem?

Systems that store Unix time in a signed 32-bit number overflow on 19 January 2038, 03:14:07 UTC. Current 64-bit systems are fine; old embedded devices and some file formats aren’t.

Why would I convert a timestamp from a token?

exp and iat in a JWT are Unix timestamps in seconds. If a token is refused as expired, comparing them with the time now is the first check: see JWT “jwt expired”.