UTC Time Converter

How to convert UTC to your local time

Pick your time zone from the list, and the live UTC display shows the current local time alongside it. But the conversion only works if you know two things: your current offset (like UTC-5 or UTC+5:30) and whether daylight saving time is in effect where you are right now. Select "Eastern Time" in January and the offset is UTC-5. Select it in July and it is UTC-4. That switch is the most common reason conversions go wrong.

Understanding UTC offsets for conversion

Every place on Earth has a base offset from UTC, expressed as UTC±HH:MM. The offset tells you how many hours and minutes to add to UTC to get local time, or subtract from local time to get back to UTC. A positive offset (UTC+1, UTC+8) means local time is ahead of UTC. A negative offset (UTC-5, UTC-8) means local time is behind.

From the January 2026 fact sheet: New York at UTC-5, Los Angeles at UTC-8, London at UTC+0, Paris at UTC+1, Dubai at UTC+4, Mumbai at UTC+5:30, Singapore at UTC+8, Tokyo at UTC+9, Sydney at UTC+11, Johannesburg at UTC+2, São Paulo at UTC-3, Chicago at UTC-6.

Manual conversion: add or subtract your offset

If you are reading a UTC timestamp in an email and need to convert it without a tool, do this:

1. Note the UTC time. Use 24-hour format to avoid AM/PM mistakes. 14:00 UTC is 2:00 PM, not 2:00 AM.
2. Find your current offset. In January, New York is UTC-5. In July, New York is UTC-4.
3. If your offset is positive, add it to UTC. If negative, subtract it.

Example: UTC 14:00 in January for New York (UTC-5). 14:00 minus 5 hours = 09:00 local (9:00 AM EST).

Example: UTC 14:00 in July for New York (UTC-4). 14:00 minus 4 hours = 10:00 local (10:00 AM EDT).

The same UTC time gives different local times in the same city because the offset changed. UTC did not move, your local clock did.

Common UTC conversions to EST, PST, IST and CET

These examples use the January 2026 offsets (standard time in the Northern Hemisphere):

In July, the Northern Hemisphere cities shift. New York becomes UTC-4 (EDT), Los Angeles UTC-7 (PDT), London UTC+1 (BST), Paris UTC+2 (CEST). Mumbai, Tokyo, and Johannesburg do not observe DST, their offsets stay the same year-round.

Daylight saving: why your offset changes

Daylight saving time is a local decision. UTC never observes it. When your government moves the clock forward in spring, your offset from UTC increases by one hour. When clocks go back in autumn, your offset decreases by the same amount.

The common error: someone notes their offset in winter (say UTC-5 for New York) and uses it all year. In July they are actually at UTC-4. Their conversion will be one hour off. If they are scheduling a 15:00 UTC call in July using the winter offset, they will arrive at 10:00 local instead of 11:00 local, and miss the meeting.

The solution: check your current offset every time you convert. Selecting the correct IANA time zone (not just the abbreviation) handles the DST switch automatically.

Why the 24-hour clock matters for UTC conversion

UTC contexts, aviation, IT, global scheduling, use the 24-hour clock. 00:00 is midnight. 12:00 is noon. 23:59 is one minute before midnight. There is no AM or PM. This eliminates the most common source of conversion error: confusing 2:00 AM with 2:00 PM when adding or subtracting hours.

If you receive a UTC time in 12-hour format ("2:00 PM UTC"), convert it to 14:00 before doing the math. Write it in 24-hour format. One wrong AM/PM and your meeting is off by 12 hours.

Quick reference: major cities UTC conversion

Keep this for daily use. Offsets are for January 2026 (standard time in the Northern Hemisphere).