Unix timestamp converter

Seconds or milliseconds

Paste a Unix timestamp (seconds or milliseconds) to see the date and time in UTC or your chosen time zone, or paste a date to get its epoch seconds and milliseconds. Leave it empty for now.

Fill in the fields to see the result.

How to use it

Paste a timestamp or an ISO 8601 date; leave empty for the current time.
Pick the time zone to show it in (remembered).
Copy the seconds, milliseconds, ISO string or local time.

Details

Epoch: Seconds since 1970-01-01 00:00:00 UTC, ignoring leap seconds
Detection: 13-digit numbers are milliseconds, shorter ones seconds
Input dates: ISO 8601 with Z or an offset, like 2026-07-04T09:30:00-04:00

Questions

Is my timestamp in seconds or milliseconds?

Current times are 10 digits in seconds (1.7 billion) and 13 digits in milliseconds. JavaScript's Date.now() and Java give milliseconds; Unix tools, Python's time.time() and most APIs use seconds.

Do Unix timestamps have a time zone?

No. A timestamp is the same instant everywhere; the time zone only changes how it's displayed. That's why the converter shows UTC and your chosen zone.

What is the year 2038 problem?

Signed 32-bit seconds run out at 03:14:07 UTC on 19 January 2038 (2147483647). Systems that store time in 64 bits, as modern ones do, are fine.

How do I get the current timestamp in code?

JavaScript: Math.floor(Date.now() / 1000). Python: int(time.time()). Shell: date +%s. SQL (Postgres): extract(epoch from now()).

Is what I type sent anywhere?

No. The calculation runs in this browser tab with the same code our MCP server uses. Nothing you type is sent to a server or saved, apart from settings like filing status, which stay in this browser.

Can an AI agent use this?

Yes. The same function is a tool on our free MCP server at tools.cuelark.com/mcp, so ChatGPT, Claude or Cursor get exactly the answer this page shows. 'Copy MCP call' gives you the arguments.