Batch Geocoding
Turn a whole list of addresses into coordinates — or a list of coordinates into addresses — in one run. The queue runs in your browser at a polite ~1 request/second against your own free API key, so your file never touches our server and progress survives a pause.
The key is kept in this browser only (local storage) and is used to call the API directly from your device.
| # | Input | Latitude | Longitude | Match |
|---|
How it works (and why your file stays private)
Everything runs client-side: your CSV is parsed in the browser, each row is sent one-by-one to the same developer API you could call yourself, and results accumulate in the table below. The server sees individual geocoding queries under your key's normal rate limits — never your file, never the batch as a whole. Close the tab and nothing remains anywhere.
The queue deliberately runs at ~1 request/second to respect the upstream OpenStreetMap geocoder (and your key's 60/minute limit). 500 rows therefore takes about 9 minutes — you can pause and resume at any point, and failed rows can be retried at the end.
Input formats
- Forward mode: one address per line —
221B Baker Street, London. A CSV works too: the whole line is treated as the address (headers likeaddressare skipped automatically). - Reverse mode: one coordinate pair per line —
28.6139, 77.2090(decimal or DMS). - Limits: 500 rows per run (fair use). Bigger jobs? Split the file, or read our advice for high-volume work in the API docs — hammering a free community geocoder with 50,000 rows is what commercial geocoders are for.