induwara.lk
induwara.lkUtility · Time

Timezone Converter — convert time across cities with DST

Convert any wall-clock time between two cities with full daylight-saving awareness. Pick a date, a time, and the source and target zones — the tool resolves them through the IANA tz database that ships in your browser. No signup, no tracking, no network call.

By Induwara AshinsanaUpdated May 11, 2026
Convert a time across time zones
IANA tzdata · DST-aware

Calendar date read in the source zone's local clock.

Wall-clock time in the source zone.

UTC+05:30· GMT+5:30· Asia/Colombo
UTC-04:00· EDT· America/New_York
Quick target
Source · GMT+5:30
14:00
Mon, 11 May 2026 · 14:00
Target · EDT
04:30
Mon, 11 May 2026 · 04:30
Offset difference
−9h 30m
UTC+05:30 → UTC-04:00
Day delta
Same day
Target date: Mon, 11 May

Same moment, other cities

ColomboGMT+5:30
14:00
Mon, 11 May
LondonGMT+1
09:30
Mon, 11 May
New YorkEDT
04:30
Mon, 11 May
Los AngelesPDT
01:30
Mon, 11 May
DubaiGMT+4
12:30
Mon, 11 May
SingaporeGMT+8
16:30
Mon, 11 May
TokyoGMT+9
17:30
Mon, 11 May
SydneyGMT+10
18:30
Mon, 11 May
Runs entirely in your browser.

How it works

A wall-clock time on its own (say 14:00 on 11 May 2026) is ambiguous without a zone — it points to a different moment in Colombo than it does in London. The converter handles this in two deterministic steps:

  1. Resolve the entered date and time, plus the sourcezone, to a single UTC instant (epoch milliseconds). The browser's Intl.DateTimeFormat knows the historical offset of every IANA zone — including DST shifts — and the conversion uses that lookup directly.
  2. Format the same UTC instant in the targetzone's local clock. Because both steps share one instant, the conversion is exact: the answer is what an atomic clock would read.

Daylight saving is handled correctly because offsets are looked up at the actual instant, not at the current moment. Converting 2 pm New York time in July uses EDT (UTC−4); the same wall clock in January uses EST (UTC−5). The same logic applies to Australia's southern-hemisphere DST, the UK's BST, central European CEST, and so on.

Sri Lanka itself sits on Asia/Colombo, fixed at UTC+5:30 with no daylight saving. The IANA database also knows the country's 1996–2006 stint at UTC+6, so historical conversions stay accurate.

Two edge cases get explicit handling. On spring-forward days, a wall clock can skip an hour entirely (02:30 didn't exist in New York on 8 March 2026). On fall-back days, the same wall clock occurs twice. The converter resolves both by picking the later offset — the same default disambiguation rule used by the upcoming Temporal.ZonedDateTime API.

Everything runs client-side. The browser ships the full IANA tz dataset and the ECMAScript Internationalization API surfaces it through formatToParts(). That means no network request, no server round-trip, and the calculator works the same on a flaky connection as on a fast one.

Worked examples

Source

Colombo (UTC+5:30) · 14:00 on 11 May 2026

Result

New York (EDT, UTC−4) · 04:30 on 11 May 2026

  1. Read 14:00 in Asia/Colombo at its current offset of UTC+5:30.
  2. Convert to UTC: 14:00 − 5:30 = 08:30 UTC.
  3. Look up America/New_York's offset on 11 May 2026: EDT (UTC−4).
  4. Apply offset: 08:30 UTC − 4:00 = 04:30 EDT.
  5. Result: 04:30 on the same calendar date.

Source

Sydney (AEST, UTC+10) · 06:00 on 15 Jul 2026

Result

London (BST, UTC+1) · 21:00 on 14 Jul 2026

  1. Sydney in July is AEST (UTC+10) — Australia's southern winter, no DST.
  2. Convert to UTC: 06:00 − 10:00 = 20:00 UTC the previous day (14 Jul).
  3. London in July is BST (UTC+1).
  4. Apply offset: 20:00 UTC + 1:00 = 21:00 BST.
  5. Result: 21:00 on 14 Jul 2026 — one day earlier than the source.

Source

New York · 02:30 on 8 Mar 2026 (DST gap)

Result

Resolved with later disambiguation → 03:30 EDT (07:30 UTC)

  1. On 8 March 2026 New York clocks jump 02:00 EST → 03:00 EDT — 02:30 does not exist on the wall.
  2. Pick the later disambiguation (the Temporal default) — the instant lands after the transition.
  3. Resolve 02:30 with the pre-transition offset (EST, UTC−5): 02:30 + 5:00 = 07:30 UTC.
  4. Format 07:30 UTC back in New York: 03:30 EDT — the clock has skipped forward by one hour.
  5. Treat this as a flag — meetings scheduled inside a DST gap should be rebooked to a real wall time.

Frequently asked questions

Sources & references

Time-zone offsets and DST transitions were last cross-checked against the IANA tzdata edition shipped in current Chrome/Firefox/Safari on 2026-05-11. The data refreshes through your browser's own update cycle.

Related tools

Rate this tool
Be the first to rate

Comments & feedback

Spotted a bug or want an improvement? Tell us — our team reviews every comment, and good ideas get built. Comments are public and anonymous.

Spotted an edge case or want a city added to the picker?

Email me at [email protected] — most fixes ship within 24 hours.