Detected zone
What Is My Timezone
Your browser IANA zone, UTC offset, and whether DST is in effect.
My time zone
Calculate to read this device’s zone; optionally compare a city.
This page reads the IANA time zone that the current browser reports, then prints the UTC offset and daylight-saving status for a date you choose. The identifier looks like America/Chicago or Europe/London. It is the same name operating systems and programming libraries use, not a marketing label such as Central Time. Detection uses the JavaScript Intl API on this device. Nothing is uploaded for a typical lookup.
What the browser actually reports
Modern browsers expose resolvedOptions().timeZone from Intl.DateTimeFormat. That string is an IANA zone from the tz database. The page shows it as soon as you calculate. If a locked-down or very old client hides the zone, the result says the browser did not expose one, and offset math cannot start from a real identifier.
The zone is a property of this device and its OS settings, not of your mailing address. A laptop left on a European zone after a trip still reports that zone until the system clock is changed. A virtual machine can report UTC even when the host sits in another country. Treat the printed name as “what this session believes,” then confirm against the clock in the system tray if the two disagree.
IANA names are stable enough to store in appointment software. Abbreviations such as CST are not. CST can mean Central Standard Time in North America or China Standard Time. If a form asks for a zone, paste the IANA string from this page rather than a three-letter code. The time tools hub collects related clocks that also speak IANA names.
Offset on a chosen date
UTC offset is not a permanent sticker on a city. Chicago is UTC−6 in winter and UTC−5 in summer. The page evaluates noon in the detected zone on the date in the form so the printed offset matches that civil day, including any daylight-saving rule that applies then. Changing the date and calculating again is how you inspect a future travel day or a past log line.
Offsets print in hours and minutes. India is UTC+5:30; Nepal is UTC+5:45; Adelaide is UTC+9:30 or UTC+10:30 depending on the season. A whole-hour mental model fails for those zones. If you only need how far two named cities sit apart on one date, open world clock for many simultaneous readings, or use the dedicated two-city difference page rather than this detector.
The offset is computed for a single instant (noon in the detected zone). That avoids the ambiguous hour in the autumn fallback, when local 1:30 can exist twice. For legal filing times that fall inside a fallback hour, record both the IANA name and UTC, not the wall clock alone.
Daylight saving on versus off
The page compares January and July offsets for the same zone and year. If those two offsets differ, the zone observes a seasonal change. The date you picked is then labeled as daylight saving in effect or as standard time, depending on which offset is the larger (more eastward) one. Arizona (America/Phoenix) and Hawaii typically show no seasonal change. Much of Europe and the United States do.
Governments change DST rules. The browser uses the tz data shipped with the OS or the browser itself. A device that has not received updates may still think a country starts DST on an old date. After a law change, update the operating system before trusting the on/off line for a planning date months ahead. Historical dates before a zone existed under its current name can also disagree with paper archives.
DST is not the same as “summer.” In the southern hemisphere the long-offset season falls in December and January. The January versus July comparison still detects a change; the on/off label follows which offset is in force on your chosen date, not a northern-hemisphere season name.
Optional city comparison
A city picker on this page is only a side check. It prints that city’s IANA name and offset at the same instant, then says how many hours this device sits ahead of or behind that city. It does not replace a two-city difference tool, and it does not list a dozen clocks at once. Use it when you already know “my laptop” and want one counterpart such as a client office.
If both sides show the same offset, you can still be on different dates near the International Date Line. Offset equality is not “same local calendar day.” For scheduling a call across many offices, the meeting planner is the better surface because it shows overlapping work hours rather than a single gap.
VPNs, phones, and wrong zones
A VPN changes the apparent IP address. It does not, by itself, change the IANA zone the browser reports. The zone still comes from the OS. People who assume “the VPN city is my time zone” will misread this page. Conversely, a traveler who set the phone to automatic zone while roaming will see the visited zone, which is usually what they want for local appointments.
Some corporate images freeze the zone to UTC for log consistency. Developers on those images should not copy the printed zone into customer-facing copy. Dual-boot machines can disagree between operating systems. Always read the identifier after the environment you will actually use for the meeting or the deploy.
Browser privacy modes do not typically hide the time zone; the clock is considered necessary for the page. Fingerprinting concerns exist in the wider web platform, but this tool only displays what the engine already resolved. No extra probe beyond Intl is required.
Where this job stops
This detector answers three questions: which IANA name this browser has, what UTC offset that name uses on the chosen date, and whether DST is on. It does not convert an event wall time in city A into city B. It does not list current clocks for a watchlist of capitals. Those jobs live on neighboring pages so each URL stays single-purpose for search and for bookmarks.
Support tickets that say “the site is one hour wrong” often start here. If the printed IANA name is unexpected, fix the device clock first. If the name is correct but a web app still disagrees, the app may be storing a fixed offset instead of a zone name. Ask the vendor which identifier they persist.
Printable month grids still help when you plan around the detected zone: open monthly calendars or the yearly calendar 2026 after you know which zone the laptop is using. Civil holidays for the same year sit on the holidays calendar 2026.
Related tools
Many simultaneous city clocks belong on world clock. Finding a shared meeting hour belongs on the meeting planner. Duration between two clock faces, without zones, belongs on the hours calculator.
Frequently asked questions
What IANA identifier does the browser report for this device?
The page prints the IANA name from Intl.DateTimeFormat, such as America/Chicago or Asia/Kolkata. That string comes from this device’s operating system, not from your IP address or mailing address. If the browser hides the zone, offset lines cannot be filled from a real identifier and the result says so.
How is the UTC offset calculated for the chosen date?
The offset is evaluated at noon in the detected zone on the date in the form. That instant includes whatever daylight-saving rule the zone uses that civil day. Changing the date and calculating again shows travel days or past log dates. Offsets can include 30- or 45-minute fractions, not only whole hours.
When does this page say daylight saving is in effect?
Daylight saving is reported as on when the zone’s January and July offsets differ and the chosen date uses the larger offset. If January and July match, the zone has no DST change that year. Southern-hemisphere summers still follow the same on-or-off test; the label is not a northern season name.
Why can two computers in one city show different zones?
Each device reports its own OS setting. A laptop left on a European zone, a VM frozen on UTC, or a phone set to automatic roaming can disagree while sitting on the same desk. VPNs change IP geolocation but typically do not change the IANA name the browser exposes. Confirm the system clock tray if results look wrong.
Is this the same as looking up many cities at once?
No. This detector is for the current browser session, with an optional one-city comparison. A watchlist of capitals belongs on the world clock. Hours between two named IANA cities on a chosen date belong on the time-zone difference page. Meeting overlap across work hours belongs on the meeting planner.
How do I compare my offset with another listed city?
Pick a city in the optional list and calculate. The result adds that city’s IANA name and offset at the same instant, then states how many hours this device is ahead or behind. Equal offsets do not guarantee the same calendar date near the International Date Line. Use a two-city tool when both sides are named cities.