Timestamp Converter
Paste any date or Unix timestamp and read it in your time, in every format and zone.
Runs fully in your browser. Nothing you paste here is sent anywhere.PrivateYour date
What it means
About this tool
Paste the date exactly as you found it. You do not need to know what format it is in, what unit it uses or which time zone it was written in: the tool works that out, tells you how it read it, and shows the moment in your local time with a plain "3 hours ago" next to it. Below that, the same instant is written out in every format you might need to paste somewhere else — ISO 8601, RFC 2822, HTTP date, SQL, Unix seconds, milliseconds, microseconds and nanoseconds, Excel serial, .NET ticks — each with its own copy button, and a table of what time it is in the main cities of the world.
It reads Unix epochs in any unit, ISO 8601 and RFC 3339 in all their spellings (with Z, an offset, a bracketed region or an abbreviation such as CEST), RFC 2822 and HTTP headers, what JavaScript and Java print for a Date, Apache and syslog lines, Postgres timestamps with microseconds, dates written in English or Spanish with month names, slashed dates, compact YYYYMMDD, spreadsheet serials, .NET ticks and Windows FILETIME, and the creation time hidden inside a MongoDB ObjectId, a ULID, a version 1 or 7 UUID or a Twitter or Discord snowflake. When the date is wrapped in a JSON line, a log line or quotes, the relevant part is picked out for you.
Every guess is shown, never hidden. A timestamp that carries no zone is read in the zone selected in the toolbar, and the panel says so; a number’s unit is inferred from its length, and the other believable readings are listed one click away; a date like 01/02/2026 is read in your locale’s order with the other order offered beside it; an ambiguous abbreviation such as CST or IST is flagged. If the input cannot be read at all, the tool says so instead of showing a wrong date.
Nothing you paste is transmitted. The page is static HTML and both the parsing and the time zone arithmetic run in your tab on the zone data your browser already ships, so it is safe for timestamps from production logs, tokens and database rows.
Frequently asked questions
Is my data uploaded to a server?
No. The converter is plain JavaScript running in your browser. There is no backend endpoint, so nothing you paste leaves your device — you can disconnect from the network and it still works.
The date I pasted has no time zone. Which one is used?
The one selected under "No zone in the input? Read it as" in the toolbar. It starts on UTC because that is what most servers, databases and logs store, and the panel on the left always says when the zone was assumed rather than read. If the source system uses another zone, pick it there and everything updates.
How does it know whether a number is seconds or milliseconds?
From its length: up to ten or eleven digits is seconds, thirteen is milliseconds, sixteen microseconds and nineteen nanoseconds. Eight digits that form a valid calendar date, such as 20260919, are read as that date. Every other unit that would land somewhere between 1980 and 2100 is listed under "It could also be", and clicking one switches the reading.
Why does 01/02/2026 show two readings?
Because both fields fit a month. The English site reads month first (2 January) and the Spanish site day first (1 February), and the other order is offered right below so you can pick the one your source uses. When one field is bigger than 12 there is no ambiguity and only one reading is shown.
Does it remember my time zone?
Yes. The zone used for inputs without one, the zone the result is shown in, and the list of cities in the comparison table are saved in your browser’s local storage under the key timestamp-converter, so they are there the next time you open the page. They stay on your device, are never sent anywhere, and clearing site data removes them. Choosing "Local" keeps following your device’s zone rather than pinning the one you had when you chose it.
What does it not read yet?
Durations and relative phrases such as "2 hours ago" or "next Friday", dates before the year 1 or in non-Gregorian calendars, and month names in languages other than English and Spanish. Times with leap seconds (23:59:60) are reported as invalid rather than rounded.
Is it really free?
Yes, with no account and no usage limit. The site is funded by ads placed around the tool, never inside your working area.