Unix Timestamp Converter
Convert Unix epoch time to IST, UTC and ISO dates, and dates back to timestamps
Timestamp → date
Date → timestamp
Runs entirely in your browser. Nothing you type or upload is sent to us or stored.
Results are for general guidance. Please check anything important before relying on it. Terms of use
How to Use
- The top box shows the current Unix timestamp in seconds and milliseconds, updating every second. Tap the copy icon to copy either.
- Under Timestamp → date, paste a timestamp. The unit (seconds, ms, µs or ns) is detected from its length, or you can pick it.
- You'll see the date in IST, UTC and your own time zone, plus ISO 8601 and how long ago it was. Each row has a copy button.
- Under Date → timestamp, pick a date and time, say whether it's in IST, UTC or your time zone, and copy the timestamp.
What is a Unix timestamp?
A Unix timestamp (also called epoch time or POSIX time) is the number of seconds since 1 January 1970, 00:00:00 UTC, a moment known as the Unix epoch. It's a single number with no time zone, so 1791786600 means the same instant everywhere in the world. Databases, server logs, APIs, JWT tokens and mobile apps store time this way. It takes little space, sorts easily and avoids time-zone mix-ups. This timestamp converter turns it into a readable date, and back.
Converting to Indian time
India uses a single time zone, Indian Standard Time (IST), which is UTC + 5 hours 30 minutes all year with no daylight saving. To convert:
IST date = UTC date + 5 h 30 min
1791786600 → 12 Oct 2026, 06:30:00 UTC → 12 Oct 2026, 12:00:00 IST
Because of that offset, timestamp 0 was 1 January 1970, 05:30 IST, not midnight. A common bug in Indian apps is a date that's 5½ hours off. That almost always means a UTC time was shown as if it were IST, or the other way round.
Seconds, milliseconds, microseconds, nanoseconds
Different languages count in different units. The tool guesses the unit from the number of digits:
| Unit | Digits today | Example (12 Oct 2026, 12:00 IST) | Common in |
|---|---|---|---|
| Seconds | 10 | 1791786600 | Unix, PHP time(), Python time.time(), MySQL UNIX_TIMESTAMP(), JWT |
| Milliseconds | 13 | 1791786600000 | JavaScript Date.now(), Java System.currentTimeMillis() |
| Microseconds | 16 | 1791786600000000 | PostgreSQL timestamp resolution, Python datetime precision |
| Nanoseconds | 19 | 1791786600000000000 | Go time.Now().UnixNano(), Python time.time_ns() |
If the detected unit looks wrong, for example a very old date in a test fixture, choose the unit yourself with the buttons.
Useful timestamps
| Timestamp (s) | UTC | IST |
|---|---|---|
| 0 | 1 Jan 1970, 00:00:00 | 1 Jan 1970, 05:30:00 |
| 1000000000 | 9 Sep 2001, 01:46:40 | 9 Sep 2001, 07:16:40 |
| 2000000000 | 18 May 2033, 03:33:20 | 18 May 2033, 09:03:20 |
| 2147483647 | 19 Jan 2038, 03:14:07 | 19 Jan 2038, 08:44:07 |
The last row is the Year 2038 problem: 2147483647 is the largest value a signed 32-bit integer can hold. Systems that still store time in 32 bits will overflow one second later. Modern operating systems and databases use 64-bit time, but old embedded devices and legacy database columns may not.
ISO 8601
ISO 8601 is the standard text format for dates, used by most JSON APIs: 2026-10-12T06:30:00.000Z (the Z means UTC) or 2026-10-12T12:00:00.000+05:30 for the same instant written in IST. The tool shows both. Always include the offset or Z, because a time without one is ambiguous.
Tips
- Store and send timestamps in UTC, and convert to IST only when showing them to people.
- Unix time ignores leap seconds, so every day is exactly 86,400 seconds.
- Negative timestamps are dates before 1970. The tool handles them too.