GeoJSON and Shapefile are the two formats every GIS user meets first, and choosing between them is one of those small decisions that quietly shapes your whole workflow. The Shapefile is the old standard, invented by Esri in the 1990s and still the default export in many tools. GeoJSON is the web-native challenger, a plain-text format that any browser, any JavaScript map library and most modern GIS tools can read. Both store the same thing, points, lines and polygons with attributes, but they do it in very different ways, and the right choice depends on where your data is going.

What Is a Shapefile, Really?

A Shapefile is not one file. It is at least three, and usually more: a .shp file holding the geometry, a .shx index, a .dbf file holding the attributes in an old dBase format, and often a .prj file for the coordinate system and a .cpg file for the character encoding. Lose any one of them and the dataset breaks, which is why emailing a Shapefile means zipping the whole folder. The format has real limits: field names are capped at 10 characters, so population_density becomes populatio, it cannot store NULL values properly, it has no support for curved geometries, and it tops out at 2 GB. Despite all of that, it remains the most widely supported vector format in GIS, and almost every desktop tool reads and writes it without complaint. Its durability is its strength: a Shapefile from 2005 still opens today.

What Is GeoJSON?

GeoJSON is a single plain-text file written in JSON, the same format the web runs on. A point in GeoJSON looks like a small block of readable text with coordinates and properties, and you can open it in any text editor and understand what you are looking at. It has no field-name limit, it handles NULL values properly, and it is the native format of web mapping libraries such as Leaflet and MapLibre, which means a GeoJSON file can go straight into a web map with no conversion. Its weaknesses are size and speed: because it is text, a GeoJSON file is much larger than the equivalent Shapefile, and it is slow to load for large datasets. It also has no built-in spatial index, so a desktop GIS has to scan the whole file to find anything. For small to medium datasets, those weaknesses do not matter. For a national road network, they do.

Side by Side: The Practical Differences

On file handling, GeoJSON wins: one file, human-readable, easy to version in Git, easy to email. On compatibility with old desktop workflows, Shapefile wins: it is the default in ArcGIS, QGIS and most government data portals, and it is what your colleagues expect. On attribute handling, GeoJSON wins: long field names, proper NULLs, nested properties and Unicode text all work without the dBase quirks that cause Shapefiles to lose attributes when you save them. On performance with large data, Shapefile wins, and both lose to modern formats such as GeoPackage and FlatGeobuf, which combine the single-file convenience of GeoJSON with the speed of a binary format. On web mapping, GeoJSON wins outright: it is the format the web speaks, and no conversion step is needed.

When to Use Each One

Use GeoJSON when you are building a web map, sharing a small dataset with a colleague, storing data in Git, or working with a JavaScript mapping library. Use a Shapefile when a client, a government portal or an old workflow demands it, or when you need maximum compatibility with desktop tools that expect it. Use GeoPackage when you want the best of both: a single file, fast, with proper field names and no size limits, which is why it is increasingly the recommended default in QGIS. The conversion between all three is one click in QGIS: right-click the layer, choose Export, then Save Features As, and pick the format. There is no reason to be loyal to one format for everything. Pick the format that fits the destination, and convert freely.

The Bottom Line

Shapefile is the legacy standard that refuses to die, and GeoJSON is the web-native format that keeps winning new work. Neither is going away, and a working GIS professional needs to be fluent in both. If you are starting a new project today, default to GeoPackage for storage and GeoJSON for the web, and keep Shapefile in your toolkit for the clients and portals that still ask for it. The format is not the work. The map is the work, and the right format is the one that gets your map to the people who need it with the least friction.