Time/Numbers

Timezone Converter

One moment in time, across several time zones at once. Compare working hours, plan calls, see the day difference.


                    

This tool shows one moment in time across several time zones at once — handy when a team or your clients are spread across countries and you need to quickly find a workable time for a call.

How to use it

Common uses

Things to keep in mind

The offset between zones isn't always a whole number of hours — some zones are offset by 30 or 45 minutes (e.g. India, Nepal).

Daylight saving transitions happen on different dates in different countries, so the gap between two zones can shift temporarily during the year.

Article about this tool: Time zones: why UTC isn't the same thing as GMT

Frequently asked questions

Is daylight saving time transition accounted for?

Yes, the converter relies on IANA rules for the selected timezones and automatically accounts for DST — the result will be correct even if the date falls on a transition day.

Why is it better to choose an IANA timezone name rather than a fixed UTC offset?

An offset like UTC+2 doesn't "know" about daylight saving transitions and can become incorrect in a different season. A name like "Europe/Kyiv" always follows the current rules for that region.

What does the (+1 day) or (-1 day) marker next to a time mean?

It shows that in the target timezone it's already the next calendar day, or still the previous one, compared to the source date — this often happens with a large hour difference.

Are all time zones offset by a whole number of hours?

No, some have a fractional offset — for example, India (UTC+5:30), Nepal (UTC+5:45), or parts of Australia (UTC+9:30). That's why this converter relies on IANA timezone names rather than plain integer-hour offsets.

How many time zones can I compare at once?

You can add as many target time zones as you need with the "Add time zone" button — handy for seeing the time for a team spread across several countries at once.

Articles: Time/Numbers

Unix time: why computers count time from 1970

Why January 1, 1970 became the reference point for time in most computer systems.

Cron expressions: how to decode a task schedule

How to decode an expression like */15 * * * * and know exactly when the job will run.

Number systems: why binary, octal, and hexadecimal exist

Why the color #FF5733 in CSS is written in hexadecimal digits instead of decimal.

Bitwise operations: how AND, OR, and XOR work at the bit level

How bitwise AND differs from logical AND, and why you'd operate on individual bits of a number at all.

Date difference: why counting days is trickier than it looks

Why naively subtracting dates can give the wrong result because of leap years.

Age calculation: why it's not just subtracting years

Why simply subtracting birth years can give an age one year higher than the real one.

Duration calculator: how to correctly add up hours, minutes, and seconds

Why adding minutes and seconds requires "carrying" the remainder to the next place, just like in decimal addition.

ISO 8601 duration: how to write a duration in a standard format

Why PT1H30M means "1 hour 30 minutes," not "1 minute 30 hours."

Week number: why different countries count weeks differently

Why January 1 sometimes falls into week 52 or 53 of the previous year under the ISO 8601 standard.

Roman numerals: how a system with no zero and no place value works

Why IV means 4, not 6, and how the subtraction rule works in Roman numerals.

IEEE 754: why 0.1 + 0.2 doesn't equal 0.3 in code

Why almost every programming language prints 0.1 + 0.2 as 0.30000000000000004.

Number to words: why turn digits into text

Why bank documents write an amount both in digits and in words at the same time.