GeoJSON Viewer & Validator
Paste or drop GeoJSON to validate it, see it on a map, and read a feature summary — right in your browser.
Your GeoJSON is validated, summarized, and drawn in your browser and is never uploaded. Only OpenStreetMap map tiles are loaded over the network to render the base map; the geometries you view are not stored on a server.
Need a table instead? Convert GeoJSON to CSV.
About GeoJSON Viewer & Validator
This GeoJSON viewer and validator checks your data and draws it on a map without leaving your browser. Paste GeoJSON, or drop a .geojson or .json file, and it first confirms the text is well-formed JSON and then a valid GeoJSON object — a FeatureCollection, a single Feature, or a bare geometry like Point, LineString, or Polygon. Anything wrong gets a precise message: a JSON syntax position, an unknown geometry type, missing or non-array coordinates, or a ring with too few positions. Valid geometries are rendered with a Leaflet map that auto-fits to the data, and you get a summary of the total features, a breakdown by geometry type, and the overall bounding box. Pretty-print or minify with one click. Coordinates are parsed and drawn on your device, so your data stays with you.
Features
- Validate that input is well-formed JSON and a valid GeoJSON object in one pass
- Accepts a FeatureCollection, a single Feature, or a bare geometry
- Precise errors: JSON syntax, unknown type, missing coordinates, wrong ring arity
- Renders points, lines, and polygons on a Leaflet map that auto-fits the bounds
- Summary of total features plus a count of each geometry type (Point, Polygon, ...)
- Computes and copies the overall bounding box as [west, south, east, north]
- Pretty-print or minify the GeoJSON and copy either with one click
- Drop a .geojson or .json file, or paste text, with a live map preview
How to use the GeoJSON Viewer & Validator
- Paste GeoJSON into the input, or drop a .geojson / .json file (or load the example).
- Read the validation banner: a green result, or a precise error to fix.
- See valid geometries drawn on the map, which fits itself to the data.
- Check the feature count, geometry breakdown, and bounding box in the summary.
- Copy the pretty-printed or minified GeoJSON, or copy the bounding box.
Example
Input
{"type":"Feature","geometry":{"type":"Point","coordinates":[2.2945,48.8584]},"properties":{"name":"Eiffel Tower"}}
Output
Valid Feature · 1 feature
Point: 1
Bounding box: [2.2945, 48.8584, 2.2945, 48.8584]
A single Point Feature validates and drops a pin at the Eiffel Tower in Paris.
Common errors & troubleshooting
- The map is empty even though the GeoJSON looks valid. — Check coordinate order — GeoJSON is [longitude, latitude], not lat/long. Swapped values often land the point in the ocean, off the fitted bounds.
- A Polygon is rejected for having too few positions. — Each Polygon ring needs at least four positions and must be closed, meaning the last coordinate repeats the first. Add the closing point to the ring.
- Validation fails with an "unknown type" message. — The "type" must be a GeoJSON type: FeatureCollection, Feature, or a geometry such as Point, LineString, Polygon, MultiPolygon, or GeometryCollection. Fix the casing or the value.
Frequently asked questions
- What counts as valid GeoJSON in this viewer?
- Input must be well-formed JSON and a GeoJSON object: a FeatureCollection with a features array, a single Feature with a geometry, or a bare geometry like Point, LineString, or Polygon. The viewer checks the type and every coordinate array before drawing it.
- Why does my point appear in the wrong place on the map?
- GeoJSON stores coordinates as [longitude, latitude], the opposite of the lat/long order many maps and APIs use. If a point lands in the sea or another country, your longitude and latitude are almost certainly swapped.
- How is the bounding box calculated?
- The viewer walks every coordinate in the data and tracks the minimum and maximum longitude and latitude, returning [west, south, east, north]. Features with a null geometry contribute no coordinates, so the box covers only the located geometries.
- Which geometry types can it render and count?
- Point, MultiPoint, LineString, MultiLineString, Polygon, MultiPolygon, and GeometryCollection. Points are drawn as pins; lines and polygons are drawn as shapes. The summary shows how many of each geometry type your data contains.
- Does viewing GeoJSON here upload my coordinates anywhere?
- No. Parsing, validation, and the summary run in your browser, so the GeoJSON you paste stays on your device. Only OpenStreetMap map tiles are fetched over the network to draw the base map behind your geometries.
Related tools
- GeoJSON to CSV — Convert a GeoJSON FeatureCollection to CSV and back — Point features become latitude/longitude columns with their properties.
- WKT to GeoJSON — Convert WKT (Well-Known Text) to GeoJSON and back, in your browser.
- KML to GeoJSON — Convert KML ⇄ GeoJSON — turn Google Earth KML into GeoJSON for web maps, or GeoJSON back into KML.
- GPX Viewer — Open a GPX file and see its tracks, routes and waypoints on a map, with distance, elevation and bounds.
- GPX to GeoJSON — Convert GPX to GeoJSON and back — GPS tracks, routes and waypoints to GeoJSON features, or GeoJSON back to a GPX file.
- Coordinate Map Viewer — Plot a latitude/longitude on an OpenStreetMap map, or click the map to read coordinates back out.
All ArrayKit tools