What a Unix timestamp is
It counts seconds since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. Because it has no time zone, the same timestamp is the same instant everywhere; only the displayed clock time changes between zones.
Convert Unix timestamps, the seconds-since-1970 numbers used in logs, databases and APIs, into readable dates, and dates back into timestamps. Paste a 10-digit seconds value or a 13-digit milliseconds value and see the date in India Standard Time and UTC. Or pick a date and time, say which time zone it is in, and get the timestamp.
Calculator
Seconds and milliseconds are detected automatically from the size of the number.
The date appears in IST and as an ISO date in UTC.
Choose a date, time and zone to get the timestamp in seconds and milliseconds.
Timestamps and calendar dates answer different questions.
| Option | Best for | Trade-off |
|---|---|---|
| Epoch Timestamp Converter (this page) | Reading and creating Unix timestamps. | One value at a time. |
| Date Difference Calculator | Days between two calendar dates. | No timestamps or times of day. |
| JSON Formatter | Reading API responses that contain timestamps. | Does not convert them. |
| UUID Generator | Unique IDs for records. | Not time-based. |
| A spreadsheet | Converting thousands of timestamps at once. | Needs formulas. |
A log line shows the timestamp 1700000000 and you need the IST time.
Use it while debugging, reading logs, writing database queries or checking when a token or link expires. Support teams can translate a timestamp from a log into a local IST time for a customer.
It counts seconds since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. Because it has no time zone, the same timestamp is the same instant everywhere; only the displayed clock time changes between zones.
Unix tools and many databases use seconds; JavaScript and Java often use milliseconds. A 13-digit value is almost always milliseconds. The converter decides by size, and tells you which unit it used.
A date and time on its own is ambiguous until you say which zone it is in. 09:30 in India is 04:00 in UTC, so choosing the zone avoids an error of five and a half hours.
Spreadsheets store dates as day counts, not Unix timestamps. To convert a column of timestamps, use this page to check a few values by hand, then apply the matching formula in your spreadsheet so you can confirm it gives the same dates.
Older systems stored Unix time in a signed 32-bit number, which runs out on 19 January 2038. Modern systems and JavaScript use 64-bit values, so the limit does not apply here, but it is worth checking when you work with old databases or embedded devices.
JavaScript’s Date.now() returns milliseconds since 1970, so values from browser logs and many APIs have 13 digits. Unix command-line tools and many databases use seconds. Mixing the two is a common bug that puts dates in 1970 or far in the future.
India has no daylight saving. For “this device’s time zone”, your browser applies its own rules.
No, one value at a time.
No. Conversion happens in your browser.
Current timestamps in seconds have 10 digits; in milliseconds they have 13. The converter treats numbers of 100 billion or more as milliseconds.
Both IST (Asia/Kolkata, UTC+5:30) and UTC are shown, so you can match either.
Yes. Negative values are dates before 1 January 1970.
Timestamps from your logs are converted locally, so internal data in them stays on your machine.