How does auto-detection choose the timestamp unit?
Auto-detection uses the number of digits to infer seconds, milliseconds, microseconds, or nanoseconds. You can force a unit when you know the source system.
Convert timestamps while debugging time data
Unix timestamps appear in logs, queues, analytics exports, cache records, scheduled jobs, API payloads, JWT claims, and database rows. This converter accepts common timestamp units and displays the matching date in local time, UTC, ISO 8601, and a selected time zone.
The reverse converter creates timestamp values from a date and IANA time zone for tests, fixtures, API examples, and manual operations.
What the timestamp converter includes
- Convert seconds, milliseconds, microseconds, and nanoseconds into readable dates.
- Auto-detect timestamp precision from the input length.
- Show local time, selected time zone, UTC, ISO 8601, weekday, and relative time.
- Convert a time-zone-aware date back into copy-ready timestamp values.
Loading tool...
Avoid timestamp unit mistakes
The most common timestamp issue is using the wrong unit. Backend systems often use seconds, JavaScript uses milliseconds, and some databases expose microseconds or nanoseconds. Choose the unit explicitly when precision matters.
Unix timestamp converter FAQ
Why do timestamp units matter?
JavaScript Date uses milliseconds, while many APIs and databases use seconds or microseconds. Unit mismatches are a common cause of dates near 1970 or far in the future.
Can I convert a date back to a timestamp?
Yes. Enter a date and time with a time zone to generate seconds, milliseconds, microseconds, nanoseconds, and ISO 8601 output.
