Timestamp Converter

Paste a Unix timestamp in the box above and it turns into a readable date at once: in the time zone you choose, in your own zone, as ISO 8601, RFC 2822 and relative time, plus the same moment as an Excel serial, a Windows FILETIME and more. The number can be in seconds, milliseconds, microseconds or nanoseconds; the timestamp converter works out which from the number of digits.

It also goes the other way. Type a date and a time zone and you get the timestamp back, with summer time handled. Above everything, the current Unix timestamp ticks live, ready to copy.

This timestamp converter runs entirely in your browser with its built-in time-zone database. Nothing you type is sent anywhere.

A Unix timestamp, also called epoch time or POSIX time, is the number of seconds since the Unix epoch: 00:00:00 UTC on 1 January 1970. Today that count is a ten-digit number of almost 1.8 billion, and it goes up by one every second, everywhere on Earth at the same moment.

Because it is a single number with no time zone, no calendar and no date format, it is easy to store, sort, compare and send between systems. Databases, log files, APIs, JSON payloads, cookies and JWT tokens all use it. The cost is that people cannot read it, which is what a converter is for.

Times before 1970 are simply negative. -86400 is one day before the epoch, 31 December 1969, and the timestamp converter accepts the minus sign.

Most mistakes with timestamps come from the unit, not the date. A unix timestamp converter that guesses wrong shows a date in 1970 or thousands of years from now. With Unit on Auto, this page counts the digits: up to 11 digits are read as seconds, 12 to 14 as milliseconds, 15 to 17 as microseconds and 18 or more as nanoseconds. A short line such as Read as milliseconds shows what it chose.

If the guess is wrong, for example for an old date in milliseconds that has fewer digits, pick s, ms, µs or ns yourself. A minus sign is allowed for dates before 1970 and a decimal point for fractions of a second. Spaces, commas and underscores used as digit separators are ignored.

Anything else, such as letters, shows a short message instead of a wrong date. The timestamp converter handles about 270,000 years either side of 1970, the same range as JavaScript dates.

The same moment can be written four ways. Unix itself counts seconds, but JavaScript's Date.now(), Java's System.currentTimeMillis() and many APIs return milliseconds, three digits longer. Python's time.time_ns(), Go's UnixNano and tracing tools go down to nanoseconds.

As a timestamp converter in milliseconds and smaller units, the output lists the moment in all four: Seconds, Milliseconds, Microseconds and Nanoseconds, each with a Copy button. These rows are exact to the millisecond; digits below that are rounded, because browsers keep times in milliseconds.

Once the number is read, the table under the box converts the unix timestamp to date and time in every common format at once. Here is each row for 1761043200 with UTC chosen:

The Day row uses ISO weeks, which start on Monday. Week 1 is the week with the first Thursday of the year, so 30 December can belong to week 1 of the next year; the row then names that year. The chat tags work in apps that read the <t:…> format, Discord being the best known: R shows relative time, F the full date and time, d a short date, each in the reader's own zone.

A timestamp is the same everywhere; only the wall-clock time differs. Choose any IANA zone under Show in, such as America/New_York, Europe/Berlin or Asia/Kolkata, and the readable date, ISO 8601, RFC 2822, Day and Excel rows switch to that zone. Your own zone is listed near the top, marked (yours).

A timestamp converter with timezone support matters because of summer time. New York is UTC-5 in winter and UTC-4 in summer, London switches between GMT and BST, and the dates of the change differ by country. The timestamp converter uses your browser's built-in time-zone database (Intl), so each date gets the offset that applied on that day, including past rule changes the database knows about.

To compare places, the Same moment in other time zones card starts with New York, London, Kolkata and Tokyo. Remove any with the cross, or pick a zone and press Add, up to 20. It is a quick way to plan a call or read a log from a server abroad.

UTC, Coordinated Universal Time, is the time at zero longitude with no summer time. Unix timestamps are defined in UTC, which is why the page opens as a timestamp converter UTC-first: Show in starts on UTC until you change it, and the ISO 8601 (UTC) row always stays in UTC with a Z at the end.

Local time is UTC plus an offset, such as +05:30 for India or -07:00 for California in summer. The Your time zone row shows the moment in your device's zone, so you see both without switching. A good habit: store and send timestamps or UTC times, and convert to local time only when showing them to a person.

ISO 8601 writes a date from the largest unit to the smallest: 2025-10-21T10:40:00Z. The T separates date and time, and the end shows the offset: Z for UTC, or +05:30, -04:00 and so on. It sorts correctly as plain text, and it is what JSON APIs, JavaScript's toISOString() and most databases expect. The form used here is also valid RFC 3339.

The timestamp converter ISO 8601 row shows milliseconds only when they are not zero and gives the offset of the zone you chose, so 10:40 UTC appears as 2025-10-21T16:10:00+05:30 for Asia/Kolkata. The ISO 8601 (UTC) row gives the Z form of the same moment.

RFC 2822 is the older format from email headers, such as Tue, 21 Oct 2025 10:40:00 +0000. HTTP headers and RSS feeds use a close relative. Copy whichever your system asks for.

A timestamp converter to date is only half the job; often you have a date and need the number. Type it in the Date to timestamp card, or use the date and time picker next to it, and choose the zone the date is in. You get Seconds, Milliseconds, ISO 8601 (UTC) and the offset of that zone on that date.

The box understands 2026-10-21 14:30, 2026-10-21T14:30:00.250, 21 Oct 2026 2:30 PM and RFC 2822 dates. A date that ends with Z or an offset such as +05:30 uses that offset and ignores the zone menu. Without one, the date is read as wall-clock time in the chosen zone, with summer time taken into account. A date alone, such as 2026-10-21, means midnight at the start of that day.

Dates with slashes are read the way your browser reads them, usually month first, so the year-month-day form is the safest choice.

The dark bar at the top shows the unix timestamp now, in seconds, updating every second, with the same moment in milliseconds and as a UTC time below it. Press Copy to take the seconds, Pause to freeze the clock, Resume to restart it, and Use to send the current value to the converter.

The clock comes from your device, so it is only as right as your device's time. Phones and computers that sync time automatically are usually within a fraction of a second.

Not every system counts from 1970. This epoch converter online also handles the other counters you meet in spreadsheets, Windows and Apple software: as output rows for every timestamp and, for Excel and Windows, as inputs in the Excel and Windows times card.

Windows FILETIME is also the format of Active Directory attributes such as lastLogonTimestamp, pwdLastSet and accountExpires, so you can paste an 18-digit value from an LDAP query into the FILETIME box and read the date. The Apple Cocoa value appears in iOS and macOS databases.

If you need an epoch converter in Excel itself, one formula is enough. Excel and Google Sheets store dates as days since 1900, and 1 January 1970 is day 25569, so a Unix timestamp in seconds becomes a date by dividing by 86,400 and adding that day:

Format the result cell as a date and time, or you see a plain number such as 45951.44. The result is in UTC; add or subtract hours divided by 24 for a local zone, keeping in mind that a fixed offset ignores summer time. Mac workbooks set to the 1904 date system count from 1904 instead, where 1970 is day 24107.

Going the other way, paste an Excel serial into the Excel / Sheets serial number box and the timestamp converter shows the ISO date and the Unix seconds. Excel serials have no time zone, so the result is shown as if the sheet were in UTC. In the output rows, the Excel / Google Sheets serial follows the zone under Show in, ready to paste into a sheet that uses that local time.

Paste up to 5,000 lines into Convert many at once, one timestamp or date per line, mixed if you like. Each line gets its ISO 8601 date in the zone under Show in and its Unix seconds, and the first 200 are listed on the page. Bulk unit can stay on Auto, which reads each number by its digits, or be set to s or ms when the whole list uses one unit.

Press CSV to download timestamps.csv with the columns input, type, iso_8601 and unix_seconds. It opens in any spreadsheet or database import, and lines the page could not read are marked not understood.

The Get or convert a timestamp in code panel under the tool has short snippets for JavaScript, Python, PHP, Java, C#, Go, MySQL, PostgreSQL, Bash and Excel: how to get the current time as a timestamp and how to turn one into a date. The most common ones:

Unix time pretends every day has exactly 86,400 seconds. Real UTC has had 27 leap seconds added since 1972 to keep clocks in step with the Earth's rotation. Unix time ignores them: during a leap second the count repeats a second or the system smooths it out, so the gap between two timestamps can be off by those seconds over long spans. For everyday dates this never matters, and this timestamp converter, like nearly all software, follows Unix time.

The year 2038 problem comes from systems that store timestamps as a signed 32-bit integer. The largest value, 2147483647, is 03:14:07 UTC on 19 January 2038. One second later such a counter overflows to -2147483648, which reads as 13 December 1901. Modern systems, databases and languages use 64-bit timestamps that last for billions of years, but old devices, file formats and database columns can still be affected. Type 2147483648 above to see the moment just after the limit.

Every conversion happens in your browser, using its built-in time-zone database (Intl). Timestamps, dates and bulk lists are not uploaded, logged or put in the address bar, and the CSV file is created on your device.

This timestamp converter remembers only your settings, the unit, the Show in zone, the extra zones and the bulk unit, in this browser's local storage. You can clear them in your browser's site data settings.

Timestamps often sit inside other data. The JWT Decoder shows a token's claims, including exp and iat, and the JSON Formatter makes an API response readable so you can find the date fields. To turn a bulk CSV into JSON, use CSV to JSON.

Need random IDs for test records? The UUID Generator makes them. To compare two log files line by line, open the Diff Checker, and to test a pattern that matches dates, try the Regex Tester.