Timezone Meeting Converter

This timezone meeting converter converts one meeting time across several timezones at once, correctly handling daylight saving time using your browser's own timezone database. No accounts, no calendar integration — just a fast conversion.

How to use it

Pick the timezone the meeting time is already in, set the date and time, then add whichever timezones your other attendees are in. Each row updates live and flags when the converted time falls on a different calendar day.

Why IANA timezone names instead of offsets

Names like Europe/Berlin or America/Chicago encode a full history of daylight-saving rules for that region, not just a single fixed offset — which is exactly why converting "9am Berlin time" six months from now still needs to know it's Berlin, not just "UTC+1" or "UTC+2." This tool always works from named zones for that reason.

How the conversion is computed

Given a wall-clock time in a specific zone, the tool asks the browser's Intl API what UTC instant that corresponds to (by comparing against how that instant would display in the same zone, and correcting for the difference), then reformats that single instant into every other zone you've added. All zones are describing the exact same moment.

Timezone Meeting Converter Pro

Pro version coming soon — batch validation via CSV upload, exportable results, API access, and an offline version. The free tool stays free.

Pro version coming soon

Batch validation via CSV upload, exportable results, API access, and an offline version are on the way. The free tool stays free.

Frequently asked questions

How does this handle daylight saving time?

Correctly and automatically — it reads each timezone's actual UTC offset for the specific date you picked, using your browser's built-in timezone database, so a meeting scheduled across a DST transition still converts accurately.

Why not just use UTC offsets like "UTC+2" directly?

A fixed UTC offset silently breaks across DST transitions — "UTC+2" today might be "UTC+1" in six months for the same city. Using named IANA timezones (like "Europe/Berlin") instead of raw offsets is what keeps the conversion correct year-round.

Does this need a timezone conversion library?

No — every modern browser already ships a complete, regularly-updated IANA timezone database via the Intl API. This tool uses that directly instead of bundling a separate library, so it's both smaller and exactly as accurate as your browser's own clock and date settings.

What does the day indicator mean?

When a converted time falls on a different calendar day than the meeting's original date, this tool shows "+1 day" or "−1 day" next to it — an easy detail to miss when scheduling across timezones that are far enough apart to cross midnight.

Is my meeting time sent anywhere?

No. The conversion happens entirely in your browser using the Intl API — nothing is transmitted, logged, or stored.