Unix timestamp converter
Developers, testers and data analysts meet Unix timestamps everywhere — API responses, database rows, log files and JWT tokens. This epoch converter turns a timestamp into a readable date inIST, UTC and your own time zone, with ISO 8601 output and a “how long ago” hint. It works the other way too: pick a date and time to get the timestamp in seconds and milliseconds. Seconds, milliseconds, microseconds and nanoseconds are detected automatically.
How to use it
- Paste a timestamp to see it as a date — or tap the live timestamp to copy it.
- To go the other way, choose a date, time and zone.
Example
The timestamp 1791417600 is 8 October 2026, 5:30:00 am IST (00:00:00 UTC on 8 October 2026). As milliseconds it would be written 1791417600000. Formatting JSON from an API? Try the developer tools, or convert time zones for humans with the time zone converter.
Frequently asked questions
What is a Unix timestamp?
The number of seconds since 00:00:00 UTC on 1 January 1970 (the “Unix epoch”), ignoring leap seconds. It is how most computers, databases and APIs store points in time, because it is a single number with no time zone.
Seconds or milliseconds?
Unix time is traditionally in seconds (10 digits today, like 1791417600). JavaScript and many APIs use milliseconds (13 digits). The converter detects seconds, milliseconds, microseconds and nanoseconds automatically from the size of the number.
What is the Year 2038 problem?
Systems that store Unix time as a signed 32-bit number overflow at 03:14:07 UTC on 19 January 2038 (timestamp 2147483647). Modern 64-bit systems are not affected.
How do I get the current timestamp in code?
JavaScript: Math.floor(Date.now() / 1000). Python: int(time.time()). PHP: time(). MySQL: UNIX_TIMESTAMP(). Linux shell: date +%s.