Unix Timestamp Generator
The current epoch time in seconds and milliseconds, updating every second.
Convert Unix timestamps to dates and dates back to timestamps.
Seconds and milliseconds are both detected automatically.
A Unix timestamp counts the seconds that have passed since the first moment of 1 January 1970 in UTC. Databases, log files and APIs store time this way because a single integer is unambiguous, sorts correctly and carries no timezone confusion. The cost is that a raw timestamp means nothing to a human reading it.
This converter works in both directions. Paste a timestamp to see it as a readable date in your local timezone and in UTC, alongside the ISO 8601 form that most APIs expect. Or pick a date and time to get the matching timestamp in both seconds and milliseconds.
The tool detects automatically whether a pasted number is in seconds or milliseconds, which removes the most common source of error: a value that is a thousand times too large lands in the year 56000 rather than next Tuesday. It also shows how long ago or how far ahead the moment is, which is often the thing you actually wanted to know.
The timestamp converter is used by writers, developers, students, marketers and anyone else who needs the job done once without installing software. Common cases include:
By magnitude. A ten-digit value lands in a sensible range when read as seconds, while a thirteen-digit value only makes sense as milliseconds. The detected unit is shown so you can override it if a value is unusual.
Local time is adjusted by your device's timezone offset, including daylight saving if it applies on that date. Both are shown because logs are usually in UTC while people think in local time.
It is the international standard for writing dates and times, such as 2026-10-06T11:30:00Z. Most APIs accept it, it sorts correctly as plain text, and it leaves no ambiguity about day and month order.
Yes. Timestamps before the epoch are negative numbers, and both directions handle them correctly.
No. Unix time deliberately ignores leap seconds, as do browsers and almost every database. For everyday application work this is the behaviour you want.
No. All conversion uses your browser's own date functions, and your device clock provides the current time.
If the timestamp converter is not quite what you need, these other free tools solve closely related problems.
The current epoch time in seconds and milliseconds, updating every second.
Enter a date of birth to get an exact age plus total months, weeks and days.
Pretty-print and validate JSON, with the exact line and column of any error.
Split a URL into every component, including a table of query parameters.
Strip whitespace from JSON and compare original and minified sizes.