Time Zone Converter
Convert local date and time between worldwide IANA time zones, with city-first labels for easier searching and daylight-saving rules for the selected date.
Use the Time Zone Converter
Convert a local date and time between supported IANA time zones using the browser time-zone database, including daylight-saving rules for that date.
File processing and generation happen locally in your browser; this batch does not require an external processing service.
Results and generated drafts use only the visible inputs. Review the output and source facts before relying on it.
How to use it
Start with the realistic worked example, replace it with your own data or local file, inspect the generated result, and verify the important assumptions before using the output.
How the Time Zone Converter works
The Time Zone Converter translates a local date and clock time between worldwide IANA time zones while accounting for the offset rules that apply on that date. Zone choices are labelled city first, followed by country and the IANA identifier for easier lookup.
Calculation breakdown
ToolLott will explain the current inputs and displayed result here.
How named time-zone conversion works
ToolLott resolves the entered local time against named IANA-style zones rather than applying one fixed hour difference. That matters because locations such as London, Sydney and New York can change offset during daylight-saving periods while Perth and some other zones do not.
target local time = source instant + target UTC offsetThe source local time is first resolved to a UTC instant using the source zone rules for that date.
| Symbol / input | Meaning | Unit |
|---|---|---|
source zone | Named time zone in which the entered local time occurs | IANA zone name |
target zone | Named time zone used for the converted display | IANA zone name |
Step-by-step method
- Validate the local date, time and two different named zones.
- Resolve the source local date/time to a single instant using the source zone offset for that date.
- Format that same instant in the target named zone.
- Return the converted date and time, allowing seasonal offset differences to appear naturally.
Worked example
Priya, a operations coordinator, A Perth project coordinator has a design call booked for 16:00 on 15 January 2026 and needs to tell a London consultant the exact local time without assuming the seasonal offset.
Example inputs
- date = 2026-01-15
- time = 16:00
- from = Australia/Perth
- to = Europe/London
Calculation / processing
15 Jan 2026 16:00 in Australia/Perth corresponds to 08:00 in Europe/London.The same conversion in July gives 09:00 because London is on its summer offset.The verified January result is 15 Jan 2026 08:00 Europe/London.
The result represents the same instant shown on the target location clock. The difference can change through the year where daylight-saving rules apply.
Assumptions
- The browser/runtime time-zone database recognises the selected named zones.
- Historic and future offset rules depend on the time-zone data shipped with the runtime.
Limitations
- Government time-zone rules can change, so very recent legislative changes may require an updated runtime/database.
- Ambiguous or skipped local times around daylight-saving transitions require special care beyond a simple fixed-offset mental calculation.
Common questions
Why can the Perth-to-London difference change during the year?
Perth stays on UTC+8 while London changes between standard time and British Summer Time.
Is a time zone the same as a UTC offset?
No. A named time zone can have different UTC offsets on different dates because of daylight-saving or historic rule changes.
Why must the source and target zones be different?
The converter is intended to show a translation between zones; selecting the same zone would not perform a useful conversion.
Methodology sources
Related ToolLott tools
A realistic way Priya could use this tool
Priya is a operations coordinator.
A Perth project coordinator has a design call booked for 16:00 on 15 January 2026 and needs to tell a London consultant the exact local time without assuming the seasonal offset.
The worked data is explicit: date = “2026-01-15”; time = “16:00”; from = “Australia/Perth”; to = “Europe/London”. From that input set the tool returns 15 Jan 2026 16:00 Australia/Perth = 15 Jan 2026 08:00 Europe/London, so Priya can change one assumption at a time and see what actually drives the output.
The case ends with a measurable/checkable result—15 Jan 2026 16:00 Australia/Perth = 15 Jan 2026 08:00 Europe/London. That is the evidence Priya can use to tell a London consultant the exact local time without assuming the seasonal offset, rather than simply being told the tool was helpful. The page also keeps this limitation explicit: No new external service or backend is introduced.
Fictional scenario using realistic example data. For Ready tools, the worked result is tied to the tested example shown in the tool. Replace the figures with your own inputs and independently verify important professional, financial, legal, health or safety decisions.
What this converter is for
Use it to convert a date and time between worldwide city-based IANA time zones with daylight-saving rules for the selected date.
It sits within ToolLott’s Date & Time collection, where you can also calculate age, date differences and durations, or convert meeting times between worldwide cities and time zones.