How to Convert Addresses to Latitude and Longitude in Excel

Updated July 7, 2026 · Geloky team

Excel is where address lists live — customer files, store lists, delivery routes — but Excel itself cannot turn an address into map coordinates. There are three working ways to add latitude and longitude columns to a spreadsheet. Here they are, fastest first, with the honest limits of each.

Method 1 — Batch upload (no code, minutes)

1. Prepare the sheet. One address per row. A single "full address" column is fine; separate street / city / state / ZIP / country columns usually match better.
2. Upload it to the Geloky batch geocoding tool — .xlsx, .xls and .csv are accepted, and you don't need an account to start.
3. Map the columns. Tell the tool which columns hold the address parts.
4. Preview. The first rows are geocoded free and plotted on a map, so you can verify accuracy before processing the whole file.
5. Convert and download. You get the same spreadsheet back with latitude and longitude columns appended. The first 100 records per day are free; beyond that it's $1 per 1,000 records.

This is the right method when the goal is simply "my Excel file, plus two new columns" — no API keys, no request loops, no rate limits to babysit.

Method 2 — Excel formulas calling a geocoding API

Excel for Windows (2013+) can call web services directly:

=WEBSERVICE("https://geocoding-api.example.com/search?q=" & ENCODEURL(A2) & "&format=xml&key=YOUR_KEY")

…then extract fields from an XML response with FILTERXML(). It works, but know the limits before committing a 5,000-row file to it:

• WEBSERVICE is not available in Excel for Mac (older versions) or Excel for the web.
• Every recalculation re-fires every request — easy to burn through an API quota by pressing F9.
• Geocoding APIs rate-limit; a column of simultaneous requests will hit those limits and return errors mid-column.
• Error handling (empty results, ambiguous matches) has to be built formula by formula.

Good for a handful of ad-hoc lookups; painful for whole files.

Method 3 — Power Query

Power Query (Data → Get & Transform) can call a geocoding API with Web.Contents() in M code and parse JSON properly. It solves the recalculation problem and handles errors better than formulas — at the cost of writing M code and still managing API keys and rate limits yourself. If you already live in Power Query, it's a solid option; if not, the learning curve is steeper than the task deserves.

Which method should you use?

• A file of addresses, wanted back as a file: batch upload (Method 1).
• A few dozen lookups inside a live workbook: formulas (Method 2).
• A repeating ETL pipeline in Excel/Power BI: Power Query (Method 3), or better, a geocoding API called from the pipeline.

Frequently asked questions

Can Excel convert addresses to coordinates by itself?

No — Excel has no built-in geocoder. You either call an external geocoding service from formulas or Power Query, or batch-process the file with a tool and download the result.

How many addresses can I geocode for free?

Geloky's free tier covers 100 records per day; after that it's $1 per 1,000. API providers each have their own free tiers and limits.

How accurate are the results?

Complete street addresses typically geocode to rooftop or street level. City-only rows return the city centroid. The cleaner the input, the better the match rate — see our guide on cleaning address lists.