How to use the timestamp converter
Paste any timestamp — the tool works out what it is. Epoch seconds, milliseconds, microseconds and nanoseconds are told apart by their size; ISO 8601 strings and plain dates parse directly. You instantly get your local time, UTC, both epoch forms, a relative reading like "3 days ago", and the ISO week. Click any tile to copy it, and the live Unix clock at the top is always one click from your clipboard.
What a Unix timestamp actually is
A Unix timestamp counts seconds since midnight UTC on 1 January 1970 — the "epoch". It has no timezone and no daylight saving; it is the same number everywhere on Earth, which is exactly why databases, logs and APIs love it. All the timezone complexity only appears when a human needs to read it — that conversion is what this page does.
Seconds or milliseconds? How detection works
Unit mix-ups are the classic timestamp bug — a milliseconds value read as seconds lands you in the year 56,000-something. Detection here uses magnitude: today's date is a 10-digit number in seconds, 13 digits in milliseconds, 16 in microseconds, 19 in nanoseconds. Those ranges don't overlap for any modern date, so pasting any of them just works — the detected unit is always shown so you can sanity-check it.
Frequently asked questions
Is anything I paste sent anywhere?
No. Parsing and every conversion happen in your browser using its own timezone database. Nothing is stored or transmitted.
Why does my timestamp show a different hour than my server logs?
Your server probably logs in UTC (or its own zone) while this page shows your local time — both tiles are shown, and the city picker lets you check any other zone. The epoch number itself is identical everywhere; only the human formatting differs.
What is the ISO week number for?
Many industries plan by week numbers (W1–W53, ISO 8601 rules: weeks start Monday, week 1 contains the first Thursday of the year). The tile shows the week and its week-based year, which can differ from the calendar year around New Year.