GeoJSON Validator
Find out whether your GeoJSON follows the standard, and exactly where it does not. Checks geometry types, positions, closed polygon rings and coordinate ranges. Done in your browser.
- Use it as often as you like
- Private by design
- Checks RFC 7946 rules
- Errors with JSON paths
- Runs on your device. Files are never uploaded.
- Free and unlimited. No sign-up, no watermark.
GeoJSON validator in three steps
No account, no email, no waiting for an upload.
- STEP 01
Paste or open your GeoJSON
Use a .geojson, .json or .txt file, or paste into the box.
- STEP 02
Run the check
The text is parsed as JSON first, then checked against the GeoJSON rules.
- STEP 03
Read the report
You get a verdict, a count of what the file contains, and a list of errors and warnings with their paths, such as $.features[2].geometry.
What GeoJSON validator does, and what it doesn't
We'd rather tell you up front than surprise you after the download.
What you get
- Structure checksFeatureCollection, Feature and all seven geometry types are checked for required members: type, coordinates, geometries, geometry and properties.
- Position checksEach position needs at least two finite numbers. Longitude and latitude outside the valid range raise a warning, which often means swapped or projected coordinates.
- Polygon ringsLinear rings need at least four positions and must be closed. Counter-clockwise outer rings and clockwise holes are expected, and flagged as warnings if reversed.
- Other membersbbox shape, the Feature id type and the obsolete crs member are checked.
- A summarySee how many features and geometries of each type the file holds, and how many numbers each position has.
Good to know
- No geometric topologySelf-intersecting polygons, overlapping rings and antimeridian crossings are not tested.
- Errors versus warningsWinding order and out-of-range values are warnings, because many real files break these guidelines and still work.
- Up to 500 issuesThe list is cut after 500 entries. Fix the first batch and run again.
Your data never leave your device
The tool runs inside your browser instead of on our servers, so there is nothing to upload, store or delete afterwards.
Typical online tool upload
Your file travels over the internet, sits on someone else's computer for a while, and you wait for the upload and the download.
Mediaextractr no upload
The tool loads into your browser once, then works on your file locally. Nothing is sent, so nothing can leak.
When people use GeoJSON validator
Debug a map that will not load
Find the polygon that is not closed or the missing properties member.
Check exports from GIS tools
Confirm output meets the standard before using it in a web map.
Review a downloaded dataset
See what a file really contains.
Learn the format
Test small examples and read the explanations.
Mediaextractr vs typical upload tools
| MediaextractrPrivate | Typical upload tools | |
|---|---|---|
| Your file is uploaded | Never | Yes |
| Sign-up needed | No | Often, after a few files |
| Daily file limit | None | Often 1–2 free files |
| Watermark | Never | Sometimes |
| Wait for upload & download | No | Yes |
| Speed on very large files | Depends on your device | Depends on their servers |
The rules in short
GeoJSON positions are [longitude, latitude], in that order, in the WGS 84 coordinate system. A Polygon is a list of linear rings. The first is the outer boundary and the rest are holes. Each ring must end where it begins.
RFC 7946 removed the old crs member, because coordinates are always WGS 84. A file that still has one gets a warning.
Frequent problems
Most map errors come from a short list:
- Latitude and longitude swapped, giving points in the wrong place.
- A polygon ring that is not closed.
- A Feature without a properties member (it may be null, but must exist).
- Coordinates in a projected system such as Web Mercator, with huge numbers.
- Convert valid files to records with GeoJSON to JSON, or check plain JSON syntax with the JSON validator.
A quick example
A Point written as [77.59, 12.97] passes. A point at [200, 10] gets a range warning, because longitude cannot go beyond 180. Swapped coordinates are not always detectable, since both numbers may be valid, so always confirm that longitude comes first. Features that land in the wrong ocean usually have this mistake.
Questions, answered
How do I validate a GeoJSON file?
Paste it here and read the report. It lists errors and warnings with their paths.
Is my map data uploaded when I validate it?
No. The GeoJSON is checked by script in this tab, so locations of sites, assets or people stay on your device.
Which standard does it check?
RFC 7946, the GeoJSON specification.
Why is a ring flagged as clockwise?
RFC 7946 says outer rings should run counterclockwise and holes clockwise. This is a warning, not an error.
Does it fix problems for me?
No. It reports them so you can fix the source.
Does it work on a phone or tablet?
Yes, from a phone or tablet browser. Large files may be slow on older devices.