UTC Time Zone Converter

What UTC actually is

UTC is a fixed reference point: an atomic-clock standard that the world agrees to measure time against. It has an offset of exactly zero, it never shifts for daylight saving, and it never changes its name — so "UTC+2" means the same thing in January and in July.

That fixedness is the whole point. Local civil time is a political and geographical layer stacked on top of UTC: a city picks an offset, sometimes adds an hour in summer, occasionally shifts by 30 or 45 minutes, and occasionally changes its mind entirely. UTC is the layer nobody has to renegotiate.

In the IANA time zone database — the same ruleset your phone, your laptop and your servers run on — UTC is simply the zone id "UTC". Systems that need a canonical instant store it as a UTC timestamp and render it in whatever local zone the reader happens to be in.

How to convert UTC to your local time

Conversion is arithmetic, but only if you use the right offset. Find the UTC offset of the target city *for the date you care about*, then add it to the UTC time and wrap around midnight if you cross 24 hours.

For example, 14:00 UTC on a winter day becomes 09:00 in New York (UTC−5), 15:00 in Berlin (UTC+1), 18:00 in Dubai (UTC+4), 23:00 in Tokyo (UTC+9) and 03:00 the next morning in Auckland (UTC+13). In summer, New York is UTC−4 and Berlin is UTC+2, so the same instant lands at 10:00 and 16:00.

• UTC+0 — London in winter, Reykjavík, Accra, Dakar, Abidjan
• UTC+1 — Berlin, Paris, Madrid, Rome, Warsaw, Lagos, Casablanca
• UTC+2 — Cairo, Nairobi, Pretoria, Athens, Bucharest, Helsinki
• UTC+3 — Moscow, Istanbul, Nairobi-adjacent East Africa, Addis Ababa
• UTC+4 — Dubai, Abu Dhabi, Muscat, Tehran (UTC+3:30), Yerevan
• UTC+5:30 — Delhi, Mumbai, Chennai, Kolkata, Colombo
• UTC+5:45 — Kathmandu
• UTC+7 — Bangkok, Jakarta, Ho Chi Minh City, Phnom Penh
• UTC+8 — Singapore, Hong Kong, Shanghai, Beijing, Taipei, Perth, Kuala Lumpur
• UTC+9 — Tokyo, Seoul, Osaka, Yakutsk
• UTC+10 — Sydney, Melbourne, Brisbane, Port Moresby, Vladivostok
• UTC+12 — Auckland, Fiji, New Zealand summer time

UTC vs GMT: the difference that actually matters

UTC and GMT are used interchangeably by almost everyone, and for practical purposes the distinction is invisible — but there is a real difference. GMT is a time zone tied to Greenwich, and in the IANA database Greenwich is an alias for the zone "Europe/London", which observes British Summer Time. UTC is a fixed offset with no daylight saving.

So for roughly six months of the year they agree exactly, and for the other six months London is one hour ahead of UTC. If a colleague says "GMT+1" in July, they almost certainly mean "UTC+1", and the number is what matters — not the label.

This converter always shows the abbreviation currently in force (GMT, BST, CET, CEST, JST …) next to the numeric offset, so there is never any ambiguity about which one you are looking at.

Why UTC is the language of machines

Log files, database timestamps, cron jobs, ISO 8601 strings, aviation schedules, satellite downlinks and API payloads all use UTC, because a single unambiguous instant is worth more than a friendly local time. If two servers in Frankfurt and Singapore both write "2026-03-14 02:30", nobody can tell whether they agree — but both writing "2026-03-14T02:30:00Z" removes the ambiguity entirely.

That said, daylight saving is still a human problem. Your meeting, your flight and your support hours are all denominated in local time, which is exactly why a converter that reads live IANA rules — rather than a hardcoded offset table — is worth using.