Date & Time Converter

Convert Unix timestamps to human-readable dates, format dates as ISO 8601, or convert times between time zones.

Date & Time Converter
— or convert a date to a timestamp —

"Now" button:

📐 How to Use

  1. Choose a mode: "Unix Timestamp", "ISO 8601 Format", or "Time Zone".
  2. Unix Timestamp: enter a timestamp to convert it to a readable date, or pick a date/time to get its Unix timestamp (in both seconds and milliseconds).
  3. ISO 8601: pick a date and time to see it formatted as a standard ISO 8601 string, in both UTC and your local time zone.
  4. Time Zone: enter a date/time and source time zone, then select a target time zone to see the converted time.
  5. Results update instantly as you type — no need to click Calculate.

🎯 When to Use This

  • Debugging a log line that stores times as integers, where the seconds and milliseconds toggle settles which unit the field is using.
  • Writing an API payload that requires an ISO 8601 string, with both the UTC form and the offset-carrying local form shown together.
  • Scheduling a call across offices by converting a wall-clock time from one zone into another before you send the invitation.
  • Checking what a database timestamp means in your own local time, including the relative phrase telling you whether it is past or future.

❓ Frequently Asked Questions

QWhat is a Unix timestamp?
A Unix timestamp (or Epoch time) is the number of seconds (or milliseconds) that have elapsed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It is widely used in programming and databases to represent a point in time.
QWhat is the difference between seconds and milliseconds timestamps?
A seconds-based timestamp (10 digits for current dates) counts whole seconds since the Unix epoch. A milliseconds-based timestamp (13 digits for current dates) is 1,000 times larger and is commonly used by JavaScript's Date object and many APIs.
QWhat is ISO 8601 format?
ISO 8601 is an international standard for representing dates and times, e.g. "2026-06-11T14:30:00Z". The "Z" indicates UTC; offsets like "+05:30" indicate other time zones. It is unambiguous and widely used in APIs and data interchange.
QHow accurate is the time zone conversion?
Time zone conversions use your browser's built-in time zone database (IANA time zones), which includes daylight saving time rules. Results should match official local time for the selected zone and date.
QIs my data sent to a server?
No. All conversions happen locally in your browser using JavaScript's built-in Date and Intl APIs. Nothing is sent to or stored on any server.

ℹ️ About This Calculator

A Unix timestamp counts seconds since 1 January 1970 UTC, ignoring leap seconds, and it names an instant rather than a wall-clock reading. An ISO 8601 string names the same instant but carries an offset, which is why 14:30Z and 20:00+05:30 are the same moment. Confusing an instant with a local reading is the usual source of off-by-hours bugs in logs and APIs.

Three modes share the page. Unix mode reads a number as either seconds or milliseconds, depending on the toggle, and returns a UTC string, a full local rendering, a relative phrase and an ISO string, and it converts back from a date and time you pick. ISO mode prints the UTC form and a local form carrying your browser's offset. Time zone mode uses Intl.DateTimeFormat to read each zone's offset at the relevant instant.

⚠️ Notes & Limits

  • The relative phrase approximates a month as 30 days and a year as 365, so two months ago is a rough label rather than a calendar count.
  • Time zone mode resolves the source offset at the entered time read as UTC, so a time inside the hour of a daylight-saving shift can come out an hour off.
  • The zone menu lists 24 common IANA zones plus your browser's own; other zones cannot be typed in and no historical zone picker is offered.
  • ISO mode and the reverse Unix conversion read your entry in the browser's local zone, not UTC, so a machine set to the wrong zone gives the wrong instant.