Convert Unix timestamps in seconds, milliseconds or microseconds into UTC, local and ISO dates, or pick a date and read its timestamp. A live panel shows the current time ticking every second.
Your files are processed in your browser, on your own device. Nothing is uploaded to a server.
A Timestamp Converter turns a Unix timestamp into a date you can read, and turns a date back into a timestamp in your browser. ToolPeko reads seconds, milliseconds and microseconds, then shows the moment in UTC, your local time and ISO format, with nothing uploaded.
Paste a number and the converter works out the unit from its length, then prints the date in UTC and your local time, next to an ISO line and a relative reading. You can also start from a date you type or pick.
Negative numbers work. A timestamp below zero is a moment before 1 January 1970, and this converter reads it the same way it reads a modern one. The relative reading points the right way, so a future time says how long from now instead of how long ago.
Logs and API answers are full of bare numbers. A database column holds 1761840000, a token carries an expiry as a long integer, and neither means anything at a glance. Paste the number here and you know the moment it names: UTC for the record, your local time for your head.
Debugging expiry is the sharpest case. A session set for a day ends in an hour, or a cache header points at a date from last year. Converting the stamp takes ten seconds and settles whether the bug sits in the value itself or in the code that reads it. Support teams use the same trick on events a customer system stored only as a number.
Planning across time zones is the third regular use. A launch, a migration window or a cron job set in UTC has to land at a sane local hour. The UTC row and the local row side by side end the mental arithmetic, and the live panel gives you the current stamp when a query asks for now.
The unit comes from the digit length, and that is a reading, not a fact. Ten digits is read as seconds, thirteen as milliseconds, sixteen as microseconds. If the number you paste was built in a unit its length does not give away, the date can land far from the one you meant.
JavaScript dates carry a hard range, roughly the years 271821 BC to 275760 AD. A stamp outside that range has no date to show, and the honest answer is an out of range note rather than a made-up date. Unix time leaves leap seconds out, so a Unix reading can sit a few seconds away from atomic clock time. That gap is part of the format, not an error on this page.
The local row follows your own device. It renders with the clock and the time zone settings of your machine, so a device with a wrong clock gives a local row that matches the wrong clock. The UTC row comes straight from the number. A schedule is easier to check against a server in another zone with our Cron Parser.
Every conversion runs in your browser. The numbers and dates you enter are not sent to a server, not stored by ToolPeko and not read by anyone here, the right setup for stamps from private logs. There is no account, no daily cap, and the only file that leaves the page is the .txt you choose to download.
It reads the length. Ten digits is taken as seconds, thirteen as milliseconds and sixteen as microseconds. If a result looks wrong, the stamp was likely built in a different unit than its length suggests, so count the digits first.
It shows the current time as a Unix timestamp in seconds and in milliseconds, updating once a second from your device clock. It is the quickest way to grab a now value for a query or a log note.
Yes. Type a date or pick one in the date and time picker, and the page shows that moment as a timestamp alongside its UTC and local readings. Dates before 1970 work too and produce negative timestamps.
Almost always a unit mix-up. A millisecond value read as seconds lands tens of thousands of years in the future, and a second value read as milliseconds lands near 1970. Check the digit count against its unit.
Yes. Unix timestamps go negative before 1 January 1970, and this converter reads them, showing the UTC and local date with a relative reading pointing into the past.
No. The conversion runs in your browser and nothing is sent to or stored on a ToolPeko server. The .txt file is created on your device and downloads only when you ask for it.
Same rules as this one: free, in your browser, with nothing uploaded.
Paste messy JSON, get it neat and valid.
Format messy PHP to clean PSR-12, in your browser.
Check JSON and find the exact line that breaks it.
Squeeze JSON down to one tight line.
Open JSON as a tree you can fold and explore.
JSON rows turned into a CSV a spreadsheet can open.
A CSV file turned into clean JSON objects.
JSON rewritten as YAML for config files.