Compare with these zones
| Time zone | Local date and time | UTC offset | Daylight saving time |
|---|
Results follow the time zone rules in your browser's Intl data, so they reflect the database version your browser ships with.
Why Time Zone Conversions Go Wrong
A time zone is more than a fixed number of hours from UTC. It is a named set of rules, maintained in the IANA time zone database, that says what the local clock shows at each moment. Zones change their standard offsets, start or stop daylight saving time, and occasionally switch rules altogether. The same calendar date can map to different offsets in the same zone depending on the season.
The most common mistakes are assuming a zone always sits at one offset, forgetting that a meeting is on a different calendar day in another zone, and mixing up the source zone with the zone you are viewing from. Working from one stored instant, as this converter does, avoids most of them.
Reading the Results Table
The first row is the source zone you entered. Every other row shows the same instant in a target zone. The columns mean exactly what they say, and the table is laid out so you can scan the weekday and date before the time.
| Column | What it shows |
|---|---|
| Time zone | The IANA zone name. The source row is marked as the source. |
| Local date and time | The weekday, date and 24-hour time on the clocks of that zone at the chosen instant. |
| UTC offset | How far the zone is ahead of (+) or behind (-) UTC at that instant, such as UTC-04:00. |
| Daylight saving time | Yes with the extra amount when daylight saving time is in effect, otherwise No. |
A line above the table gives the same instant in UTC, which is handy when you need one reference time to write down.
How the Conversion Works
The page uses only the Intl API built into your browser, with no network requests. Nothing you enter is sent or stored.
Frequently Asked Questions
No. Conversions use the Intl API built into your browser. Nothing you enter is transmitted or stored by this page.
Results follow your browser's time zone database. If a government changes its daylight saving rules, an updated browser or operating system applies the change, and the converter follows it on the next run. Check the date you entered, because some zones are on a different calendar day.
During a spring-forward change some clock times never appear. The converter moves such a time forward by the skipped amount and shows a note. During a fall-back change one clock time occurs twice, so the converter uses the earlier instant and says so.
It compares the zone's UTC offset on the chosen date with the lower of its January and July offsets for that year. A larger offset means daylight saving time is in effect. This matches almost every zone, but it is an inference, not a flag read from the database, so treat unusual historical changes with care.