More games at WuGames.ioSponsoredDiscover free browser games — play instantly, no download, no sign-up.Play

Address Geocoder - Convert Address to Coordinates

Free address geocoder: convert any address to GPS coordinates (latitude/longitude). Get precise location data from street addresses, places, and landmarks instantly.

Examples: 1600 Pennsylvania Ave NW, Washington, DC | Eiffel Tower, Paris | Tokyo Tower

What is Address Geocoding?

Address geocoding is the process of converting a human-readable address (like a street address, place name, or landmark) into geographic coordinates (latitude and longitude). This transformation enables addresses to be plotted on maps, used in navigation systems, and analyzed spatially.

Geocoding is essential for location-based services, mapping applications, logistics, delivery routing, real estate, and any application that needs to translate addresses into precise geographic locations.

Key features of this geocoder:

  • Global Coverage: Search addresses worldwide using OpenStreetMap data
  • Flexible Input: Accept full addresses, partial addresses, landmarks, or place names
  • Multiple Results: Returns top 5 matching locations when address is ambiguous
  • Detailed Information: Provides coordinates, formatted address, location type, and bounding box

How to Use the Address Geocoder

Using the address geocoder is simple:

  1. Enter Address: Type or paste any address, place name, city, or landmark
  2. Click Geocode: Press the 'Geocode Address' button to search
  3. Review Results: View latitude, longitude, and formatted address
  4. Copy Coordinates: Use the copy buttons to quickly copy latitude or longitude values

Geocoding Use Cases

Address geocoding is used in many applications:

  • Mapping & Navigation: Plot addresses on maps, calculate routes, and provide directions
  • Logistics & Delivery: Optimize delivery routes, track shipments, and plan logistics
  • Real Estate: Display property locations, create property maps, and analyze neighborhoods
  • Marketing: Target customers by location, analyze market areas, and plan store locations
  • Emergency Services: Quickly locate addresses for dispatch and response coordination

Understanding Geocoding Results

The geocoder provides several pieces of information for each result:

  • Latitude/Longitude: The precise GPS coordinates of the location
  • Formatted Address: A standardized, complete address string
  • Location Type: The category of location (building, street, city, landmark, etc.)
  • Bounding Box: The geographic area containing the location (useful for map zoom)
  • Multiple Results: When an address is ambiguous, multiple matches are shown for selection

Geocoding Accuracy

Geocoding accuracy depends on the specificity of the input address. More detailed addresses (including street number, street name, city, and postal code) yield more accurate coordinates. Partial addresses or place names may return approximate locations.

This tool uses OpenStreetMap's Nominatim service, which provides high-quality geocoding with global coverage. The service is free and respects user privacy by not tracking search queries.

About Address Geocoder - Convert Address to Coordinates

Address Geocoder turns any street address, landmark, or place name into precise GPS coordinates (latitude, longitude) so you can map it, store it in a database, or feed it into navigation. Built for developers wiring up store-locator features, logistics teams batch-geocoding delivery routes, real-estate analysts geocoding property listings, journalists plotting datasets on maps, and anyone who needs to verify a postal address resolves to the right spot. Runs against OpenStreetMap's Nominatim service for global coverage, returns formatted address, bounding box, and quality grade, and respects rate limits responsibly. Try also our Coordinate Converter and GeoJSON Validator.

Frequently Asked Questions

Geocoding is the process of turning a human-readable address ("1600 Pennsylvania Ave NW, Washington, DC 20500") into a latitude-longitude coordinate pair (38.8977, -77.0365). Under the hood, a geocoder normalizes the input (expanding "Ave" to "Avenue", correcting typos, fixing case), parses it into structured fields (street number, street name, city, postal code, country), and then looks each component up in a reference database such as OpenStreetMap, USPS, TIGER/Line, or a commercial dataset. The match returns a coordinate that is either the exact parcel centroid, the building rooftop, the address interpolated along a road segment, or a fallback to the city/postcode centroid. The geocoder also returns a confidence score and "quality" tag so you know whether you got a rooftop hit or a fuzzy neighborhood approximation.

Several pitfalls. Ambiguous addresses ("Springfield" exists in 30+ U.S. states; "Washington" is both a state and a city); missing context ("123 Main Street" without city or postcode resolves to the most populous match); typos and abbreviations the parser doesn't recognize; rural addresses that aren't in the database; new construction not yet imported; and address interpolation, where the geocoder estimates your position by interpolating along a road segment between two known house numbers — often placing you in the middle of the street or even on the wrong block. Always include city, state/region, and country, and verify the returned coordinate visually on a map. For high-stakes applications like emergency dispatch, prefer geocoders that return a quality grade (rooftop, parcel, interpolated, fallback).

GPS (and GNSS more broadly) is the gold standard: 3-5 m horizontal accuracy with a clear sky view, sub-meter with corrections (RTK, SBAS). Address geocoding accuracy depends on the source — rooftop matches are within ~10 m, parcel centroids ~25 m, interpolated street addresses 50-100 m, and postcode fallbacks 1-5 km. IP geolocation is by far the loosest: country accuracy is ~95-99%, city accuracy 50-80% in dense urban areas and much worse in rural ones, and "precise" IP lookups (claiming street-level) are largely marketing — real accuracy is typically 5-50 km. IP databases also lag by weeks-to-months and routinely fail for mobile networks, VPNs, and corporate proxies. Use GPS for navigation, geocoding for addresses, and IP only for soft signals like language detection or fraud scoring.

Nominatim ("name finder" in Latin) is the geocoder built on top of OpenStreetMap data, maintained by the OSM Foundation. It powers the search box on openstreetmap.org and is free to use under the ODbL license, with a strict usage policy: at most 1 request per second from a single source, a meaningful User-Agent header, and proper attribution ("© OpenStreetMap contributors"). For higher volume, you can self-host Nominatim (full planet import needs ~1.2 TB SSD and 64 GB RAM as of 2026) or use a commercial mirror like Geocoding.ai, LocationIQ, MapTiler, or Geocode.maps.co. Nominatim's quality varies dramatically by region: excellent in Western Europe (mapped by an active community), patchy in parts of Africa, Latin America, and rural Asia. For mission-critical addressing in those regions, supplement with Google, Mapbox, or HERE.

Forward geocoding goes from address text to coordinates: input "Eiffel Tower, Paris" and get back (48.8584, 2.2945). Reverse geocoding does the opposite: input (48.8584, 2.2945) and get back a structured address — "Champ de Mars, 5 Avenue Anatole France, 75007 Paris, France." Reverse geocoding is what powers the "What's here?" feature in mapping apps, automatic location tagging in photo apps, ride-share pickup-point selection, and IoT sensor reports. Both directions share the same address database but reverse uses a spatial index (R-tree, geohash, or PostGIS GIST) to find the nearest feature to the coordinate. Reverse-geocode accuracy depends on density: in a city you may resolve to a specific building, in the desert you may get only a road name or town centroid 50 km away.

That's address interpolation, the cheapest and most common geocoding method. The geocoder knows that house numbers 100-200 lie along a road segment between two endpoints and assumes they are evenly distributed. To geocode 150, it linearly interpolates 50% of the way along that segment, ignoring the actual lot widths, vacant parcels, and corner addresses. The result is usually on the road centerline, sometimes on the opposite side of the street, and occasionally on a completely wrong block when the parity rule (even on one side, odd on the other) is misapplied. To get rooftop or parcel accuracy, use a geocoder that explicitly supports "rooftop quality" — Google's `location_type=ROOFTOP`, Mapbox's `accuracy=rooftop`, or commercial parcel-level providers — and always inspect the returned `match_type` or `quality` field before trusting it.

Three practical paths. First, pick a geocoder that publishes a batch endpoint with bulk pricing — Google's Geocoding API (50 QPS, paid per 1,000), Mapbox (600 QPM with proper plan), HERE Batch Geocoder (up to 1M rows per job), or PositionStack/Geocodio for bulk CSV. Second, self-host Nominatim or Pelias on your own server and stop worrying about per-request quotas; Nominatim handles ~50-200 QPS on a modest VPS. Third, cache aggressively: 60-90% of real-world address lists contain duplicates, so a SHA-1 of the normalized address keyed to (lat, lng) cuts your bill drastically. Always backoff exponentially on 429 errors, randomize request order so you don't hammer one region, and log the raw response — geocoders occasionally change result schemas and you'll want forensic data when something looks off in production.

Most geocoders accept free-form text, but structured input wins. Follow these rules: spell out city and state/region names rather than abbreviating ambiguously ("WA" can mean Washington state, Western Australia, or Washington DC); always include the country (ISO 3166-1 alpha-2 like "US", "GB", "VN" is preferred); put postal codes in the correct national format ("SW1A 1AA" for UK, not "SW1A1AA"); use the local language for street names where supported ("Avenida Paulista" not "Paulista Avenue"); and avoid embedding suite/unit numbers in the street field — they confuse parsers and rarely affect the coordinate. The xAL/PAF standards (ISO 19160) define structured address schemas used by postal authorities; Google's `address_components` array follows a similar pattern. Normalize once, then geocode — round-trip data through `place_id` (Google) or `osm_id` (Nominatim) for stable references.
Address Geocoder - Convert Address to Coordinates — Free address geocoder: convert any address to GPS coordinates (latitude/longitude). Get precise location data from stree
Address Geocoder - Convert Address to Coordinates