Free - No signup - Coordinates stay in your browser

Turn CSV coordinates into a private point map.

Choose latitude and longitude, validate every row, color and size points, inspect the map, then export GeoJSON, KML, or SVG - without tiles, geocoding, or upload.

A CSV coordinate map plots one point per valid WGS 84 latitude-longitude row. This workspace keeps the file local, makes the coordinate roles explicit, reports skipped rows, and exports the reviewed points in standard GIS formats.

01 - How it works

Map coordinates with visible rules.

A useful point map needs more than a converter output. Review the two coordinate roles, see every valid point, audit every rejected row, then decide what properties leave the tab in an export.

i. load

Open CSV or Excel

Drop a file, paste CSV, or use the deliberately imperfect sample. Multi-sheet workbooks stay local while you choose one sheet.

ii. map

Confirm coordinate roles

Choose distinct latitude and longitude columns. Add an optional label, category, and numeric size without hidden value-based guessing.

iii. inspect

Validate and export

Explore the local SVG, use the exact accessible point list, review skipped rows, and download complete GeoJSON, KML, or a presentation-ready SVG.

02 - Why this workflow

A map with an audit trail.

The preview is intentionally schematic. Its job is to reveal coordinate order, range errors, geographic outliers, categories, and export contents before a destination map receives the file.

  • 01

    Header-only suggestions

    Common latitude, longitude, label, category, and size headers are suggested from names only. Private values never drive a hidden semantic decision.

  • 02

    Complete validation

    Every row is checked for numeric decimal degrees and legal ranges. A bounded ledger stays responsive without implying that later rows were ignored.

  • 03

    No map-provider leak

    The land outline and graticule ship with the page. No coordinate, viewport, category, or label is sent to tiles, geocoding, analytics, or another service.

  • 04

    Standards-shaped exports

    GeoJSON receives longitude-latitude Point positions, KML receives longitude-latitude-altitude tuples, and both preserve valid source-row properties.

"See the outlier before the destination imports it."
csvtodashboard.com
Coordinate and privacy notes

Know what the preview does not do.

The map supports WGS 84 decimal-degree points. It does not infer addresses, convert UTM or local grids, draw routes or polygons, or promise street-level cartographic accuracy.

  • Latitude and longitude

    Latitude describes north/south position and must stay from -90 to 90. Longitude describes east/west position and must stay from -180 to 180.

  • Map scale

    Natural Earth 1:110m land is appropriate for a compact world overview. Use a GIS or destination map when you need streets, parcels, boundaries, or projected coordinates.

  • Export privacy

    GeoJSON and KML intentionally keep every source property for valid points. Inspect the output and remove fields that should not travel with the locations.

03 - FAQ

CSV map questions.

How do I plot CSV coordinates on a map?
Load or paste the CSV, choose separate latitude and longitude columns, review every invalid row, optionally choose label, category, and size columns, then inspect the local point map or download GeoJSON, KML, or SVG.
The workspace accepts WGS 84 decimal degrees: latitude from -90 to 90 and longitude from -180 to 180. It does not geocode addresses or convert projected coordinate systems.
The CSV may keep them in separate columns in either order because you map them explicitly. GeoJSON output stores positions as longitude then latitude, and KML writes longitude,latitude,0.
Blank, non-numeric, and out-of-range latitude or longitude values are reported with source row numbers and skipped. Every row is validated even when the visible issue table is bounded.
Yes. Choose a categorical column for color and a numeric column for relative radius. A visible legend and exact point table keep category identity available without relying on color alone.
No. The preview uses a checked-in simplified Natural Earth land outline, local SVG graticule, and browser-rendered points. It makes no tile, geocoder, viewport, or file-derived request.
Every original source property on each valid point is preserved. That is useful for downstream inspection but may include sensitive data, so review the exported file before sharing it.
No. Parsing, mapping, validation, rendering, selection, and export happen in the browser tab. Audience measurement receives the pathname only, never map data or interaction payloads.