Unix Timestamp Converter: Epoch Time to Date and Back
Part of Text tools: See all Text tools.
What is Timestamp Converter?
Convert Unix (epoch) timestamps to dates and dates to timestamps. Paste one timestamp or a list in seconds, milliseconds, microseconds or nanoseconds and see each moment in UTC and in the time zone you choose, as ISO 8601, RFC 2822, a readable date and a relative time. Or enter a date and clock time in any time zone to get the timestamp, with daylight-saving gaps and repeated hours called out.
How to use Timestamp Converter
- Paste a Unix timestamp, or several one per line, or press Use current time.
- Leave Unit on Detect from digit count or choose seconds, milliseconds, microseconds or nanoseconds yourself.
- Pick the time zone to show alongside UTC (your device zone is the default) and press Convert.
- To go the other way, pick a date and time, choose the time zone that clock time belongs to and press Get timestamp.
- Copy the ISO 8601, RFC 2822, seconds or milliseconds value you need from the results.
Why use this tool?
Timestamps in logs, databases, APIs and tokens are unreadable as raw numbers, and mixing up seconds and milliseconds or local and UTC time is one of the most common date bugs. This converter says which unit it assumed, shows UTC and local time side by side, and warns when a local time is skipped or happens twice because of daylight saving.
FAQ
- What is a Unix timestamp?
- It is the number of seconds since 00:00:00 UTC on 1 January 1970, the Unix epoch, not counting leap seconds. Many systems use milliseconds or finer units instead, counted from the same moment.
- How does it tell seconds from milliseconds?
- By the number of digits: up to 11 digits are read as seconds, 12 to 14 as milliseconds, 15 to 17 as microseconds and 18 or 19 as nanoseconds. The result always says which unit was assumed, and you can override it with the Unit menu.
- Can I convert several timestamps at once?
- Yes. Paste up to 500, one per line. You get a table with the unit, the UTC time and the time in your chosen zone for each line, and any line it cannot read is marked with the reason.
- Which time zones are available?
- Every IANA time zone your browser knows, such as America/New_York, Europe/London or Asia/Kolkata, plus UTC and your device's own zone. Daylight saving and historical offsets come from that database.
- What happens with times skipped or repeated by daylight saving?
- If the clock time you enter never happened, for example 02:30 on the day clocks jump forward, the tool says so instead of shifting it. If it happened twice, when clocks go back, it shows both timestamps.
- Does it handle dates before 1970?
- Yes. Negative timestamps count backwards from the epoch, so -86400 is 31 December 1969 at 00:00 UTC. You can also turn a pre-1970 date into a negative timestamp.
- Is my data sent anywhere?
- No. The conversion runs in your browser and nothing you type is sent to our server or stored.
What this Unix timestamp converter does
A Unix timestamp is a count of time since the Unix epoch, which is 00:00:00 UTC on 1 January 1970. Logs, databases, APIs, JWT tokens, cookies and file systems all store moments this way because a single number is easy to sort, compare and send between systems. The catch is that nobody can read 1767225600 at a glance. This converter does the translation both ways. Paste a timestamp and it shows the moment in UTC and in any time zone you pick, in ISO 8601, in the RFC 2822 style used by email headers, as a readable date, and as "3 days ago" or "in 2 hours". Or pick a date and a clock time, say which time zone that clock time belongs to, and it gives you the timestamp in seconds and milliseconds.
It also handles the cases that usually cause bugs: timestamps in milliseconds, microseconds or nanoseconds, negative timestamps for dates before 1970, lists of many timestamps pasted from a log, and local clock times that are skipped or repeated when daylight saving starts or ends. Everything runs in your browser using its built-in time zone database.
Seconds, milliseconds, microseconds or nanoseconds?
The classic Unix timestamp counts seconds. JavaScript's Date.now(), Java's System.currentTimeMillis() and many web APIs count milliseconds. Python's time.time_ns(), Go's UnixNano() and some databases and tracing tools use nanoseconds, and others use microseconds. The same moment therefore shows up with 10, 13, 16 or 19 digits. For dates between September 2001 and November 2286 a seconds timestamp has exactly 10 digits, so the digit count is a reliable clue for modern dates.
With the Unit menu on "Detect from digit count", the tool reads up to 11 digits as seconds, 12 to 14 digits as milliseconds, 15 to 17 as microseconds and 18 or 19 as nanoseconds, and it always tells you which one it assumed. If that guess is wrong, for example a 12-digit number that really is seconds in the far future, pick the unit yourself. A quick sanity check: if a millisecond value gives a date in January 1970, you almost certainly fed it seconds by mistake, and if a seconds value lands tens of thousands of years from now, it was milliseconds or finer.
Dates are shown to the millisecond. If you paste microseconds or nanoseconds, the finer digits are not thrown away silently: the result names them in a precision note so you know they existed. Seconds may include a decimal part, such as 1700000000.5, which is the style Python's time.time() prints.
Reading the results
For a single timestamp you get a small table. UTC (ISO 8601) is the unambiguous form most APIs expect, ending in Z for UTC, for example 2026-01-01T00:00:00Z. UTC (RFC 2822) is the format used in email Date headers and HTTP, such as Thu, 01 Jan 1970 00:00:00 +0000. The two rows for your chosen zone show the same instant as a wall-clock time there, once as ISO 8601 with the UTC offset (2026-01-01T05:30:00+05:30 for India) and once in readable form with the weekday. Relative to now counts whole years, months, days, hours, minutes or seconds from your device clock, using an average month length, so treat it as a rough guide. The last rows repeat the moment in plain seconds and milliseconds so you can copy whichever your code needs.
Paste several timestamps, one per line, and the tool switches to a compact table with the input, the unit it used, the UTC time and the time in your chosen zone. Lines it cannot read are marked in place with the reason, so one bad value does not stop the rest. Up to 500 lines are converted at once. Spaces, commas and underscores used as digit separators are ignored.
Converting a date and time to a timestamp
A clock time on its own is not a moment. 09:00 on a given day happens at different instants in London, New York and Sydney. That is why the second section asks which time zone your date and time belongs to. Choose "Your device time zone", UTC, or any named zone such as America/New_York or Europe/Berlin, and the tool finds the instant when clocks there showed that time. You can enter seconds as well as hours and minutes.
Daylight saving makes this harder twice a year. When clocks jump forward, a range of clock times never happens. In New York, 02:30 on 8 March 2026 does not exist because clocks went from 01:59:59 straight to 03:00:00. The tool tells you so instead of quietly shifting the time. When clocks go back, an hour happens twice. In New York, 01:30 on 1 November 2026 occurs first at UTC-4 and again an hour later at UTC-5, so the tool shows both timestamps: 1793511000 and 1793514600. Many converters silently pick one, which is a common source of off-by-one-hour bugs in schedules and billing.
Worked examples
- 1767225600 read as seconds is 2026-01-01T00:00:00Z. In Asia/Kolkata that is 2026-01-01T05:30:00+05:30, and in America/New_York it is still Wednesday 31 December 2025 at 19:00.
- 1767225600000 has 13 digits, so it is read as milliseconds and gives the same instant. Force the unit to Milliseconds on the 10-digit version instead and you get 21 January 1970, the classic sign of a unit mix-up.
- 1767225600123456789 has 19 digits, so it is read as nanoseconds: 2026-01-01T00:00:00.123Z, with the extra digits 456789 named in the precision note.
- -86400 is one day before the epoch: 1969-12-31T00:00:00Z. Negative timestamps are valid and are how many systems store birthdays and historical dates.
- 2147483647, the largest value a signed 32-bit integer can hold, is 2038-01-19T03:14:07Z. Software that still stores time in 32 bits will overflow one second later, which is the "year 2038 problem".
- 18:07:00 on 10 November 2026 in Asia/Kolkata converts to 1794314220 seconds, which is 12:37:00 UTC.
Time zones and daylight saving rules
The zone list comes from your browser, which ships the IANA time zone database used by operating systems and most programming languages. It knows the current and historical offsets and daylight saving rules for each region, including half-hour and 45-minute offsets such as India, Nepal and parts of Australia. Results for future dates use today's rules, and governments do change them, sometimes with little notice, so a far-future local time is a best estimate. Before standard time zones existed, places used local mean time based on the sun, which is why very old dates can show odd offsets such as +05:21:10 for Kolkata in 1900. That is correct historical data, not a bug.
Leap seconds and range
Unix time pretends every day has exactly 86,400 seconds. The 27 leap seconds added to UTC since 1972 are not counted, which is how POSIX defines it and how practically every computer, database and browser behaves, so the tool follows the same rule. JavaScript dates, which the tool uses, reach about 275,760 years either side of 1970, far beyond anything you will meet in a log file. The tool uses the proleptic Gregorian calendar throughout, so dates before the calendar reform of 1582 are shown in Gregorian form, as in ISO 8601.
What it does not do
It does not parse free-text dates such as "next Tuesday" or "3 Jan 26", because those are ambiguous between countries. Use the date and time picker instead. It does not convert to calendars other than the Gregorian one, and it does not read timestamps from other epochs, such as Windows FILETIME (1601), .NET ticks, Excel serial dates or GPS time. Those need a different offset first. It reads only plain numbers, so to convert a date written as text in a log, copy the timestamp field rather than the whole line.
Privacy
The timestamps and dates you enter stay in your browser. The page does not send them to our server or save them. Closing or refreshing the tab clears them, which makes it safe to paste values from production logs.
Related tools
To compare clock times across several cities for a meeting, use the time zone converter. To count the days, weeks or working days between two dates, try the date difference calculator. For scheduled jobs, the cron expression generator builds and explains cron schedules.
Also try
Related tools that work well with this one: