Convert any date and time into 21 major world time zones at once — perfect for planning international meetings, calls, and travel. Daylight Saving Time is handled automatically.
| City / Zone | Local Date & Time |
|---|
Pick a date, time and source zone, then click Convert to see the equivalent time worldwide
This free time zone converter and world clock takes a single date and time and instantly shows what that same moment looks like in 21 major cities and time zones around the world — useful for scheduling international meetings, planning calls with remote teams, or working out arrival times for flights and trips. Enter any date, pick the zone it's written in, and see it translated everywhere from Honolulu to Auckland in one click.
Enter a date and time and choose the time zone it's written in as the "From" zone, then click Convert. The tool looks up the exact UTC offset for that date in every zone — using the same time zone database built into your browser and operating system — so Daylight Saving Time shifts are applied automatically rather than using a fixed, always-wrong offset. Your source zone is highlighted in the results table so it's easy to see the reference point at a glance, and every other zone updates simultaneously in the same table.
This world clock is built for remote workers and managers coordinating across distributed teams, travelers mapping out flight departure and arrival times, event organizers scheduling webinars or livestreams for a global audience, and anyone who regularly needs to know "what time is it there right now" without doing DST math in their head. It's equally useful for a one-off international call or for repeatedly checking the same handful of zones throughout the week.
Fixed-offset time math breaks twice a year whenever a region enters or exits Daylight Saving Time, and different countries switch on different dates — a common source of missed meetings and mistimed calls. Calculating each zone's offset from the actual calendar date, rather than assuming a constant gap, keeps every converted time accurate no matter when in the year you're planning around.
The logic behind turning one date and time into 21 correct local times
UTC (Coordinated Universal Time) is the fixed reference point every time zone is defined relative to. Rather than storing "New York is always 5 hours behind UTC," the calculator asks the browser's built-in time zone database what New York's offset actually is on the specific date you entered — because that offset is only −5:00 for part of the year (Eastern Standard Time) and −4:00 the rest of the year (Eastern Daylight Time). The same lookup happens independently for all 21 listed zones, which is why the results table can show London switching between GMT and BST, or Sydney between AEST and AEDT, without any manual rule-writing.
Every zone's local time is derived from the same underlying UTC instant, so the 21 results always describe exactly the same moment, just expressed differently.
Because the offset is looked up per-date rather than hardcoded, the converter automatically applies the correct Daylight Saving Time rule for zones that observe it.
Several of the 21 listed zones carry dual abbreviations (like GMT/BST or CET/CEST) precisely because their real-world offset from UTC changes across the year.
From entering a date to reading the equivalent time worldwide
Pick the date and time you want to convert in the Date & Time field. It defaults to the current moment on your device, but you can change it to any past or future date.
Choose the time zone that the date and time you entered are written in. The dropdown pre-selects your browser's detected zone if it's one of the 21 listed.
The calculator anchors your input to a precise UTC instant, then works out the correct local time in all 21 listed zones for that exact moment.
Scan the results table for the specific city or zone you need — a colleague's office, a client's location, or a travel destination.
Note the local date and 12-hour time shown for that zone, and use the highlighted "From" row to keep track of your original source zone at a glance.
Converting 3:00 PM New York time to London and Tokyo — in summer and in winter
Suppose it's 3:00 PM on Wednesday, July 15 in New York, and you select America/New_York as the "From" zone.
Now suppose the exact same clock time, 3:00 PM, is entered for Wednesday, January 15 in New York instead.
Explanation: Notice that 3:00 PM in New York lines up with 8:00 PM in London in January but only 8:00 PM lines up with 7:00 PM UTC in July — the New York–London gap itself changes from 5 hours to 4 hours because both cities observe Daylight Saving Time, just not on identical calendar dates every week of the transition period. Tokyo, which never observes DST, keeps a completely stable relationship to UTC in both scenarios — its gap to New York moves only because New York's own offset moved. This is exactly the kind of shift that a fixed "just add 9 hours" mental calculation misses, and why the converter re-derives every offset for the specific date entered.
How to read the results table correctly
| Result Element | What It Means |
|---|---|
| City / Zone label | The listed city or region plus its common abbreviation, e.g. "Tokyo – JST" or "London – GMT/BST." A dual label means that zone alternates between two abbreviations across the year. |
| Local Date & Time | Shown in 12-hour format with AM/PM, plus the weekday, month, day and year — e.g. "Wed, Jul 15, 2026, 8:00 PM" — so the date is never ambiguous even when it rolls to the next or previous day. |
| Highlighted row (From) | The row matching your selected source zone is shaded and labeled "(From)," giving you a fixed reference point while scanning the other 20 rows. |
| No numeric UTC offset column | The table doesn't print a raw offset like "+05:30" — the offset is already baked into the local time shown, and the zone abbreviation in the label communicates it (e.g. IST is always UTC+5:30). |
Reading AM/PM vs. 24-hour thinking: All results use 12-hour clock notation with AM/PM rather than 24-hour ("military") time. If you're more used to 24-hour format, remember that any time reading "12:00 AM" is midnight (the very start of that date) and "12:00 PM" is noon.
Reading the date, not just the time: Because the same instant can fall on a different calendar date elsewhere in the world, always check the weekday/date shown alongside the time — a converted result of "4:00 AM" the next day is a different moment in your planning than "4:00 AM" the same day would be.
This converter is a scheduling aid based on your browser's time zone data. For legal, contractual, or safety-critical timing (e.g. court filing deadlines, financial market cutoffs), verify the applicable official time from the relevant authority.
Where instant, DST-aware time zone conversion is genuinely useful
Find a meeting slot that works across distributed team members in different countries.
Confirm a client or partner call time won't land at an inconvenient hour on their end.
Work out local arrival and departure times when booking or tracking international travel.
Publish an event start time that's correctly translated for a global audience.
Students coordinating classes, exams, or advisor calls across countries and semesters abroad.
Expats and immigrants checking a considerate time to call relatives back home.
E-commerce teams coordinating order cutoff times across warehouses and customers in different zones.
Streamers and creators scheduling a release so it lands at a good time for viewers worldwide.
Support managers mapping agent shift start times against customers' local business hours.
Coordinate video calls at a reasonable hour for both people across the time difference.
Organizers publishing match start times that convert correctly for international players and viewers.
Check when a foreign market or exchange opens relative to your own local time.
Coordinate a synchronized announcement or release across offices in different countries.
Schedule cross-border calls between offices, embassies, or field teams in different zones.
What this time zone converter does well, and where it has boundaries
The 21 zones supported by this converter, with their standard-time UTC offset
| City / Zone | Abbreviation | Standard UTC Offset | Observes DST? |
|---|---|---|---|
| Honolulu | HST | UTC−10:00 | No |
| Anchorage | AKST/AKDT | UTC−9:00 | Yes |
| Los Angeles | PT (PST/PDT) | UTC−8:00 | Yes |
| Denver | MT (MST/MDT) | UTC−7:00 | Yes |
| Chicago | CT (CST/CDT) | UTC−6:00 | Yes |
| New York | ET (EST/EDT) | UTC−5:00 | Yes |
| São Paulo | BRT | UTC−3:00 | No (currently) |
| UTC | UTC | UTC±0:00 | No |
| London | GMT/BST | UTC±0:00 | Yes |
| Paris | CET/CEST | UTC+1:00 | Yes |
| Moscow | MSK | UTC+3:00 | No |
| Cairo | EET | UTC+2:00 | Varies by year* |
| Dubai | GST | UTC+4:00 | No |
| Mumbai / New Delhi | IST | UTC+5:30 | No |
| Dhaka | BST | UTC+6:00 | No |
| Bangkok | ICT | UTC+7:00 | No |
| Beijing / Shanghai | CST | UTC+8:00 | No |
| Tokyo | JST | UTC+9:00 | No |
| Seoul | KST | UTC+9:00 | No |
| Sydney | AEST/AEDT | UTC+10:00 | Yes |
| Auckland | NZST/NZDT | UTC+12:00 | Yes |
*Egypt has switched its Daylight Saving Time policy on and off multiple times in recent years — a real-world example of exactly why this converter looks up each zone's rule for the specific date entered rather than hardcoding a single answer. Offsets above reflect standard (non-DST) time; zones marked "Yes" shift by one hour for part of the year, which the converter applies automatically based on your selected date.
Summary: This time zone converter turns one date, time, and source zone into an accurate world-clock view across 21 major zones, automatically applying Daylight Saving Time rules for the exact date you choose. Use it for meeting scheduling, travel planning, and any situation where "what time is it there" needs to be right, not just roughly right. Pair it with the Countdown Calculator and Date Difference Calculator for broader date and time planning.
Common questions about converting between time zones
Official references to complement this calculator
Explore other time & date tools