Time Zone Lookup

Instantly find the current time, UTC offset, and daylight saving status for any city worldwide. Perfect for travel, business calls, global scheduling, and programming—never get caught out by time zone confusion again.

A collage of world clocks and digital time displays showing different cities, suggesting global time zone lookup

Time zone lookup is essential whether you're planning a virtual meeting, booking a flight, scheduling a global online event, or programming date/time logic. With hundreds of time zones and local daylight saving rules, finding the right local time—and knowing if a city is observing DST—can be tricky. Our tool gives you instant answers, accurate for 2026 and beyond.

Who needs a time zone lookup? Anyone working with teams across continents, traveling internationally, running global businesses, or building apps that handle time and dates. Our tool helps you:

  • Check the current time and UTC offset for any city or country.
  • See if daylight saving time (DST) is in effect and when it changes.
  • Get official time zone names (IANA/Olson database) for programming or documentation.
  • Reference a global table of major city time zones for at-a-glance planning.
Tip: For advanced conversions, try our Timezone Converter or Date Time Converter.

Quick Links

Interactive Time Zone Lookup Tool

How does this work? Type a city or country, or select from the list. Results include current time (accounting for daylight saving), UTC offset, and IANA time zone name. Data is based on the latest IANA time zone database and browser time.

Major World Cities and Their Time Zones

Sortable table of major cities, countries, time zones, UTC offsets, and DST status
City Country Time Zone UTC Offset Daylight Saving? Current Time
All times and DST statuses are based on current date and IANA database. For advanced conversions, use our Timezone Converter.

Practical Tips for Handling Time Zones

For Software Developers
  • Use official IANA time zone names (America/New_York, Europe/Berlin, etc.) in your code and databases.
  • Treat all server-side timestamps as UTC; convert for display only.
  • Use robust time libraries (e.g., moment-timezone, date-fns-tz, Intl.DateTimeFormat in JS) for conversions and DST handling.
  • Avoid hardcoding offsets—DST and time zone rules change!
See our Date Time Converter for parsing/formatting.
For Travelers
  • Check time zones before booking flights or meetings to avoid confusion across borders.
  • Remember, some countries (e.g., India, Nepal) use half-hour or 45-minute offsets.
  • Not all countries observe DST—and DST start/end dates differ.
  • Always confirm local time before important calls or appointments.
Tip: Use your device's "world clock" feature for quick checks.
Remote Teams & Global Calls
  • Schedule meetings in UTC to avoid ambiguity; let team members convert to their local time.
  • Rotate meeting times to fairly accommodate global participants.
  • Share links to tools like this one to help everyone check times easily.
  • Be mindful of holidays and DST differences when planning recurring events.
See our Timezone Converter for more coordination features.

FAQ: Time Zones, UTC, and Daylight Saving Explained

UTC (Coordinated Universal Time) is the modern global time standard, based on atomic clocks and not affected by daylight saving. GMT (Greenwich Mean Time) was the older standard based on the mean solar time at Greenwich, London. For most practical purposes, they are equivalent, but UTC is preferred for technical, legal, and scientific contexts.

Some countries (like India, Iran, Nepal, and parts of Australia) use time zones offset by 30 or 45 minutes instead of whole hours. This is due to historical, political, or geographic compromises to better align local time with solar noon or national policies. Always check the exact UTC offset for your destination!

Daylight Saving Time (DST) shifts the local time—usually by one hour—during part of the year. Not all regions use DST, and start/end dates differ by country. Scheduling across DST boundaries can cause confusion. Always specify the time zone (and whether DST is in effect) when setting meetings or deadlines. Our table and tool show the current DST status for each city.

Device clocks can be incorrect if they haven't updated their time zone database, if the device’s location is set incorrectly, or if you’ve crossed a border without syncing. Some systems require manual DST changes. Always double-check with an authoritative world clock, especially after travel or when scheduling across time zones.

Always store and process time in UTC on the backend; only convert to local time for display. Use IANA time zone names, not hardcoded offsets, since rules change. Use established libraries for all conversions, and test with edge cases (DST shifts, leap years, etc.). For user input, ask for both time and location or time zone.

Our lookup tool and table display the current DST status for each city, based on the latest IANA time zone database. If "Yes," the local time includes the DST adjustment. For future or historical dates, use a time zone conversion tool that lets you pick a specific date.