Start with a date and a named time zone
A meeting time needs a calendar date and a location-based time zone. For a future call, convert the time on that date rather than subtracting the cities' current clock readings. Daylight-saving rules can make today's offset different from the meeting's offset.
Use a named zone such as America/New_York instead of an abbreviation such as EST, which describes one offset rather than every date in that city's calendar. Desklium uses the time-zone rules available in your browser; keep the browser and operating system current.
Worked example: New York, London, and Singapore
For October 8, 2026, enter 09:30 and America/New_York in the Time Zone Converter. Check Europe/London and Asia/Singapore in turn. The shared UTC instant is 13:30Z. These are illustrative calculations, not a real invitation.
A recurring meeting needs another check around clock changes. On March 16, 2026, the same 09:30 New York time is 13:30 in London. On October 8 it is 14:30 in London. Keeping the local New York time fixed does not keep the London time fixed throughout the year.
| Location | Local date | Local time on October 8 |
|---|---|---|
| New York | 2026-10-08 | 09:30 |
| London | 2026-10-08 | 14:30 |
| Singapore | 2026-10-08 | 21:30 |
Find overlap before sending the invitation
The example conversion is valid, but 21:30 is outside a typical Singapore workday. Use Meeting Overlap Planner with the chosen date and workday start and end. If the shared window is empty, that is useful information: agree on an exception, alternate inconvenient slots, or use an asynchronous handoff.
The current planner applies the same start and end clock times to each selected location. It does not model individual calendars, public holidays, or overnight shifts. Check participants' actual availability separately. Use World Clock for a quick current-time check, not as a substitute for converting a future meeting date.
Check skipped and repeated hours
When clocks move forward, some local times do not exist. Desklium reports a skipped local time as invalid. When clocks move back, an hour can occur twice; confirm the intended UTC instant if your meeting lands in that repeated hour.
Before sending, include the full date, city or zone, and each participant's local time. A calendar invitation with a time zone helps preserve the intended instant. Recheck recurring calls when time-zone rules or participants' locations change.
Try the tools
- Time Zone Converter — Convert a wall-clock date and time between IANA time zones.
- Meeting Overlap Planner — Compare working-hour windows for three locations on a chosen date.
- World Clock Dashboard — See current local times across a hand-picked set of global cities.
- Meeting Cost Calculator — Estimate meeting labor cost from attendees, duration, and hourly rates.
Sources and further reading
Tool-specific behavior and examples describe Desklium's current implementation; the linked references explain the underlying formats and time-zone data.
Found an incorrect example or a changed tool behavior? Contact Desklium with the page URL and a non-sensitive example.