How to Convert GeoJSON to a Shapefile Without Losing Your Data

Your data lives in GeoJSON. The next tool — often ArcGIS, an old QGIS project, or a city system — asks for a Shapefile. The move sounds simple, but this is the road where data gets hurt most often. Field names shrink. Mixed shapes split. Long text gets cut. None of it has to happen without warning.

This guide shows you how to convert GeoJSON to a Shapefile ZIP here with your eyes open. You will learn which Shapefile limits can bite, how to plan for each one before you run the job, and how to check the result so you can prove that nothing was lost in silence.

The worked example is a set of bike share docks stored as GeoJSON points, with long, clear field names — just the kind of file that shows the Shapefile limits at once. If your file is polygons or lines, the same steps and the same checks apply.

Why This Road Is the Risky One

GeoJSON is the newer, looser format. A Shapefile is the older, stricter one. When you move from loose to strict, the strict rules win. Three rules cause almost all the pain. First, a field name can hold at most 10 letters. Second, one Shapefile holds one kind of shape. Third, a text field holds at most 254 letters in the classic table form.

There is a fourth, quieter rule. A Shapefile is a set of files, not one file. Your one GeoJSON file will come back as a ZIP that holds .shp, .shx, and .dbf parts, plus a .prj for the coordinate system. Whoever gets the data must keep the set whole. If they pull out just the .shp file, the data is broken, and they will blame the file, not the unpack step.

None of these rules is a reason to avoid the job. They are a reason to plan it. Rename fields on purpose, with names you choose. Split mixed shapes on purpose, into files you name. Then the strict format holds no shocks, and the report can show each change you agreed to.

What Stays Safe, and What Needs a Plan

Shapes stay safe. Points stay points, lines stay lines, and polygons keep their edges, as long as one file holds one kind. Whole numbers and plain decimal numbers stay safe too. Dates are the one number-like type to watch: the Shapefile table holds a date with no time of day, so a full time stamp loses its hours and minutes.

Text needs the plan. A field named station_manager_name will not fit in 10 letters. The tool will cut it, and it will list the new name in the report — but a name you pick yourself, like manager, is clearer than a name a tool picks for you. Read your field list before the job, and write the short names you want. Our notes on how to keep long field names safe in a GeoPackage show the other path, for cases where short names are not an option at all.

Null values — empty facts — also need a glance. GeoJSON uses a clear null. The old table form has weaker rules for empty numbers, and some tools read an empty number as zero. If empty and zero mean different things in your data, check those fields with care after the move, and note the fact in your hand-over note.

Words to Know

These five terms cover the parts of the job where loss can hide. Read them before you start.

• Feature. one real thing on the map, such as one park, one road, or one shop. A file can hold many features.
• Attribute. a fact about a feature, stored as text or a number. A park has a name. A road has a speed limit. Those facts are attributes.
• Layer. one set of features of one kind, shown as one sheet on a map. A city file may hold a roads layer and a parks layer.
• ZIP file. one packed file that holds many files in it. A Shapefile needs a ZIP, since a Shapefile is three or more files that must travel as one set.
• Bounding box. the smallest box that holds all your data. It is named by its west, south, east, and north edges. A box in the wrong place is a fast sign that a file went wrong.

When You Should Make This Move

Most people make this move for one clear reason: the next tool demands it. That is a good reason. Here are the cases we see most:

• A city or state office asks for a Shapefile as the format for a formal hand-over.
• Your team works in ArcGIS, and the project was set up around Shapefiles years ago.
• A print or survey tool takes Shapefiles and nothing else.
• You must match an old archive, and all the past years are stored as Shapefiles.

If none of these is true, think twice. Keep your master copy in GeoJSON or GeoPackage, and make the Shapefile a copy for one job. And if your data started life as a Shapefile, keep that set too. The FAQ at the end of this guide links the return road, so you can move back with the same care you used on the way in.

A Worked Example: Bike Share Docks

Your GeoJSON holds 48 bike share docks. Each dock is a point, with four facts. Two of the field names are too long for a Shapefile. Here is the plan you make before you run the job:

{
  "type": "Feature",
  "geometry": { "type": "Point", "coordinates": [-0.1276, 51.5072] },
  "properties": {
    "dock_name": "Riverside Dock 4",
    "docks_available_count": 18,
    "station_manager_name": "A. Osei",
    "open_all_day": true
  }
}

48 docks go in. 48 docks must come out, in one point file. The field names change, by your plan, and the report should list the same four changes you wrote down. If the report lists a fifth change, stop and look. That is how you catch a field you missed in your plan.

Note the true/false field. The classic Shapefile table has no clean true/false type. Tools store it as a short text (true / false) or as 1 and 0. Either is fine, as long as the team that gets the file knows which one you used. Write it in your hand-over note.

Keep Your Source Safe

Work on a copy, not on your only file. Save the first file in a safe place and do not change it. If a test goes wrong, you can start again from the clean source. This sounds like a small point, but it saves more work than any other habit in this guide.

Give each test a clear name. A name like test-1 tells you the order of your tries. A name like final-final-2 tells you nothing at all. When you find the settings that work, write them down in a short note next to the files. The next file of the same kind will then take minutes, not an hour.

How to Convert GeoJSON to a Shapefile, Step by Step

Plan first, convert second. Steps 1 and 2 are the plan. If you skip them, the tool still runs — but it makes the choices for you, and you find out what it chose only when a name looks wrong weeks later.

Step 1: List your fields and mark the long ones

Open your GeoJSON in a text app, or read the field list from a past report. Write down each field name and count its letters. Mark each name over 10 letters. For each marked name, write the short name you want. Keep the short names distinct: docks_avail and docks_broken must not both shrink to the same 10 letters.

Step 2: Check for mixed shapes

Look at the geometry types in your file. If the file holds points and lines, or polygons and points, one Shapefile cannot hold them all. Split the file by type first, or let the tool split it and name each part. Each output file gets one type, and your counts must match per type, not just in total.

Step 3: Upload the GeoJSON file

Drop the file on the home page. The summary shows the feature count, the shape types, the field list, and the bounds. Match each one to your plan. If the count is wrong at this stage, the file you uploaded is not the file you planned for. Stop and find the right one.

Step 4: Set the short field names

Where the tool shows the field mapping for Shapefile output, type the short names from your plan. Take your time here. This one step is the whole ball game for this road. A clear short name now beats a week of email later, when a partner asks what station_ma was meant to mean.

Step 5: Choose the target coordinate system

GeoJSON is always WGS 84. Your target may not be. If the office that asked for the file works in a state plane or UTM system, pick that system, or type its EPSG code. If they gave you no rule, keep WGS 84. Our guide to what to do when a Shapefile will not open also shows how the .prj file records this choice for the next reader.

Step 6: Run the job and read the rename list

Click Convert. When the job ends, read the report top to bottom. It lists features in and out, and each field rename it made. Match the rename list to your plan, line by line. A rename you did not plan is a flag, not a detail. Check that field in the source before you send the file on.

Step 7: Download the ZIP and keep it whole

Download the result. It is a ZIP that holds the full set of parts. Send the ZIP as it is. Do not unzip it and send loose files, and tell your reader not to pull the parts apart. The set works as a team, or not at all.

How to Check Your Result

Never trust a conversion you have not checked. The good news is that a sound check takes just a few minutes, and it is the same each time you work on a GeoJSON to Shapefile job.

First, match the counts. The report shows how many features went in and how many came out. The two counts should be the same. If the output count is lower, a step dropped data, and you should find out why before you share the file.

Next, look at the map preview. Your data should sit in the right town, state, or sea. If it sits in the ocean, or on the wrong side of the world, the coordinate system is the prime suspect. Zoom in on one place you know well and check that roads, parks, or points fall where they should.

Then check the fields. Open the field list in the report and read the names. Make sure the key fields are still there, with the right names and the right kind of values. Pick one feature you know and match each value back to the source by hand.

• Check the rename list once more in the downloaded set. Open the table and read the column names with your own eyes.
• Spot-check one long text value. If a name or note was near 254 letters, make sure it was not cut in the middle of a word.
• Check one empty field and one zero field. They must not have swapped meanings in the new table.

Last, keep the source file. Save the result with a clear name that holds the date and the format, like parks-geojson-2026-11-07.zip. Keep the source and the result in one folder. If a question comes up next month, you can trace each feature back to where it came from.

Common Mistakes and How to Fix Them

Two Fields Got the Same Short Name

This happens when two long names share the same first 10 letters. The tool adds a number to split them, but the names stay hard to read. Fix it at the plan stage: give each field a short name that is distinct in its first few letters, not just at the end.

Some Features Are Missing in the Output

Mixed shapes are the usual cause. The output file holds one type, and the other type went to a second file — or was left out. Check the input summary for more than one geometry type. Convert each type as its own job, and match counts per type.

The File Opens but the Table Is Empty

The .dbf part is missing or has a different base name. A Shapefile with no table part shows shapes with no facts, or fails in odd ways. Keep the whole ZIP whole. If you got loose parts, ask for the ZIP form and start again.

Dates Lost Their Times

The Shapefile table stores a date and no time. A stamp like 2026-11-07 14:30 comes back as 2026-11-07. If the time matters, add a text field with the full stamp before you convert, or keep the master data in GeoJSON and treat the Shapefile as a view, not the record.

The Map Puts the Data in the Wrong Place

The target system was picked wrong, or the reader ignored the .prj file. First check that the ZIP holds a .prj part. Then check the system it names. If your reader still places the data wrong, send a test file with one known point and agree on the system by name and EPSG code, in writing.

What the Plans Allow

You can start free. The Free plan gives you 5 conversions a month, with one file at a time and a size limit of 25 MB per file. That is enough to test a GeoJSON export for a partner office on real data and check the result with care.

Starter costs $9 a month. It gives you 200 conversions a month, files up to 500 MB, and batch jobs of up to 10 files at once. Pro costs $19 a month. It gives you 1,000 conversions a month, files up to 5 GB, batch jobs of up to 25 files, and API access for work you run on a schedule. You can compare the plans side by side before you pick.

All plans work the same way at the core. You get a map preview, feature counts in and out, and a clear report if a file has a fault. Your files are kept for 72 hours so you can download them again, and then they are deleted.

Frequently Asked Questions

Will I lose my long field names for good?

In the Shapefile copy, yes — the format cannot hold them. In your master GeoJSON, no. Keep the GeoJSON as the master. Think of the Shapefile as a print-out: made for one reader, not the place where the true data lives.

Can a Shapefile hold more than one layer?

No. One Shapefile is one layer of one shape type. A ZIP can hold more than one Shapefile set, one per layer. Name each set with care, so the reader can tell which is which.

What is the biggest GeoJSON I can convert?

On the Free plan, files up to 25 MB. Starter takes up to 500 MB and Pro up to 5 GB. Note the format itself has a size cap of its own: a single .shp or .dbf part should stay under 2 GB for safe use in other tools.

Why did my true/false field change type?

The classic table form has no true/false type. The tool stores the value as short text or as 1 and 0, and the report says which. Tell your reader which form you used, so their queries match the data.

How do I go back to GeoJSON later?

Use the reverse trip, from Shapefile to GeoJSON, and pack all the parts into one ZIP first. Your short field names will stay short — the full names exist only in your GeoJSON master, which is one more reason to keep it.

Final Checklist

Run through this short list before you share your file:

• Counts match in total and per shape type.
• Each rename in the report was in your plan.
• The ZIP holds .shp, .shx, .dbf, and .prj parts with one base name.
• One long text value and one empty value check out by hand.
• Your GeoJSON master is saved and named as the master.

If each point passes, your file is ready to use.

References

• https://gdal.org/en/stable/drivers/vector/shapefile.html — The GDAL Shapefile driver notes. They state the 10-letter field name limit and the field types the table can hold.
• https://www.loc.gov/preservation/digital/formats/fdd/fdd000280.shtml — The Library of Congress format note for the ESRI Shapefile. It describes the set of files and the format history.
• https://www.rfc-editor.org/rfc/rfc7946 — RFC 7946, the GeoJSON specification, for the source format rules.