Convert a date and time between any two IANA time zones with correct daylight-saving handling. Reads the wall clock in the source zone. Runs in your browser.
Runs entirely in your browser — your data never leaves your device.
How to use Timezone Converter
What it does & when you need it
You are scheduling a call across continents, reading a UTC log line, or planning a
release window, and you need to know what a given time is somewhere else — with
daylight saving handled correctly. This tool reads the date and time you enter as
the local clock time in a source zone, pins it to a single instant, and shows that
instant as the wall-clock time in a target zone. It draws on your browser's Intl
date engine and the full IANA time-zone database, so conversions are accurate and
private.
How to use
Enter a date and time in the field — it is read as local time in the
From zone.
Choose the From and To zones in the toolbar, or press ⇄ to swap
them. Your own zone is detected on load.
The converted time and a readable, zone-aware label appear below. Press
Copy result (or Ctrl/Cmd + Enter) to copy it.
Things worth knowing
Wall clock in, wall clock out. The tool does not just add a fixed offset; it
figures out which instant your entered time refers to in the source zone and then
renders that instant elsewhere. This is what makes "2:30pm in New York" resolve to
the right time in London whether or not either place is on summer time.
Daylight saving is per-instant. New York is UTC−5 in January but UTC−4 in
July, so the same city differs by an hour depending on the date. Because offsets
are looked up for the specific moment, a fixed numeric offset would be wrong half
the year — a classic scheduling bug.
IANA names carry the rules. Identifiers like Europe/Paris or Asia/Kolkata
encode a region's entire history of offsets and DST changes, unlike a bare
abbreviation such as "EST". Around a fall-back transition one local hour repeats;
the tool resolves to a single valid instant and the label shows the zone
abbreviation. For durations and machine timestamps, pair this with the
Unix timestamp converter.
Examples
A meeting time across zones
2026-07-02T14:30
Enter a local time, then set the From and To zones (say New York → London) to read the matching wall clock.
A UTC log timestamp to local
2026-01-15T12:00
Convert a winter UTC time into a zone with DST and compare it with a summer date to see the offset change.
Near a DST boundary
2026-11-01T02:30
A time close to a fall-back transition still resolves to the correct instant in the target zone.
Frequently asked questions
How does the tool interpret the time I type?+
The date and time you enter are read as the local wall-clock time in the “From” zone — the time a clock on the wall there would show. The tool resolves that to a single instant on the global timeline and then re-displays it as the wall-clock time in the “To” zone, so 2:30pm in New York becomes the correct local time in London or Tokyo.
Does it handle daylight saving time?+
Yes. Offsets are looked up for the specific instant rather than assumed, so a July conversion for New York uses UTC−4 (EDT) while a January one uses UTC−5 (EST). This is why converting with a fixed numeric offset is unreliable: the same city can be an hour apart depending on the date.
What is an IANA time zone?+
IANA (tz database) identifiers are names like America/New_York, Europe/Paris, or Asia/Kolkata. Unlike a bare abbreviation such as “EST”, each identifier carries the full history of that region’s offsets and daylight-saving rules, which is what makes an accurate, date-aware conversion possible.
What about the ambiguous hour when clocks fall back?+
On the autumn transition one local hour repeats, and on the spring transition one hour is skipped. For a repeated time the tool settles on a single valid instant, and the readable label shows the resulting zone abbreviation so you can see which side of the change you landed on. For anything time-critical, storing in UTC avoids the ambiguity.
Is any of this sent to a server?+
No. All conversions use your browser’s built-in Intl date engine, so the times you enter stay on your device and the tool keeps working offline once the page has loaded.