A timezone API takes a city, a pair of coordinates or an IP address and hands back the local time zone and UTC offset, so you never maintain time zone data yourself. Choose by the input your app already holds, then decide whether you want a dedicated time API or an endpoint inside a location platform you already use.
The input you start from narrows the field before you've read a single feature list. A booking form that asks for a city, a mobile app with a map pin and a website that only knows a visitor's IP address need three different kinds of lookup, and the wrong one adds a conversion step you'll be debugging for months.
Timezone lookups by the input they start from
| Type of lookup | What you send | Check before you commit |
|---|---|---|
| Coordinates lookup | Latitude and longitude from a map pin, a device or an address you've already geocoded | That the response returns the UTC offset as well as the zone name |
| IP address lookup | The visitor's IP address, with nothing typed by the user | What comes back for a VPN, an office network and a mobile connection |
| City or place name lookup | A city the user types or picks from a list | How it handles cities that share a name in different countries |
| Endpoint inside a bigger platform | Whatever that platform's other APIs already take | Whether you're signing up for a whole platform to use one call |
| Free database plus API | Lookups against a published time zone database | Who keeps your copy current and how you'll hear about changes |
I'd fill that table in for your own app before looking at vendors at all. Once you know which row you're in, the shortlist writes itself.
Why the input matters more than the brand
Coordinates are the most direct route. If you already hold a latitude and longitude, from a map, a device or an address you've turned into a point, a coordinates lookup gives you the zone with no guessing about which city someone meant. If you're starting from addresses, it's worth pairing this with one of the geocoding APIs so the point is right before you ask for its zone.
City names feel friendlier and they're the riskiest input. Plenty of towns share a name across countries and states, so a city lookup is only as good as the way your form makes people pick one. A dropdown that includes the country beats a free text box every time.
IP lookups need nothing from the user, which is why they're tempting for a website that wants to show local times on arrival. They tell you where the connection appears to come from, not where the person is, so treat the result as a sensible default and let people change it. If you're already paying for an IP data service, check its response first: you may have a timezone field already, and my roundup of IP geolocation APIs covers that side in more depth.
IPGeolocation.io is one service that takes all three inputs, an IP address, coordinates or a city, through one time zone API.
A dedicated time API or an endpoint in a platform
The second fork is about how much you're taking on. A dedicated time API does one job and keeps your dependency small. A time zone endpoint inside a broader product is handy when you already use that product for maps, location or a bundle of utility APIs, because there's one key, one bill and one set of docs.
Abstract's endpoint sits within a time, date and timezone API, Google's is part of Google Maps Platform and Geoapify's belongs to a location platform.
My view: if your app already calls one of those platforms, use its endpoint and save yourself another vendor. If it doesn't, don't adopt a whole location platform for a single lookup; a dedicated service or a free database is lighter.
TimeAPI links its documentation to the IANA timezones list, the naming scheme behind zone names such as Europe/London.
Whichever you pick, store that zone name alongside each booking or reminder, not only the offset. A name lets you work the offset out again for any future date.
Ten timezone APIs worth a test
TimeZoneDB
Describes itself as a free time zone database for the cities of the world, and offers its own API for lookups against it.
Abstract Time and Timezone API
Getting and converting times, dates and time zones is the job here, and it's one tool in Abstract's wider API suite.
IPGeolocation.io
Time zone lookups and time conversion from whichever input you hold: an IP address, a pair of coordinates or a city.
TimeAPI
A dedicated time and timezone API whose documentation includes a list of IANA timezones.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
timeanddate API
Developer API services from the timeanddate site, the same people who run its world clocks and time zone news.
API Ninjas Timezone
One endpoint in API Ninjas' collection, reachable by AI agents through an MCP server as well as a normal API key.
GeoNames
A geographic database first, its web services include a timezone lookup that takes a latitude and longitude.
Geoapify Timezone API
Send coordinates and get back the time zone and the exact UTC offset, as part of a broader location platform.
Google Time Zone API
The time zone endpoint inside Google Maps Platform, documented alongside its other location APIs.
IPinfo
An IP data service whose lookup response carries a timezone field next to location and network details.
A clock-change test you can run in an hour
Don't trust any vendor's description of how it handles daylight saving. Test it. Pick a place in a country that changes its clocks and another in a country that doesn't. Ask two shortlisted APIs for the zone and offset at each place, then repeat with timestamps the day before, the day of and the day after the next clock change. If an API won't take a timestamp at all, note that, because it can only tell you about right now.
Add the awkward cases while you're there. Send coordinates close to a border between two zones, a city name that exists in more than one country and an IP address from a VPN. Compare the zone names as well as the offsets. Two services that agree on the number but disagree on the name will cause you trouble later, and you'd rather find that on a test sheet than in a customer's diary.
Finally, time the calls. A lookup that runs while someone fills in a booking form needs to answer quickly, so measure a batch rather than the first request.
What timezone lookups cost
This list doesn't quote prices because they change, so check each pricing page for the current plans and limits. Where a vendor offers a free key or a free database, use it for the test above before you commit. A free self-hosted database moves the cost from a bill to your own time: someone has to keep it current. Ask any hosted service how many lookups your plan allows and what happens when you go over, then work out how many you'll make. If you store the zone name once per user or booking, you may need far fewer calls than you think.
Do you make timezone or time APIs? Tool makers can ask to be considered for a featured place on this list.
Where I'd start
For a scheduling or booking feature where users pick their city, I'd start with a lookup that takes a city or coordinates, and make the form force a country. For a website that wants to greet visitors in local time, start with the IP data you may already have and let people correct it.
For an app that already runs on a big location platform, use that platform's endpoint. For a small side project or an internal tool, a free database with an API is enough. And if what you're building is really a booking page, you may not need an API at all: one of the meeting schedulers already does the time zone work for you.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.


