Overpass JSON 📡

Overpass API JSON

Open Beta
.json · application/json

Overpass JSON is the response format of the Overpass API, a read-only query language over OpenStreetMap (Roland Olbricht, since 2008). It is a compact JSON with a list of elements (node/way/relation), their geometry, tags, and a meta block — the structure parsed directly by osmnx, the QGIS QuickOSM plugin, overpass-turbo, and dozens of pipelines that use OSM as a structured dataset. Our exporter builds JSON of the same structure from the OSM layers: each feature becomes an element of the appropriate type with id, coordinates, geometry, and tags, plus a meta section with generator and version. Honestly: we synthesize an Overpass-format-compatible response from our selection — this is not a live Overpass API query, but the result can be handed to downstream tools as a drop-in replacement for a public Overpass response.

Export Overpass JSON now ✨ Open Beta — free, no limits

Key Features

An elements array with node, way, relation types
Nodes with coordinates, ways with geometry, all with tags
A meta section with generator, timestamp, and version
Compatibility with overpass-turbo, osmnx, and QuickOSM
Single layer — a .json file, multiple layers safely merged

About Overpass JSON Format

Overpass JSON is the response format of the Overpass API, the query language for OpenStreetMap data. It is compact JSON: an elements array where every object is a node, way or relation with its coordinates, geometry and tags, plus a service meta block. This structure is read directly by OSMnx, the QuickOSM plugin for QGIS, overpass-turbo and dozens of research pipelines.

The format is chosen when OSM is used as a structured dataset: counting objects by tags, assembling a street graph, exporting points of interest into your own script. A ready file instead of a live query removes the two familiar Overpass problems — rate limits and timeouts on large selections — and it also makes the result reproducible: you hold a fixed snapshot of the data.

The exporter synthesizes a response of the same structure from your selection: points become node elements with coordinates, lines and polygons become way elements with a node list and geometry, tags are carried over as they are, and the generator and version are written into meta. Identifiers are issued by us from a separate range so as not to collide with real OSM numbers; the size of a single file is limited to a hundred thousand elements. This is not a live query to Overpass but a compatible replacement for its response.

What Program Opens Overpass JSON Files

The following programs and applications can open, edit, and work with Overpass API JSON (.json) files exported from OSM2CDR:

💻overpass-turbo 💻OSMnx 🌎QGIS (QuickOSM) 💻overpy (Python) 💻JOSM

Format specifications

Who Uses Overpass JSON Maps

🏗
Feeding osmnx as a replacement for a public Overpass API response
The data is fed into OSMnx and similar tools instead of a response from the public Overpass — with no waiting and no rate limits.
💻
Loading a selection into QGIS through the QuickOSM plugin
The selection opens in QGIS through the QuickOSM plugin like an ordinary Overpass result.
📊
A reproducible data snapshot for research without rate limits
A fixed snapshot of the data for a study: the result is reproducible half a year later too.
🎨
Driving custom Python parsers that expect the Overpass format
Your own scripts and pipelines, already written for the Overpass format, work without rewriting.

How to Export Overpass JSON

1
Select area
Draw a rectangle or polygon on the interactive map at osm2cdr
2
Choose Overpass JSON
Select Overpass API JSON from the list of 127 available export formats
3
Export
Click Export and receive your .json file in 1-5 minutes
4
Download
Download the ready Overpass JSON file and open it in overpass-turbo

How to Open After Export

Popular maps in Overpass JSON

Free

Get Overpass API JSON map exports

Download professional Overpass JSON maps from OpenStreetMap. Instant generation, any area.

Free / export
Export Overpass JSON now →

Frequently Asked Questions

Is this a live Overpass API query?
Is the result compatible with osmnx and QuickOSM?
How does Overpass JSON differ from the main OSM API?
How do I open the file?
Are the object identifiers in the file real ones?
How many objects fit into one file?

Related Formats

Frequently Exported Together

Related Articles