Time Zone Calculator: Convert Times Across Zones

I was standing in the lumber aisle doing math on my phone and nothing was adding up.

I’m not even kidding. I had a delivery window in my text messages, a supplier in a different time zone, and a crew that was already annoyed because “they said noon” apparently meant something else. I nodded like I understood. I didn’t.

So I did what you probably do: I opened a notes app, started adding and subtracting hours, and somehow ended up with a time that didn’t exist (which is a fun little magic trick when daylight saving is involved).

That’s the whole reason we built a time zone calculator on ProCalc.ai. Not because time zones are “interesting,” but because you’ve got a call, a flight, a delivery, an online exam, a game, or whatever, and you need the correct time now.

Time zones are just offsets. Mostly.

What you’re actually converting (and why you keep getting it wrong)

The thing is, most people think time zone conversion is “add 3 hours” and call it a day. And sometimes that works! If it’s a random Tuesday in February and nobody’s doing anything weird with daylight saving time, you can get away with it.

But in real life, you’re juggling a few moving parts:

• The base time (the time you were given).
• The source zone (where that time “lives”).
• The target zone (where you need it to land).
• The date (because the date changes, and DST changes, and suddenly you’re off by an hour and nobody believes you).

And yes, the date matters. If you convert 11:30 PM from one zone to another, you might land on the next day. That’s not “wrong,” it’s just annoying.

And daylight saving is the sneaky one.

I used to treat DST like a rumor. Then I had a concrete pour scheduled for “7:00 AM” and the inspector was like, “No, you’re an hour late.” That was… not my favorite morning. So now I’m pretty opinionated about this: if you’re converting times, you don’t guess. You calculate.

Do it the clean way: offset math (with a real worked example)

If you’re doing this by hand (or you just want to sanity-check a calculator), here’s the basic idea. You convert the source time to a neutral reference, then convert to the target zone. In practice, that “neutral reference” is basically UTC, which is just a standard time baseline.

Now, a worked example you can actually use.

Say you’ve got a Zoom call set for 2:00 PM in a zone that’s UTC−5, and you need to know what time that is for someone in UTC+1. (I’m using offsets instead of zone names on purpose because zone names get messy and offsets are the math part.)

1. Source Time = 2:00 PM
2. Source Offset = −5
3. Target Offset = +1
4. Offset difference = (+1 − (−5)) = +6 hours
5. Target Time = 2:00 PM + 6 hours = 8:00 PM

So you tell them 8:00 PM. And you don’t sound like you’re guessing. And you don’t end up with that awkward “wait… are you sure?” message five minutes before the call.

But here’s the catch: offsets aren’t always constant because DST can change the offset depending on the date (and not every place switches on the same day). So if you’re converting anything that matters, use a calculator that asks for the date, not just the time.

Quick table: common offset moves (so you can eyeball-check)

I like having a little “does this feel right?” table. Not to replace a calculator, just to catch obvious mistakes like accidentally subtracting when you meant to add.

That 5.5-hour row is there because half-hour zones are real, and they will absolutely ruin your day if you forget they exist.

Use the calculator (and stop arguing with your calendar)

So here’s the practical workflow I use, especially for work stuff where people are waiting on you:

1. Get the time and the date. If someone says “Friday at 9,” you ask “Friday where?” (Yes, it feels awkward. Do it anyway.)
2. Confirm the source time zone. Not “my time,” not “your time.” The actual zone.
3. Convert to the target zone and write it down with the zone label.
4. Sanity-check with the offset difference so you don’t do something silly like flip the sign.

And if you want to just punch it in and move on with your life, use these:

And yeah, here’s the embedded one so you don’t have to bounce around:

I’ll say one more thing, because I’ve watched this go sideways on job sites and in office meetings: if you’re scheduling something that involves multiple zones, put the time zone in the message. Don’t just write “3:00.” Write “3:00 PM UTC−5” or “3:00 PM Eastern” or whatever you’re using. It feels a little extra. It saves you a pile of back-and-forth.

That’s a lot of wasted time you don’t get back!

FAQ (the stuff people always ask five minutes before the meeting)