Formatters & Code
Google My Maps CSV Formatter & Coordinate Import Checker
Fix Google My Maps CSV and Excel imports locally. Repair semicolon delimiters, swapped lat/lng coordinates, decimal commas, and split 2,000-row batches.
Location data & layer settings
Column Mapping (Auto-Detected — Change to Re-Validate)
Drop your Google My Maps CSV or Excel (.xlsx) file here, or browse
100% Local Browser Validation • Zero External Map Tile Requests • Max 10 MB
Results
What the result means
Prepare a location spreadsheet for Google My Maps without uploading its contents. Map latitude and longitude, a combined coordinate, an address, or a WKT POINT column. The report checks ranges, missing fields, duplicates and the 2,000-row import limit. Coordinate swaps and decimal-comma corrections are opt-in and appear in the report. Invalid locations or malformed rows block candidate downloads; oversized files can be split only after other errors are resolved. The preview uses a local coordinate grid and no map tiles. Verify every correction against your source. Range checks cannot prove that an address exists, that axes inside their overlapping ranges are correct, or that Google will accept an import.
Related tools
Guides
Questions
Why does Google My Maps reject my CSV exported from Excel?
In European, Latin American, and French Canadian Windows/macOS locales, Excel exports CSV files delimited by semicolons (;) instead of commas (,) and formats decimal coordinates with commas (e.g. 48,8566). Google My Maps expects comma-separated columns and dot decimals, causing semicolon files to fail or collapse into a single column.
What is the maximum number of rows I can import into Google My Maps?
Google My Maps enforces a strict limit of 2,000 rows per imported file or map layer. If your spreadsheet contains more than 2,000 locations, Google only imports the first 2,000 rows or displays an upload error. After blocking errors are resolved, our formatter can split larger datasets into numbered 2,000-row batches so you can import them into separate layers subject to your map and account limits.
Why are my pins showing up in Antarctica or the wrong ocean?
This happens when Latitude and Longitude columns are reversed (for example, exported from GIS tools or GeoJSON/WKT workflows that use X/Longitude, Y/Latitude order). When a longitude value between -90 and 90 is read as latitude, pins land in the wrong hemisphere; when a longitude exceeds 90 degrees in the latitude column, Google My Maps drops the pin altogether.
How should WKT geometry columns be formatted for Google My Maps?
Google My Maps supports OpenGIS Well-Known Text (WKT) strings such as POINT (-74.0060 40.7128), other geometry types that this checker does not validate. Unlike standard Latitude/Longitude columns, WKT strictly requires Longitude first followed by Latitude separated by a space, with coordinate pairs separated by commas.
Does this tool send my customer addresses or store locations to Google Maps?
No. Everything runs locally inside your browser using JavaScript and Web Workers. Even the coordinate preview uses a self-contained SVG world graticule with zero external map tile requests.