Unix Timestamp Converter
Convert epoch time to a date, and back again.
- 100% Free
- No Sign Up
- Works in Your Browser
Timestamp converter
Convert Unix epoch time to dates
More Developer Tools
View all tools- JSON to CSVTurn a JSON array into CSV
- CSV to JSONTurn CSV rows into JSON
- JSON to YAMLConvert JSON into YAML
- YAML to JSONConvert YAML into JSON
- JSON to XMLConvert JSON into XML
- JSON formatterPretty-print and indent JSON
- Base64 encode/decodeEncode and decode Base64 text
- JWT decoderDecode a JSON Web Token
- UUID generatorGenerate random v4 or time-ordered v7 UUIDs
Every everyday developer tool, right in your browser.
No installs. No uploads. No signup.
Browse all 36 tools- Developer tools
- 36
- Cheat sheets
- 10
- Bytes uploaded
- 0
How to use the timestamp converter
Three steps, all in your browser.
- 1
Enter a time
Paste a Unix timestamp, or pick a date to convert.
- 2
Check the options
Adjust the options if you need to. The conversion updates instantly.
- 3
Copy the result
Copy the output in one click. Nothing is saved or sent anywhere.
Unix Timestamp Converter: what to know
The timestamp converter turns a Unix timestamp into a readable date and time, in UTC, your own time zone or any other, and turns a date back into a timestamp. The unit is detected from the size of the number: seconds (10 digits for current dates), milliseconds (13), microseconds or nanoseconds. Results are shown as ISO 8601, RFC 2822 and relative time, such as '3 hours ago'.
Unix time counts the seconds since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. Because it's a single number that's the same everywhere at a given instant, it's the standard way to store times in databases, logs, JWTs (the exp and iat claims) and APIs, leaving time zones to display time. JavaScript's Date.now() and Java's System.currentTimeMillis() use milliseconds instead, a common source of off-by-1000 bugs.
ISO 8601 strings such as 2026-10-02T14:30:00Z are the text equivalent: the Z means UTC, while an offset such as +02:00 records the local time zone. Use ISO 8601 or Unix time in APIs, never ambiguous formats like 02/10/2026.
Popular uses
- Reading timestamps in logs, databases and API responses
- Checking a JWT's exp claim or a cache expiry
- Creating a timestamp for a test or a SQL query
- Converting event times between UTC and local time
Tips for the best result
- A date in January 1970 usually means seconds were read as milliseconds; a date tens of thousands of years ahead means the opposite.
- Store times in UTC and convert to the user's time zone only when displaying them.
- Signed 32-bit time runs out on 19 January 2038; make sure stored timestamps use 64-bit integers.
Read how JustYourDev works and our privacy details. Code, data and files you use here are processed in your browser and are never sent to our server.