Tip: 10 digits = seconds, 13 digits = milliseconds. You can also
suffix s or ms.
Uses your local timezone (your browser's).
Share links via ?e= (epoch) or ?d=
(datetime-local).
Results
Copy buttons are per-result. URL updates happen without reloading the page.
Learn more
Need deeper context? Read the Epoch Time Guide and the ISO 8601 Guide for format comparisons and troubleshooting tips.
What this tool does
Converts Unix epoch timestamps into human-readable dates - and back again - without guesswork. It's built for quickly sanity-checking logs, API payloads, database records, and anything else that decided to express time as a large integer.
Shareable links mean you can send a timestamp to someone else and know they'll see the same result.
How it works
- Enter a Unix timestamp (seconds or milliseconds - auto-detected).
- Or pick a local date and time using the browser's timezone.
- The tool converts instantly in both directions.
- Use Now to grab the current timestamp.
- Copy individual results or share the page URL with embedded values.
Common use cases
- Checking application log timestamps during incident response.
- Verifying API request and response times.
- Inspecting database event records.
- Comparing server-generated times against local time.
- Debugging "why did this happen at 3am?" moments.
FAQ
Seconds or milliseconds - how does it know?
10 digits = seconds. 13 digits = milliseconds. You can also suffix s or ms manually.
Which timezone does the date use?
Your browser's local timezone. No surprises.
Can I share a specific conversion?
Yes. The URL updates automatically so you can paste it into chat or tickets.
Does it handle dates before 1970?
Yes. Negative epoch values are supported.