Development
Unix Timestamp Converter
Convert Unix timestamps to date and time – and dates back to timestamps. The unit is detected automatically, time zones and daylight saving time are taken into account. Plus: whole lists at once and ready-made code examples for ten languages.
- Runs entirely in your browser
- No data upload
- No sign-up
- Free
Current Unix timestamp
Milliseconds: –
Timestamp → date
Date → timestamp
Convert many at once one value per line – timestamps and dates mixed
How to do it in code with the value from above
Guide
How it works
- Paste a timestamp
Paste a Unix timestamp at the top left. The tool detects from the length whether it is seconds, milliseconds, microseconds or nanoseconds – but you can also choose the unit yourself, as well as Excel, Windows and .NET values.
- Or enter a date
On the right, enter a date – e.g. 2026-10-12 14:30, Oct 12, 2026 14:30, 2026-10-12T14:30:00Z, an HTTP date or a line from the Apache log – or pick it in the calendar.
- Choose a time zone
The default is your device’s time zone. It determines how dates are displayed and how a date without a time zone is read. Daylight saving time and clock changes are taken into account.
- Use the result
Every value can be copied with a click. Below, you can convert whole lists at once and find code examples for PHP, JavaScript, Python, SQL and more.
FAQ
Frequently asked questions
What is a Unix timestamp?
A Unix timestamp (also Unix time, epoch time or POSIX time) counts the seconds since January 1, 1970, 00:00:00 UTC. Because it is just a number and contains no time zone, it is well suited for storing and comparing points in time – e.g. in databases, log files or APIs.
Seconds or milliseconds?
PHP, Python, MySQL and most server systems use seconds (10 digits), JavaScript and Java use milliseconds (13 digits). Some databases and programs use microseconds (16 digits) or nanoseconds (19 digits). The tool detects the unit from the length; for very old or far-future dates, better choose it yourself.
Does a timestamp have a time zone?
No. A timestamp describes the same moment everywhere in the world. Only when it is displayed as a date does a time zone come into play: 1760000000 is 10:53 in Berlin and 04:53 in New York – but the same moment.
What happens when the clocks change?
When the clock springs forward in spring, one hour does not exist (in the US, e.g. 02:00–02:59). In fall, one hour exists twice. The tool points this out: a nonexistent time is shifted forward as in JavaScript and PHP; for a duplicate time, the first one is used and the second one is shown as well.
What is the year 2038 problem?
If a timestamp is stored as a signed 32-bit integer, it ends on January 19, 2038 at 03:14:07 UTC (2,147,483,647). After that, the value jumps into the negative, i.e. to the year 1901. Modern systems use 64 bits; however, the problem still lurks in old database fields (e.g. MySQL TIMESTAMP) or embedded devices. The tool warns about such values.
What about leap seconds?
Unix time ignores leap seconds: every day has exactly 86,400 seconds. An input such as 23:59:60 is therefore counted as the first second of the next minute.
Which date formats does the tool understand?
ISO 8601 (also with time zone and fractions of a second), month names such as Oct 12, 2026 or 12 October 2026, the German notation 12.10.2026, RFC 2822 and HTTP dates, the output of JavaScript Date and the date command, as well as timestamps from Apache and nginx logs. It deliberately rejects notations such as 10/12/2026 because it is unclear whether October 12 or December 10 is meant.
Is my input stored?
No. Everything is calculated locally in your browser; the server learns nothing about it.