Skip to content
Redmoon Date Calculators

← Calculators

Business

International Business Day Converter

Cross-timezone business day overlaps.

Written and maintained by Paul Clark, Redmoon Software · Rules last verified

Monday, September 7, 2026
Across timezones
UTC
Sep 7, 2026
America/New_York
Sep 6, 2026
America/Los_Angeles
Sep 6, 2026
Europe/London
Sep 7, 2026
Europe/Paris
Sep 7, 2026
Asia/Tokyo
Sep 7, 2026
Asia/Singapore
Sep 7, 2026
Australia/Sydney
Sep 7, 2026

These calculators are for informational purposes only and do not constitute legal, financial, or professional advice.

How the International Business Day Converter works

The International Business Day Converter takes a single date and shows how that date reads across eight of the world’s major business hubs at once — UTC, New York, Los Angeles, London, Paris, Tokyo, Singapore, and Sydney. Line them up side by side and the effect is immediate: the moment that anchors your date is already the next calendar day in some cities and still the previous one in others. What looks like one row on your calendar is smeared across two dates once you span enough longitude.

This is the international date line and the ordinary hours of time-zone offset doing their work. When a reference instant sits at midnight in London, it is still the evening of the day before on the US West Coast and already well into the morning after in Sydney. Most people are comfortable converting times across zones — the 3pm call that is 8am somewhere else — but the subtler trap is the date rollover, because it stays invisible until it bites. A deadline pinned to a calendar date without a zone attached means several different moments for a team spread across continents.

The practical workflow is to settle the date in one canonical zone — UTC is the honest choice for anything international — then read across the row to see what that resolves to for each office. What the converter gives you is the local calendar date each hub will be on, and only that: it does not carry a holiday calendar and does not print the weekday, so take the eight dates it returns and check them against each office’s own weekend and public-holiday schedule before the invitation goes out. State deadlines with the zone explicit ("23:59 UTC on the 12th," not "end of day the 12th") and use the converter to translate that into the local date each party will actually experience.

Worked example

Anchor a deadline to the start of July 12 in UTC and the eight zones do not all agree it is the twelfth. In Los Angeles, seven hours behind, that instant is still the evening of July 11 — a full calendar day earlier. In Tokyo and Sydney, hours ahead, it is already well into July 12 and racing toward the thirteenth. So a task "due July 12" is, depending on where your colleague sits, due on the 11th, the 12th, or effectively the 13th of their local calendar.

Frequently asked questions

Why does the same date show up as a different day in some zones?

Because a calendar date is not a single global instant. The reference moment behind your date falls at a different local time in each zone, and for zones far enough east or west that local time lands on the previous or the next calendar day. The converter surfaces exactly where the date rolls over so you can see whose version of the date you mean.

Which zone should I treat as the canonical one?

For anything international, UTC is the honest anchor because it carries no daylight-saving ambiguity and no home-team bias. Settle the date and time in UTC, then read across the eight hubs to translate it into each local calendar date. That way the deadline you set is the deadline everyone keeps rather than the one your own clock happened to show.

Why worry about the date rather than just the time difference?

Because contracts, filing windows, embargoes, and market cut-offs hinge on a calendar date, and the calendar date is exactly the thing that shifts as you cross the globe. A report "due end of day Friday" may already be Saturday, or still Thursday, for offices far enough east or west of whoever set it — an error that stays invisible until a deadline is missed.

What this calculator does not do

A limitation you know about costs far less than one you find after the deadline. These are the specific things this tool cannot work out for you.

  • Conversions use the IANA time-zone database as shipped in your browser, so daylight-saving transitions are handled — but a date far in the future may be recomputed if a jurisdiction changes its rules.
  • It shows a fixed set of major zones rather than every zone in the database.

Related calculators

Send feedback

We read every message. Tell us what could be better or what you love.