CSV to GeoJSON Converter
Convert CSV coordinates to GeoJSON
Convert a CSV containing coordinates into a valid GeoJSON FeatureCollection you can drop into Leaflet, Mapbox, QGIS, or a GitHub map preview. Upload the file and the latitude and longitude columns are detected automatically from common header names.
Every remaining column is carried through as a feature property, so labels, categories, and IDs stay attached to their points and remain available for popups, styling, and filtering on the map.
GeoJSON puts longitude before latitude in each coordinate pair — the reverse of how people write and say them. Getting that backwards silently places your data in the wrong hemisphere, so the ordering is handled for you here.
Drop your file here or browse from your device
Accepts CSV, TSV, TXT. Maximum input: 10 MiB. Files above this hard limit are rejected before local processing.
How to Convert
- Upload your CSV file or paste data containing coordinates
- Confirm the detected latitude and longitude columns, or choose them manually
- Decide whether to include the remaining columns as properties
- Review the GeoJSON and download the file
Features
- Auto-detects latitude and longitude columns from common header names
- Manual column selection when headers are unconventional
- Outputs a valid FeatureCollection of Point features
- Carries remaining columns through as feature properties
- Writes coordinates in GeoJSON order, longitude first
- Skips rows with missing or unparseable coordinates
- Runs entirely in your browser — no upload
Use Cases
- Plot a spreadsheet of locations on a web map
- Prepare point data for Leaflet, Mapbox, or QGIS
- Publish a GeoJSON file GitHub can render as a map
- Turn survey or asset records into mappable features
- Convert an address list with coordinates into map data
Frequently Asked Questions
What column names are detected automatically?
Common variants such as latitude, lat, and y for latitude, and longitude, lng, lon, long, and x for longitude. Anything unusual can be selected manually.
Which order do GeoJSON coordinates use?
Longitude first, then latitude — the opposite of the usual spoken order. Reversing them is the single most common GeoJSON mistake, and it lands your points in the wrong part of the world. The correct order is written for you.
What happens to my other columns?
They become properties on each feature, so names, categories, and IDs stay with their point and can drive popups, styling, and filtering in a mapping library. A cell is only written as a JSON number when it is exactly one, so a 01234 postcode, a 1.2.3 version, and a long ID keep their string form instead of being rounded or truncated.
What if a row has no coordinates?
It is skipped rather than emitted as an invalid feature, which keeps the output loadable by strict parsers.
Can it produce lines or polygons?
It produces Point features. Lines and polygons need ordered vertex lists, which a flat one-row-per-record CSV does not express.
Does my CSV need addresses geocoded first?
Yes. Conversion needs numeric latitude and longitude values; it does not turn street addresses into coordinates, which requires a geocoding service.
Is my data uploaded?
No. The conversion runs in your browser and the file contents are not sent to the app server.