How to use it
- Enter a timestamp or a date.
- See ISO, UTC, and local values instantly.
- Copy the value you need.
Why use it
- Convert epoch to date in one step.
- Handle seconds and milliseconds automatically.
- Debug logs and API data quickly.
- See UTC and local time together.
- Free and works on any device.
What is a Unix timestamp?
A Unix timestamp (or epoch time) counts the number of seconds that have elapsed sinceJanuary 1, 1970, 00:00:00 UTC: the Unix epoch. Because it is timezone-neutral and easy to compare, it is the standard way systems record dates.
When you see a number in a log or API response, it is almost always a Unix timestamp. Converting it to a readable date is essential for debugging, and this converter shows the value in seconds, milliseconds, ISO 8601, UTC, and your local timezone so you can interpret any of the common forms.
Seconds vs. milliseconds
Different systems store timestamps in different units, and mismatching them is one of the most common date bugs in software:
- Seconds (10 digits): used by most Unix-based systems, logs, and many APIs (for example
1693670400). - Milliseconds (13 digits): used by JavaScript's
Date.now(), databases like MongoDB, and many web stacks (for example1693670400000).
This converter lets you explicitly choose the unit, so you never have to guess whether a value is in seconds or milliseconds again.
Creating timestamps in common languages
| Language | Current timestamp (ms) | Current timestamp (s) |
|---|---|---|
| JavaScript | Date.now() | Math.floor(Date.now()/1000) |
| Python | int(time.time()*1000) | int(time.time()) |
| Bash | date +%s%3N | date +%s |
| Go | time.Now().UnixMilli() | time.Now().Unix() |
Use the "Current time" mode in this tool to grab the exact current epoch value for any of these languages, then copy it straight into your code or logs.