Time Zone Converter & World Clock
Convert a time between time zones and see a world clock.
Runs in your browser — files never leave your device
| UTC | Jul 26, 2026, 4:21 PM |
|---|---|
| America/New_York | Jul 26, 2026, 12:21 PM |
| America/Los_Angeles | Jul 26, 2026, 9:21 AM |
| America/Chicago | Jul 26, 2026, 11:21 AM |
| Europe/London | Jul 26, 2026, 5:21 PM |
| Europe/Paris | Jul 26, 2026, 6:21 PM |
| Asia/Kolkata | Jul 26, 2026, 9:51 PM |
| Asia/Dubai | Jul 26, 2026, 8:21 PM |
| Asia/Singapore | Jul 27, 2026, 12:21 AM |
| Asia/Tokyo | Jul 27, 2026, 1:21 AM |
| Australia/Sydney | Jul 27, 2026, 2:21 AM |
How it works
Enter one wall-clock time, tell the tool which zone that time belongs to, and it renders the same instant across 11 zones at once: UTC, New York, Los Angeles, Chicago, London, Paris, Kolkata, Dubai, Singapore, Tokyo, and Sydney. Everything recalculates as you type, so it doubles as a scratchpad for scheduling calls, webinars, deploy windows, and market opens across regions.
Under the hood it uses the browser’s Intl API, which ships the same IANA time-zone database that servers use. The tool first determines the source zone’s UTC offset at that exact moment, converts your wall-clock entry into an absolute instant, then formats that instant for each listed zone. Daylight saving is applied automatically per zone and per date — there are no hand-maintained offsets to go stale, and rule changes arrive with normal browser updates.
A fixed example shows why per-date rules matter. March 15, 2026, 9:00 AM in New York converts to 1:00 PM in both UTC and London — the United States enters daylight saving on March 8, but the United Kingdom not until March 29, so for those three weeks New York and London sit 4 hours apart instead of the usual 5. Enter March 30 instead and 9:00 AM in New York becomes 2:00 PM in London. The same March 15 entry reads 6:30 PM in Kolkata (a half-hour-offset zone at UTC+5:30), 10:00 PM in Tokyo, and 12:00 AM on March 16 in Sydney — a different calendar day.
That last detail is the classic scheduling trap: always check the date column, not just the clock time, when Australia or East Asia is involved. Pick the zone the meeting was quoted in as the source zone, and read everyone else’s local time straight off the table.
Frequently asked questions
- Which time-zone database does the converter use?
- The IANA time-zone database (the “tz database”), as shipped with your browser through the Intl internationalization API. That is the same source of truth Linux servers and most programming languages use, and it is kept current by regular browser updates — no manually maintained offset table is involved.
- Does it handle daylight saving time correctly?
- Yes — offsets are computed for the specific date you enter, not from a static table. For example, 9:00 AM in New York on March 15, 2026 is 1:00 PM in London — a 4-hour gap, because the US starts DST on March 8, 2026 while the UK waits until March 29. Enter March 30 instead and 9:00 AM in New York is 2:00 PM in London, the usual 5 hours.
- Why do some rows show a different date?
- Large offsets push the same instant past midnight. 9:00 AM on March 15, 2026 in New York is already 12:00 AM on March 16 in Sydney. When scheduling with Australia or East Asia, confirm the date as well as the time — “Tuesday” for one side is often “Wednesday” for the other.
- Are half-hour time zones supported?
- Yes. Kolkata runs at UTC+5:30, so an instant that reads 1:00 PM in UTC shows as 6:30 PM in Kolkata. The offset math is exact to the minute, so 30- and 45-minute zones convert correctly.
- What about times that don’t exist or occur twice during DST changes?
- When clocks spring forward, one local hour is skipped (2:30 AM may never occur that night); when they fall back, one hour repeats. If you enter a wall-clock time inside such a window, the converter resolves it to a single instant using the zone’s offset around that moment. Double-check anything scheduled in a transition hour — better yet, avoid booking meetings there.
- Is the time I enter uploaded anywhere?
- No — all conversion happens in your browser using its built-in time-zone data. Nothing is uploaded, logged, or stored.
Related tools
- Date Difference CalculatorFind the number of days, weeks, months and years between two dates.
- Date Add / SubtractAdd or subtract days, weeks, months or years from a date.
- Age CalculatorCalculate exact age in years, months and days from a birth date.
- Stopwatch & TimerA simple, accurate stopwatch and countdown timer that runs in your browser.