Alternatives

6 free alternatives to OpenCage

Builders who need more than OpenCage's testing allowance should look elsewhere when daily volume, per-second throughput, or multi-key setup becomes the bottleneck, because the free tier is capped at 2,500 requests per day, 1 request per second, and one API key.

Category: Geocoding APIsVerified

Where OpenCage's free tier stops

OpenCage OpenCage's free tier is built for testing, not scale. It stops at 2,500 geocoding API requests per day and 1 request per second, so bursty apps will hit the wall quickly. Spreadsheet uploads are limited to 100 rows, and only one API key is allowed, which makes it awkward for separate environments or projects. The tier does keep permanent data storage during testing, has no IP restriction, and no CORS restriction, but the request and key limits are the main reason builders start comparing alternatives.

Switch table

OpenCageGeocodifyGeoapify Location PlatformPositionstackGeoKeoZipcodebaseOSMNames
requests per day2,500 geocoding API requests/dayNot stated3,000 credits/dayNot stated2,500 API requests dailyNot statedNot stated
requests per second1 request/sec1 request/secUp to 5 requests/secNot statedNot statedNot statedNot stated
monthly requestsNot stated30,000 calls/monthNot stated100 monthly API requestsNot stated5,000 searches per monthNot stated
upload sizeSpreadsheet uploads up to 100 rowsNot statedNot statedNot statedNot statedNot statedNot stated
API keysSingle API key onlyNot statedMultiple API keysNot statedNot statedNot statedNot stated
support levelBest-effort supportCommunity support includedBest-effort supportNo support includedEmail support includedE-mail supportNot stated
Card required-NoNoNoNoNoUnknown
First paid tier-Starter $49.00 /MonthAPI 10 $59 billed monthlyBasic $9.99 per month or $8.99 if billed yearlyLite $30/moDeveloper $45 / moVaries by usage

The alternatives

Geocodify

FTV 60 / 100

Geocodify's free plan includes 30,000 calls per month, 1 request per second, commercial use, attribution required, and community support. That makes it a straightforward hosted geocoding option for small production uses that are still within modest monthly volume. It also keeps the interface focused on geocoding and related spatial lookups, so the switch is not conceptually large if you already work with forward, reverse, or batch address workflows. It does require attribution and the free plan is still capped, so it is not a fit for unrestricted public use. Switch if your main pain point is OpenCage's one-api-key setup and you prefer a monthly allowance instead of a daily ceiling.

  • Beats OpenCage: Monthly call allowance and commercial use on the free tier
  • Falls short: OpenCage gives a daily quota, permanent data storage during testing, and no credit card required
  • Who should switch: Choose this if you want a hosted geocoding API with a bigger free monthly bucket and can live with attribution.

Geoapify's free plan gives 3,000 credits per day, up to 5 requests per second, multiple API keys, limited commercial use, isochrones up to 15 minutes, isodistances up to 10 km, and best-effort support. For builders who need a broader location platform, that free tier covers more than geocoding alone and offers more throughput headroom than OpenCage. The multiple-key support is especially useful for separating apps, environments, or team workflows. It falls short if you need OpenCage's no-card trial style setup or a higher per-day allowance, since the free tier is still credit-based and commercially constrained. Switch if you want broader mapping tools with more operational flexibility at the free level.

  • Beats OpenCage: Multiple API keys and a broader set of free location tools
  • Falls short: OpenCage offers a clearer testing allowance with 2,500 geocoding requests per day and permanent data storage during testing
  • Who should switch: Choose this if you need more than geocoding and want multiple keys on the free plan.

Positionstack

FTV 46 / 100

Positionstack's free plan includes 100 monthly API requests, forward geocoding, reverse geocoding, HTTPS encryption, and a personal license. It is the lightest-weight option here if you only want a small, simple API surface and do not need support. The free tier is easy to understand and stays focused on basic address-to-coordinate and coordinate-to-address workflows. It falls short of OpenCage on volume by a wide margin, and it is personal use only, so it is not the one to pick for product work that needs commercial rights. Switch to it only when your usage is tiny and you want basic geocoding with minimal setup.

  • Beats OpenCage: Basic forward and reverse geocoding with HTTPS in a very simple plan
  • Falls short: OpenCage's free tier is far larger in request volume and supports testing features like spreadsheet uploads and permanent data storage
  • Who should switch: Choose this if your usage is tiny and personal, and you only need the basics.

GeoKeo

FTV 69 / 100

GeoKeo's free plan includes 2,500 API requests daily, forward geocoding, reverse geocoding, IP and HTTP restrictions, and email support. That makes it a close match for OpenCage's request volume, but with different controls around access management. The daily quota is easy to reason about for apps that run every day rather than by month, and the restriction options may suit teams that want tighter endpoint control. It falls short because OpenCage also gives permanent data storage during testing and no CORS restriction, which can matter in browser-based integrations. Switch if your main need is a daily geocoding allowance with stronger request restrictions.

  • Beats OpenCage: IP and HTTP restrictions on the free tier
  • Falls short: OpenCage adds permanent testing storage and no CORS restriction
  • Who should switch: Choose this if you want a similar daily request cap but care more about access restrictions.

Zipcodebase

FTV 68 / 100

Zipcodebase's free plan includes 5,000 searches per month, 1 concurrent request, up to 10-mile radius or distance searches, private use rights, HTTPS encryption, self-service onboarding, and e-mail support. It is a better fit if your real need is postal-code lookup and distance-based filtering rather than general place geocoding. The free tier also gives a clear concurrency limit and a defined search scope, which can be useful for small internal tools. It falls short versus OpenCage on geocoding breadth and on testing features like spreadsheet uploads and permanent data storage. Switch if your app is really a postal code search product and not a general geocoder.

  • Beats OpenCage: Postal-code search and distance/radius lookup are built into the free plan
  • Falls short: OpenCage is the more direct geocoding API with testing-oriented extras like spreadsheet uploads
  • Who should switch: Choose this if your workflow centers on ZIP or postal-code lookup rather than address geocoding.

OSMNames

FTV 12 / 100

OSMNames' free offering returns 20 autocomplete results per query and supports country-specific autocomplete searches using a lowercase ISO 3166 Alpha-2 country code. It is the narrowest option in this set, but it can be enough if you only need place-name autocomplete and do not need full geocoding infrastructure. Because it is based on OpenStreetMap data, it can fit workflows that start with search suggestions rather than direct address resolution. It falls short of OpenCage on almost every operational axis, including request volume, uploads, storage, and key management. Switch only if autocomplete is the entire job and you want a minimal public endpoint.

  • Beats OpenCage: Country-filtered autocomplete with 20 results per query
  • Falls short: OpenCage covers full geocoding workflows and has far more room for testing use
  • Who should switch: Choose this if autocomplete is all you need and you do not need a full geocoding API.

Two quick picks

Closest drop-in

GeoKeo

GeoKeo is the closest drop-in because it is also a geocoding API with forward and reverse search, and its free tier is similarly sized at 2,500 requests daily. The main workflow change is around access restrictions, but the core usage pattern stays familiar.

Most free headroom

Geoapify Location Platform

Geoapify has the most free headroom because it offers multiple API keys, 3,000 credits per day, and up to 5 requests per second. It gives the broadest free operational room before a team needs to move to a paid plan.

Frequently asked questions

Which alternative is closest to OpenCage for testing?

GeoKeo is the closest in day-to-day usage because it offers the same 2,500 daily request level and both forward and reverse geocoding, though its access controls differ.

Which free tier gives the most room before paying?

Geoapify Location Platform gives the most room overall, with 3,000 credits per day and up to 5 requests per second, plus multiple API keys.

Which alternative is best if I only need a tiny number of requests?

Positionstack is the smallest, simplest option here, with 100 monthly API requests and basic forward and reverse geocoding.

Which option is best if my app is mostly postal-code lookup?

Zipcodebase is the better fit because its free plan is centered on searches, radius/distance checks, and postal-code style lookup rather than general geocoding.

Bottom line

For the most common case, GeoKeo is the best alternative to try first. It stays closest to OpenCage's geocoding workflow, keeps the same 2,500 requests-per-day shape, and includes both forward and reverse geocoding. If you mainly want a familiar replacement without changing how your app talks to the service, it is the most natural switch. If you need more operational room rather than similarity, Geoapify is the better next step.

Read the full listing for OpenCage. Scores use the FTV methodology at /ftv. Browse more alternatives on /alternatives, or head-to-head comparisons on /compare.