GeoJSON is the friendliest format in GIS and the least friendly to read raw: a text file of nested brackets in which a city boundary and a typo look exactly alike. A GeoJSON viewer is the tool that closes that gap. It parses the file, draws every feature on a map, and lets you click features to read their properties, which turns validation from squinting at coordinates into looking at a picture: the polygon is in the ocean, the points are mirrored across the Atlantic, the file is fine. This guide explains what a viewer actually does, walks the inspection routine that catches the format's classic defects, and compares the main places to open a file, including the privacy distinction that matters when the data is not yours to upload. For the format itself, what the geometry types and properties mean, start with our GeoJSON explainer; this guide is about the looking glass.
Home / GIS and Open Map Data for Beginners
GeoJSON Viewer: Open, Inspect, and Validate a GeoJSON File in Your Browser

Photo: Lukas Blazek / Pexels
See It Before You Trust It: The GeoJSON Viewer Checklist
Check off each step as you finish it. Your progress stays on this page.
0 of 8 complete
0% done
What a Viewer Actually Does
Strip the polish and a viewer performs four jobs. It parses the text as JSON and reports syntax errors with a location, which alone justifies its existence, since a missing comma in forty thousand lines is otherwise a treasure hunt. It interprets the parsed structure according to the GeoJSON specification, RFC 7946: FeatureCollections contain Features, each Feature pairs a geometry, Point, LineString, Polygon, and their Multi- variants, with a properties object. It draws the geometries on a basemap, which requires assuming the coordinates are what the specification says they are: longitude first, then latitude, in degrees, on the WGS84 datum. And it exposes the properties as a readable table or popup when you click a feature. Every strength and every failure of every viewer follows from those four jobs, including the deepest one: a viewer cannot tell you your coordinates are wrong, only draw faithfully the wrongness you gave it, which is why the inspection routine below leans on your eyes.
The Sixty-Second Open
The fastest full-featured route is geojson.io, the browser-based editor-viewer maintained in the Mapbox ecosystem: open the site, drag your file onto the map or paste the text into the code panel, and the features render immediately, with the code and the map kept in sync so you can edit either side. Clicking a feature shows its properties; the table view lists every feature's attributes in rows. For a quick look with nothing to install, that is the whole workflow, and it handles most files a person meets. Heavier or more analytical viewing moves elsewhere: QGIS opens GeoJSON by dragging the file into the layer panel, giving you the full GIS apparatus, symbology, attribute table, reprojection, export to any format, and our QGIS field guide covers that environment. GitHub deserves a special mention: a GeoJSON file committed to a repository renders as an interactive map in the web interface automatically, which makes it the viewer of least resistance for data published as code. And kepler.gl serves the big-data end, GPU-rendered exploration of files far larger than a simple viewer should attempt. Choose by file and purpose: geojson.io to inspect, QGIS to work, GitHub to publish, kepler.gl to explore at scale.
Read the Geometry Before the Map
The map seduces; read the structure first. Check the geometry types match the story: a file of delivery zones should be Polygons, a file of sensors should be Points, and a surprise MultiPolygon where you expected simple shapes hints at a merge upstream. Count the features against expectation, since a viewer that quietly renders 9,412 of your 10,000 features has told you something important if you bother to ask. Open the properties of several features, not one: consistent keys across features mean a clean table downstream, while properties that appear and vanish feature to feature predict pain in any join or filter. Look at coordinate precision as a tell: coordinates carrying fifteen decimal places came from a float pipeline and carry false precision, while pairs rounded to five or six decimals are the sane norm for geographic data. None of this requires the map at all, and doing it first means the map, when you finally look, is a confirmation instead of a surprise.

The Swapped-Coordinates Check
GeoJSON's most famous defect deserves its own drill, because the specification's longitude-latitude order is the reverse of the latitude-longitude order every human learns first, and files get written backwards constantly. The symptoms are distinctive. Points that should cluster in a city scatter across an ocean or a wrong continent. A dataset of France renders as a splatter in the Indian Ocean, mirrored. Latitude values outside the legal range are the mathematical confession: any second coordinate beyond plus or minus 90 cannot be a latitude, so if the file's pairs routinely show second values like 122, the pairs are latitude-first in a longitude-first world. In the viewer, zoom to fit and look at the shape of the whole dataset before any detail: correct data forms the geography you expect, swapped data forms its funhouse reflection, and the whole-extent view makes the difference unmistakable in one glance. The fix belongs upstream, swap the pairs in the generator or with a conversion tool, not in the viewer; the viewer's job is the diagnosis, and it performs it beautifully. Our guide to latitude and longitude formats helps verify individual pairs while you confirm which order a file is really in.
Privacy: Local Parsing Versus Upload
Viewers divide by where the parsing happens, and the difference matters for data that is sensitive, proprietary, or simply large. Browser-local tools like geojson.io parse the file in your browser with JavaScript; the file does not need to leave your machine to be drawn, which makes them suitable for data you could not email to a stranger. Upload-based services send the file to a server for conversion or rendering, gaining power and losing confidentiality, and their terms govern what happens next. Desktop QGIS is the maximally private option: nothing leaves the computer at all. The working rule is proportional: public open data, use whatever is fastest; internal or personal location data, use a local parser or the desktop; regulated data, use the desktop and read your organization's policy before any web tool touches it. File size pushes the same direction, since browser viewers strain at tens of megabytes while QGIS and kepler.gl are built for the heavy end.
From Viewing to Using
A viewer session usually ends in a next step, and the good tools hand you to it. From geojson.io you can save edited data back out as GeoJSON, or as TopoJSON, CSV of points, and other exchange formats. From QGIS the file becomes a layer, and the whole toolbox opens: reproject it, as our reprojection guide teaches, clip it, join it, style it, export it as a shapefile or GeoPackage for other software. The habit worth forming is to treat viewing as inspection with an exit plan: validate the structure, eyeball the geography, check a sample of properties, note the defects, and only then promote the file into your working environment. Five minutes in a viewer, spent in that order, prevents the most common GeoJSON misery of all: discovering, three processing steps deep, that the data was mirrored, truncated, or hollow from the start.
Troubleshooting: When the Viewer Shows Nothing
The empty map is the viewer's most common verdict and it has a short differential diagnosis. First, the file is not valid JSON at all: a truncated download, a trailing comma, a spreadsheet that was renamed rather than exported; the viewer's parse error names the neighborhood of the wound, and a dedicated JSON check confirms it. Second, the file is valid JSON but not GeoJSON: an array of bare coordinates, a single geometry with no type field, a format wearing the wrong extension; open the head of the file and look for the words FeatureCollection, Feature, and a geometry type, whose absence tells you a conversion stands between you and a map. Third, the geometry is real but located somewhere you are not looking: zoom to fit, always, before concluding emptiness, since a viewer opens at its default viewport and your dataset may be a parish in Portugal drawn faithfully at world zoom, invisible in the Atlantic blue. Fourth, the coordinates are legal but swapped, the funhouse case from the earlier drill, recognizable by its mirrored geography. Fifth, the file is simply enormous and the browser is struggling silently; sample the first hundred features into a test file, verify those, and graduate the full dataset to QGIS or kepler.gl. Work the list in order and the blank map resolves into a cause every time, which is the viewer's final lesson: in GeoJSON work, silence is also a diagnosis, if you know the five things it can mean.
Related Guides
The closest companions to this guide are the GIS and open map data guides below. Each one picks up a thread this page starts:
- How to Add a Shapefile in QGIS: The Whole File Family, the CRS Prompt, and the Zip Trick: Adding a shapefile sounds like opening a file, and it is, once you understand that a shapefile is not a file.
- QGIS vs Google Earth: A Viewer and a GIS Are Not the Same Tool: Google Earth and QGIS are both free, both show the planet, and both get recommended for each other's jobs.
- Google Maps in QGIS: The Two Working Routes, and the Licensing Catch You Must Know: You can put Google Maps and Google satellite imagery behind your data in QGIS in about a minute, two ways: an XYZ Tiles connection, or the...
Frequently Asked Questions
What is the best free GeoJSON viewer?
For quick inspection, geojson.io in the browser: drag in a file or paste text, see the map, click features for properties, and edit in place. For serious work, QGIS opens GeoJSON natively and adds the full GIS toolbox. GitHub also renders GeoJSON files as maps automatically.
Why does my GeoJSON render in the ocean or the wrong country?
Almost always swapped coordinates. GeoJSON order is longitude first, then latitude, per RFC 7946. If a file was written latitude-first, features mirror to wrong locations. A quick tell: second values beyond plus or minus 90 cannot be latitudes, so the pairs are reversed.
Does geojson.io upload my file to a server?
geojson.io parses files locally in your browser, so viewing does not require uploading the data. Other online converters do upload files to their servers. For sensitive data, prefer local-parsing tools or desktop QGIS, where nothing leaves your machine.
Can a viewer fix invalid GeoJSON?
A viewer will report JSON syntax errors and show you where parsing failed, and editor-viewers like geojson.io let you correct the text with the map updating live. Structural problems, swapped coordinates, wrong geometry types, must be fixed in the data; the viewer diagnoses, you repair.
What is the difference between GeoJSON and TopoJSON in a viewer?
TopoJSON encodes shared boundaries once, making files smaller, and most simple viewers, including geojson.io, can open and save it. GeoJSON repeats shared borders in every polygon. For viewing and inspection they behave the same; the difference is file size and editing model.
Photo credits: Lukas Blazek (Pexels); Lukas Blazek (Pexels). Photos are served from this site; follow the credit to the library page for the original.