Timestamp Converter
Epoch time ⇄ readable dates in any time zone, with daylight saving handled.
Current Unix time
— ms · —
Enter a Unix timestamp — seconds, milliseconds, microseconds or nanoseconds are recognised by their size — or a date in ISO 8601 or RFC 2822 format to get its timestamp.
Result
Date and time → Unix timestamp
Batch convert
Uses the unit and time zone chosen above. Up to 10,000 lines.
| Line | Input | Read as | Unix seconds | ISO 8601 (UTC) | Local time |
|---|
About the Timestamp Converter
A Unix timestamp is the number of seconds since 00:00:00 UTC on 1 January 1970 (the Unix epoch). Databases, APIs, log files and JWTs use it to store moments in time — often in milliseconds (JavaScript's Date.now(), Java's System.currentTimeMillis()) and sometimes in microseconds or nanoseconds (Python's time.time_ns(), Go's UnixNano()).
Paste a timestamp to see it as a local date, UTC, ISO 8601, RFC 2822 and a relative time such as "3 days ago" — the unit is recognised from the size of the number, and long nanosecond values keep every digit. You can also pick a date, time and time zone to get the timestamp: times skipped or repeated by daylight saving are detected and explained.
How to use it
- Paste a Unix timestamp — or a date such as
2023-11-14T22:13:20Z— into the box. The unit is detected automatically; choose it yourself if the guess is wrong. - Choose the time zone for local times. Your browser's time zone is selected at first.
- Copy any format with its Copy button. The clock at the top always shows the current timestamp in seconds and milliseconds.
- To go the other way, set a date and time under Date and time → Unix timestamp. For many values, paste one per line into Batch convert and download the results as CSV.
Examples
1700000000
ISO 8601 (UTC): 2023-11-14T22:13:20.000Z Asia/Kolkata: 2023-11-15T03:43:20.000+05:30 RFC 2822: Tue, 14 Nov 2023 22:13:20 +0000
1700000000123
2023-11-14T22:13:20.123Z (detected as milliseconds: 13 digits)
1 November 2026, 01:30 in America/New_York
First (EDT, UTC−04:00): 1793511000 Second (EST, UTC−05:00): 1793514600
US clocks go back from 02:00 to 01:00 that night, so 01:30 occurs twice. Most software uses the first one.
Common uses
- Reading
created_at,exporiatvalues in API responses, JWTs and database rows. - Checking what time a log line or a monitoring alert really happened in your own time zone.
- Getting the timestamp for a deadline or a scheduled job at a local time in another country.
- Converting a whole column of timestamps from a CSV export at once.
How the unit is detected
Today's timestamps have 10 digits in seconds, 13 in milliseconds, 16 in microseconds and 19 in nanoseconds. The converter reads values below 10¹¹ as seconds (enough until the year 5138), below 10¹⁴ as milliseconds, below 10¹⁷ as microseconds and anything larger as nanoseconds.
The guess can only be wrong for very old dates in a small unit: for example 99999999999 in milliseconds is 3 March 1973, but it is read as seconds (the year 5138). Choose the unit yourself in such cases, or add a suffix such as ms.
Which date format to use
- ISO 8601 / RFC 3339 (
2023-11-14T22:13:20Z) — the standard for JSON APIs, databases and logs. It sorts correctly as text. - RFC 2822 (
Tue, 14 Nov 2023 22:13:20 +0000) — the format of e-mailDate:headers and RSS feeds. - HTTP date (
Tue, 14 Nov 2023 22:13:20 GMT) — used by HTTP headers such asLast-ModifiedandExpires; always in GMT (RFC 9110). - Unix time — compact and time-zone free; store this (or ISO 8601 in UTC) and convert to local time only for display.
Leap seconds and the year 2038
Unix time treats every day as exactly 86,400 seconds, so leap seconds are not counted: a timestamp cannot represent 23:59:60. This keeps the arithmetic simple and is how POSIX defines it.
Systems that store timestamps as signed 32-bit integers stop at 2147483647, which is 03:14:07 UTC on 19 January 2038. One second later the value overflows. Paste 2147483647 above to see it; 64-bit timestamps do not have this problem.
Limitations
- Dates must lie within the range JavaScript supports: 20 April 271,822 BC to 13 September AD 275,760 (100 million days either side of 1970).
- Time-zone and daylight-saving rules come from your browser's built-in IANA time-zone database, so they are as current as your browser.
- Relative times are rounded to the largest whole unit; months count as 30.44 days and years as 365.2425 days.
- Only ISO 8601 and RFC 2822 dates are read. Ambiguous formats such as 03/04/2026 (March or April?) are not guessed.
Privacy
Everything happens in your browser. What you enter or open here is not uploaded or stored by MySmartCoPilot.
Frequently asked questions
What is a Unix timestamp?
The number of seconds that have passed since 1 January 1970 at 00:00:00 UTC, not counting leap seconds. Because it is the same everywhere in the world, it is a convenient way to store and compare moments in time.
Is my timestamp in seconds or milliseconds?
Count the digits: current dates have 10 digits in seconds and 13 in milliseconds. JavaScript, Java and many JSON APIs use milliseconds; Unix tools, PHP and most databases use seconds. The converter detects this for you and shows which unit it used.
Why is the date different in UTC and in my time zone?
A timestamp is one moment; the calendar date depends on where you are. 1700000000 is 22:13 on 14 November in London but already 03:43 on 15 November in India (UTC+05:30).
What happens with times skipped or repeated by daylight saving?
When clocks jump forward, some local times never happen; the converter says so and uses the time after the jump, as JavaScript and most calendars do. When clocks go back, an hour happens twice; both timestamps are shown.
Does it work for dates before 1970?
Yes. Earlier dates have negative timestamps, for example -86400 is 31 December 1969.
Is anything sent to a server?
No. Everything is calculated in your browser. The live clock uses your device's clock, so it is as accurate as your system time.