More games at WuGames.ioSponsoredDiscover free browser games — play instantly, no download, no sign-up.Play

GeoJSON Viewer - View & Validate GeoJSON

Free GeoJSON viewer: view, validate and visualize GeoJSON data on interactive map. Display points, lines, polygons. Check GeoJSON syntax and structure.

Upload
Click or drag GeoJSON file here
JSON or GeoJSON format

What is GeoJSON?

GeoJSON is an open standard format for encoding geographic data structures using JSON (JavaScript Object Notation). It supports various geometry types including points, lines, polygons, and multi-part collections of these types.

GeoJSON is widely used in web mapping applications, GIS software, and location-based services. It's human-readable, easy to parse, and supported by most modern mapping libraries and tools.

Key features of GeoJSON:

  • Simple Format: Easy to read and write, based on JSON
  • Widely Supported: Compatible with Leaflet, OpenLayers, Google Maps, Mapbox
  • Rich Data: Can include properties and metadata for each feature
  • Standard Format: RFC 7946 specification ensures interoperability
  • Geometry Types: Points, LineStrings, Polygons, and their Multi- variants

GeoJSON is the preferred format for exchanging spatial data on the web, making it essential for modern web mapping applications.

GeoJSON Structure

A GeoJSON object can be one of several types:

  • FeatureCollection: A collection of Feature objects
  • Feature: A single geographic feature with geometry and properties
  • Geometry: A geometric shape (Point, LineString, Polygon, etc.)

Example GeoJSON structure:

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [105.8342, 21.0278]
      },
      "properties": {
        "name": "Hanoi",
        "population": 8000000
      }
    }
  ]
}

Each feature can have a geometry object defining its shape and location, plus a properties object containing any additional data.

Geometry Types in GeoJSON

GeoJSON supports these geometry types:

  • Point: Single location [longitude, latitude]
  • LineString: Array of two or more positions forming a line
  • Polygon: Array of linear rings (closed LineStrings)
  • MultiPoint: Array of Point coordinates
  • MultiLineString: Array of LineString coordinate arrays
  • MultiPolygon: Array of Polygon coordinate arrays
  • GeometryCollection: Array of geometry objects

Note: Coordinates are always in [longitude, latitude] order, which is opposite of the common latitude, longitude order.

Common Uses of GeoJSON

GeoJSON is used in many applications:

  • Web Mapping: Display geographic features on interactive maps
  • Data Visualization: Choropleth maps, heat maps, marker clusters
  • GIS Analysis: Import/export data between different GIS systems
  • Location Services: Store and query spatial data in databases
  • Open Data: Government and organizations publish geographic datasets
  • Mobile Apps: Offline map data and custom overlays

GeoJSON vs Other Formats

Comparison with other geographic formats:

  • vs Shapefile: GeoJSON is text-based and web-friendly, Shapefile is binary and requires multiple files
  • vs KML: GeoJSON is simpler and faster to parse, KML supports more styling options
  • vs GPX: GeoJSON is more flexible for various geometries, GPX is specialized for GPS tracks
  • vs TopoJSON: GeoJSON is easier to use, TopoJSON is more compact for large datasets

Choose GeoJSON when you need a simple, widely-supported format for web applications and don't require advanced features like topology encoding.

Frequently Asked Questions

Paste, upload, or drag-and-drop any RFC 7946 GeoJSON document and the tool renders it as an interactive Leaflet map. Points, LineStrings, Polygons, MultiGeometries, GeometryCollections, and FeatureCollections are all supported. The map zooms to the data's bounding box on load, you can click any feature to inspect its properties, and you can toggle a basemap layer (OpenStreetMap default, with optional satellite, terrain, and dark-mode tiles). The view runs entirely client-side; no data is uploaded. Common uses include validating a GeoJSON export from PostGIS, previewing API responses during web-map development, and quick spot-checks during data cleaning.

WGS84 longitude-latitude (EPSG:4326), the only CRS permitted by RFC 7946. Coordinates must be decimal degrees with longitude (X) first and latitude (Y) second. If your data is in a projected CRS such as UTM, Web Mercator (EPSG:3857), or a national grid, the geometry will land in the wrong place on the basemap (typically near 0,0 or off the visible map). Reproject the source GeoJSON to WGS84 first using QGIS, ogr2ogr, or a coordinate converter. The viewer does not attempt to autodetect projected coordinates because doing so reliably across all national grids is impractical.

For files under 10 MB, rendering is instant and interaction is smooth. Between 10 and 100 MB, expect 2 to 30 seconds of initial parse and possibly slow zoom/pan; the viewer automatically clusters Points and simplifies LineStrings/Polygons when zoomed out to reduce drawing cost. Above 100 MB, performance degrades sharply because Leaflet keeps a DOM SVG element per feature; consider using Mapbox GL or deck.gl for vector tile rendering instead. For truly massive data (gigabytes), serve it as Mapbox Vector Tiles from a tile server and view through a webmap built on Mapbox GL.

GeoJSON has no native styling concept; the spec leaves styling to the consumer. This viewer supports the Mapbox Simplestyle Specification: properties.stroke (line colour), properties.stroke-width (line thickness in pixels), properties.stroke-opacity, properties.fill (polygon fill), properties.fill-opacity, properties.marker-color (point colour), properties.marker-size (small/medium/large), and properties.marker-symbol (Maki icon name). If these properties are absent, the viewer uses sensible defaults. Custom styles can be applied via a JSON configuration that maps property values to colours or sizes (categorical or quantitative).

GeoJSON polygons are defined with one outer ring and zero or more inner rings (holes), and RFC 7946 requires the outer ring to be wound counter-clockwise and inner rings clockwise (the right-hand rule). If your polygons were exported by a tool that uses the opposite winding (some older ESRI shapefiles converted via mapshaper or older ogr2ogr versions), the viewer may render the hole as solid and the polygon body as transparent. The fix is to reorient the rings; the GeoJSON Validator and Repair tool handles this automatically by detecting and reversing improperly-wound rings.

Yes, once the page is loaded and you have visited a basemap area at least once. The application itself is fully client-side, and Leaflet uses its built-in tile caching for OpenStreetMap basemap tiles. After the first visit, the page works offline, although panning to a previously unvisited area will leave gaps in the basemap. For field work without connectivity, pre-cache basemap tiles by panning around the area of interest while online, then disconnect. The GeoJSON data itself never leaves your browser, so privacy is guaranteed even when reviewing sensitive location data.

Yes. Once loaded, the viewer can export the data as KML, KMZ, GPX, WKT, CSV (one row per feature with coordinates as columns), TopoJSON, or shapefile (zipped). The KML export preserves Simplestyle properties as KML styles where the mapping is unambiguous. GPX export is suitable only for Point and LineString geometries; Polygons are converted to a closed LineString. Shapefile export creates a zipped archive containing the .shp, .shx, .dbf, and .prj files; the projection file is hardcoded to WGS84 because the input is required to be WGS84.

Yes. The entire GeoJSON is parsed, rendered, and queried in your browser; no part of it is uploaded to any server. You can verify this by opening the network tab of your browser developer tools while you upload, view, and interact with the data; the only outgoing requests are for basemap tiles (which only reveal which map area you are looking at, not which features are loaded). For maximum privacy, switch to a basemap that you self-host (or disable the basemap entirely), then no information whatsoever leaves your browser.
GeoJSON Viewer - View & Validate GeoJSON — Free GeoJSON viewer: view, validate and visualize GeoJSON data on interactive map. Display points, lines, polygons. Chec
GeoJSON Viewer - View & Validate GeoJSON