Time Zone Converter

Convert times between any two time zones worldwide. See current time in popular cities and schedule across time zones instantly.

From Time Zone
To Time Zone
—
World Clock updates every second
UTC Offset Reference
Time ZoneUTC OffsetRegionDST?
UTC / GMT+00:00UniversalNo
America/New_York (ET)−05:00 / −04:00US EastYes
America/Chicago (CT)−06:00 / −05:00US CentralYes
America/Los_Angeles (PT)−08:00 / −07:00US WestYes
Europe/London (GMT/BST)+00:00 / +01:00UKYes
Europe/Paris (CET)+01:00 / +02:00Central EuropeYes
Asia/Dubai (GST)+04:00UAENo
Asia/Kolkata (IST)+05:30IndiaNo
Asia/Dhaka (BST)+06:00BangladeshNo
Asia/Bangkok (ICT)+07:00SE AsiaNo
Asia/Shanghai (CST)+08:00ChinaNo
Asia/Tokyo (JST)+09:00JapanNo
Australia/Sydney (AEST)+10:00 / +11:00Australia EastYes

Frequently Asked Questions

A time zone is a region of the globe that observes a uniform standard time for legal, commercial, and social purposes. There are 24 main time zones offset from UTC (Coordinated Universal Time) by whole or half hours. Some zones like India (UTC+5:30) and Nepal (UTC+5:45) use non-standard offsets.
Daylight Saving Time is the practice of advancing clocks by 1 hour in summer to extend evening daylight. Not all countries observe DST — most of Asia, Africa, and parts of South America do not. The US and EU observe DST, but transition on different dates, causing the offset between them to change briefly each year.
UTC (Coordinated Universal Time) is the primary time standard by which the world regulates clocks and time. It does not observe DST and serves as the reference from which all other time zones are calculated. UTC replaced GMT (Greenwich Mean Time) as the world standard, though the two are practically equivalent for everyday use.
IANA (Internet Assigned Numbers Authority) time zone identifiers use the format Region/City (e.g., America/New_York, Asia/Tokyo). These are the standard used by operating systems, programming languages, and this tool. They automatically account for DST transitions, historical changes, and political boundary shifts.
There are 24 standard time zones based on whole-hour offsets from UTC. However, the real total is higher when you include fractional-hour offsets. Countries like India (UTC+5:30), Iran (UTC+3:30), and Nepal (UTC+5:45) use non-standard offsets, bringing the total number of distinct UTC offsets in use to around 38. The IANA time zone database tracks hundreds of named zones because of political boundaries and historical changes.
The majority of the world does not observe DST. Countries that skip it include most of Asia (China, Japan, India, South Korea), nearly all of Africa, most of South America, and many island nations. Countries that do observe DST include the US, Canada, most of Europe, Australia, and New Zealand — though even within these regions some territories opt out (e.g., Arizona in the US).
The key principle is to always communicate a meeting time in UTC (or a clearly stated reference time zone) and let participants convert to their local time. Be aware of DST transitions which can shift overlaps unexpectedly. For recurring meetings, anchor to a fixed UTC time rather than a local time that shifts with DST. Rotating meeting times fairly across time zones shows respect for all participants.
Most time zones are offset from UTC by a whole number of hours, but some countries use fractional offsets. Notable examples: India (IST) = UTC+5:30, Iran = UTC+3:30, Afghanistan = UTC+4:30. The most unusual is Nepal (NPT) = UTC+5:45 — the only major time zone with a 45-minute offset. These exist so the country's standard time better aligns with solar noon across its territory.
IANA timezone identifiers (e.g., America/New_York) are unambiguous: they uniquely identify a time zone including its full history of DST rules and UTC offsets. Abbreviations like EST, IST, or CST are ambiguous — IST stands for Indian Standard Time, Irish Standard Time, and Israel Standard Time depending on context. For software, APIs, and scheduling, always use IANA identifiers.
UTC (Coordinated Universal Time) is the global reference standard for timekeeping. It replaced GMT as the world's primary time standard in 1972 and is maintained by atomic clocks. Unlike GMT, UTC is kept in precise synchronisation using leap seconds. All other time zones are expressed as an offset from UTC. UTC never observes Daylight Saving Time, making it the stable foundation for aviation, internet protocols, financial markets, and global software systems.

About This Timezone Converter

This free timezone converter converts a date and time from one IANA time zone to any other, accounting for daylight saving time transitions automatically. Select a source zone, enter a date and time, and choose a target zone to see the converted result.

When to use this converter

  • Scheduling international meetings across multiple time zones
  • Debugging timestamps in server logs from different regions
  • Converting event times for a global audience
  • Tracking when stock markets open and close in your local time

Standards & References

Related Converters

Time Converter Currency Exchange Speed Converter Frequency Converter

Related Articles

In-depth guides and technical articles.

View all →
Converters Aug 1, 2026
The Database That Runs Every Clock in Every App Almost Went Away in 2011 — The IANA Timezone Database Story
The IANA Time Zone Database — the source of timezone rules for Linux, macOS, Python, Java, and essentially every software platform — was briefly taken offline in 2011 due to a copyright lawsuit, creating a crisis for global software infrastructure. Here's how Samoa skipped an entire calendar day in December 2011, why Egypt and Morocco changed their DST rules with days of notice, the correct UTC-first database storage pattern, and why "UTC+1" is the wrong way to store a timezone.
Converters Jun 29, 2026
Why "9 AM London, Every Monday" Arrives at 3 AM in New York Some Weeks — DST, Offset Arithmetic, and Scheduling Global Teams
Tokyo doesn't observe DST; New York does — which means a weekly meeting at "9 AM London" shifts by an hour relative to Tokyo twice a year, while New York shifts at slightly different times than London does. Here's the full offset arithmetic for a London-New York-Tokyo meeting across the year, why "9 AM UTC" is more stable than "9 AM London" for global recurring meetings, and why calendar events stored with UTC offsets break at DST transitions while IANA timezone identifiers don't.
Converters Jun 17, 2026
Why "UTC+1" Is the Wrong Way to Represent a Timezone — DST, the IANA Database, and Ambiguous Hours
Daylight Saving Time doesn't just change what clocks show — it changes the UTC offset for every observing timezone, making "UTC+1" ambiguous between London in winter, Paris in winter, and West Africa Time year-round. Here's the IANA timezone database and what it actually contains, why hardcoded UTC offsets break twice a year, the genuinely ambiguous edge cases at spring-forward and fall-back boundaries, and why the standard advice is "store UTC, convert for display."
Converters Jun 12, 2026
Scheduling Across Timezones: Finding Overlap Windows, Fair Meeting Rotation, and Async-First Practices
A 9 AM New York meeting is 10 PM in Singapore — and scheduling from headquarters systematically burdens everyone else. Here's how to visualise timezone overlap (or its absence), rotating meeting approaches for fair distribution, the 2-3 week DST gap between US and European transitions, and async-first practices for wide timezone spreads.
Converters Jun 9, 2026
Time Zone Converter — Convert Any Time Between World Timezones Instantly
Learn how time zones work, why Daylight Saving Time causes scheduling surprises, how to find convenient overlap for remote teams, and how to use a free time zone converter for meetings, logs, and travel planning.