GeoJSON Viewer

updated 25 April 2026

Before you start

You need a GeoJSON snippet or a .geojson (or .json) file. This viewer supports everything in the RFC 7946 spec: FeatureCollection, individual Feature objects, or raw geometries like Polygon and MultiLineString.

I built this specifically for WGS84 coordinates (EPSG:4326). If your data is in a different projection (like UTM or State Plane), it won't render correctly on the OpenStreetMap tiles. You'll need to reproject your data to [longitude, latitude] format first.

There is no hard file size limit, but because everything happens in your browser's memory, very large files (500 MB+) might make the map stutter. If you have a massive dataset, I recommend using the Simplify tool first to reduce the vertex count.

How to use it

1. Paste your GeoJSON text into the left pane, or drag and drop a .geojson file anywhere on the page.
2. Click Render. The map will automatically pan and zoom to fit the boundaries of your data.
3. Click on any feature (point, line, or polygon) to inspect its properties in a popup.
4. Check the status bar at the bottom to see the total feature count and the exact bounding box coordinates.
5. If you switch to another tool in this suite, your data follows you automatically via the session cache.

Example

Input (a simple Point):

{
  "type": "Feature",
  "geometry": {
    "type": "Point",
    "coordinates": [-0.1276, 51.5074]
  },
  "properties": {
    "name": "London"
  }
}

The map will center on the UK and show a marker. Clicking it reveals the name: London property.

Tips & common pitfalls

• Longitude always comes first. The most common mistake is [lat, lng]. GeoJSON follows the [x, y] convention, so it must be [longitude, latitude]. If your markers end up in Antarctica or the middle of the ocean, check your coordinate order.
• The map auto-fits. You don't need to manually zoom to find your data; my code calculates the bounding box of all geometries and centers the view for you every time you hit Render.
• Nested properties are fine. If your feature has complex metadata, the popup will stringify those objects so you can still read them.
• Valid JSON is required. If you miss a comma or a closing bracket, the parser will fail. Use the Validator tool if you're getting syntax errors.

Troubleshooting

Related tools

• GeoJSON ValidatorCheck your data against the RFC 7946 spec for errors.
• Simplify GeoJSONReduce vertex count to make large files web-ready.
• CSV to GeoJSONDrop in a spreadsheet of coordinates and view it as a map.
• KML to GeoJSONBring Google Earth data into the GeoJSON ecosystem.

See also: if you need to do something adjacent on this site, try GeoJSON Formatter to pretty-print or minify a GeoJSON file, GeoJSON to CSV to flatten a feature collection into a CSV table, or GeoJSON to KML to convert GeoJSON to KML for Google Earth.

Frequently asked questions