Show prices in the local currency
Example
See more E-commerce use cases → Visitor from Berlin → 46.228.x.x
country: Germany · currency: EUR → store shows €49, not $49
Use case
IP Geolocation API for Localization & Personalization
Greet every visitor in the right language, currency, and format from their first page view — server-side, no permission prompt.
Your app knows what a visitor wants. IP geolocation tells you where they are — so the language, currency, timezone, and regional content all adapt on arrival. No reload, no pop-up, just the right experience instantly, with the visitor free to override.
Who uses it
The teams that lean on this most, in rough order of how often we see it.
The signals it uses
Every one ships in the standard response — no add-ons, no tiers.
country / countryCode Pick the right locale, currency, and regional defaults on arrival currency Show prices in money the visitor already recognises timezone Correct dates, delivery estimates, and sale countdowns region / city Regional content and nearest-location defaults is_in_eu EU-specific copy, consent banners, and consumer rules How different teams put it to work
The same lookup, tuned to how each kind of team localizes.
Pre-set language and locale on first load
Example
See more SaaS use cases → Visitor from Tokyo → 126.0.x.x
country: Japan · timezone: Asia/Tokyo → UI defaults to JA + local time
Localize any client site with one key
Example
See more Agency use cases → Client site visitor → 2.16.x.x
country: Italy → serves IT locale across the whole client portfolio
Tailor content to the origin market
Example
See more Travel use cases → Visitor from Dubai → 94.200.x.x
country: UAE · currency: AED → prices + offers for the UAE market
Serve the right regional edition
Example
See more Media use cases → Reader from Toronto → 99.239.x.x
country: Canada · region: ON → Canadian edition + local time on timestamps
Route multi-campus portals to the right locale
Example
See more Education use cases → Student from Madrid → 88.6.x.x
country: Spain → ES portal, local term dates and support hours
Common questions
How does IP-based localization differ from browser language settings?
Browser language tells you a preferred language; IP geolocation tells you where the request actually comes from — enough to also pick the right currency, tax rules, timezone, and regional content before the page renders. The two work well together: use IP for sensible defaults, then let the visitor override anything.
Does it need a permission prompt or slow the page?
No. It resolves server-side from the request IP with a median response under 50ms and needs no browser permission prompt, unlike GPS-based geolocation. The right locale is ready before first paint.
What if the detected location is wrong?
Country-level accuracy is very high, but city or region can be null for some IPs. Always treat the detected location as a smart default and let the visitor change currency, language, or region — never lock them in.
Localize on arrival in one request
Free tier: 2,000 lookups/day, no card. Paid plans from $2.50/month. One call per visitor, under 50ms median response.