A map tile pyramid is thousands of tiny files, and thousands of tiny files are a misery to move: folders that copy slowly, archives that corrupt silently, phones that choke on the file count. MBTiles is the format that fixed the carrying problem by refusing to be a folder at all. An MBTiles file is a single SQLite database whose tables hold the tiles, their coordinates as rows, ready to be served by any program that speaks the specification. One file to download, one file to verify, one file to hand to a colleague on a USB stick, and inside it, a whole map, zoom level by zoom level. The format came out of Mapbox's early work and became the standard shipping container for offline tiles across the OpenStreetMap world. This guide teaches the format as a system: what is inside the file, where downloads come from, how files are created when no download fits, the arithmetic of zoom and size that separates a sane file from a 40-gigabyte mistake, and the readers that put the map to work in the field.
Home / GIS and Open Map Data for Beginners
OpenStreetMap MBTiles Download: One SQLite File Holding a Whole Map

Photo: Gaspar Zaldo / Pexels
One File, Whole Map: The MBTiles Checklist
Check off each step as you finish it. Your progress stays on this page.
0 of 7 complete
0% done
Inside the File
Open an MBTiles file with any SQLite browser and the design explains itself. A metadata table holds name-value pairs describing the file: its name, its format (PNG, JPG, or vector PBF tiles), its bounds, its center, and its minimum and maximum zoom. A tiles table holds the pyramid: each row keyed by zoom level, tile column, and tile row, with the tile's bytes as a blob. One quirk betrays the format's origins and trips every newcomer who inspects a file by hand: the row coordinate is stored flipped relative to the usual tile scheme, in the TMS convention rather than the XYZ one, a detail readers and writers handle silently and only manual tinkerers ever meet. The deeper point is what SQLite buys: random access by key, so an app asks for exactly one tile and gets it in milliseconds from a file of any size; transactional integrity, so a copied file is whole or visibly not; and a format every platform already knows how to open. The pyramid did not change; its packaging became a database, and the database is why the format won.
Where Downloads Come From
Pre-made MBTiles of OpenStreetMap data circulate through the field-work ecosystem rather than through a single official shop, and knowing the neighborhoods matters more than any one address. The HOT Export Tool, taught in its own guide on this site, lists MBTiles among its export formats, which makes it a creation route disguised as a download: describe your area, choose the format, receive the file. OpenSeaMap, the marine chart project built on OpenStreetMap, distributes chart bundles in the format for offline navigation. Field-data organizations such as SurveyCTO document MBTiles as the way to put offline basemaps under their forms, and their knowledge base is a reliable explainer of the format's field behavior. Beyond those, community and commercial providers package regional extracts at various zooms and prices of effort. The standing cautions apply with force: a downloaded MBTiles is a snapshot whose date you should learn before trusting it in the field, and its zoom range is its destiny, fixed at creation; a file that stops at zoom 13 will not sharpen because you wish it would.

Creating Your Own: The Renderer Route
When no download matches your area and zoom, the file is created by rendering or packing tiles yourself, and the toolchain is the tile ecosystem's own. Planetiler, the modern open-source generator documented in field guides across the OSM world, builds tile files, MBTiles among them, from OpenStreetMap extracts at remarkable speed, and it is the current default answer for making a regional file on a laptop. The older route runs through tile renderers and downloaders that walk a tile server's pyramid for your bounding box and pack what they fetch, a method bounded by the tile usage policies of whatever server you walk: a pyramid is someone else's bandwidth, and bulk downloading against the public OpenStreetMap tile servers violates their policy, which is why creating from a local extract, Planetiler's way, is the respectable path. Whichever route, creation is where the next section's arithmetic must be done, before the render starts, not after the disk fills.
The Arithmetic: Zoom Is Destiny
Every zoom level quadruples the tile count, and that single fact governs the format's practical use. A town at zooms 10 to 16 is a file you email. A province at zooms 10 to 18 is a file you plan. A country at zooms 10 to 19 is a file you regret, because the deepest zooms, where the count explodes, cover every field track and driveway in the territory at full fidelity whether anyone will ever look at them or not. The discipline has three moves. Set the maximum zoom by the work: navigation and field verification rarely need beyond 16 or 17; reading house numbers from tiles is a fantasy the data answers better as vector. Let the minimum zoom be small: shallow zooms are nearly free and give the zoomed-out context that orients a field day. Bound the box tightly: the rectangle you choose is multiplied by every zoom, so trimming empty ocean and neighboring desert is the cheapest compression there is. Vector tiles, where the reader supports them, bend the arithmetic kindly, one compact dataset instead of raster at every scale, but the exponent does not care about your format; it only asks what area, to what depth. Answer those two questions on paper first, and MBTiles stays the friendly format it is meant to be.
The Readers: Where the File Goes to Work
An MBTiles file earns its keep inside other software. OsmAnd and Locus Map, the Android navigation staples of the OpenStreetMap world, read MBTiles as offline map sources and overlays, which is the classic field pattern: the file on the phone, the map alive with no signal. SurveyCTO Collect uses MBTiles basemaps under its forms, with a caveat its documentation states and this guide repeats because it changes planning: Collect's offline layers are raster only, so a vector MBTiles will not serve there. Desktop GIS reads the format too: QGIS opens MBTiles as a raster or vector tile layer, useful for verifying a file before it ships to the field, which is a habit worth forming, since the cheapest time to discover a wrong bounding box is at your desk. And servers and converters round the circle, unpacking or serving the file back into tile endpoints. In every case the contract is the same: the reader speaks the specification, the file answers tile by tile, and no network is consulted. That contract, boring and kept, is why a format from the early smartphone era remains the field's shipping container.
Vector MBTiles: The Same Container, Different Cargo
Everything above assumed raster tiles, little pictures in the database, but the container is agnostic and its second cargo changes the field's economics: vector tiles, stored in the same MBTiles tables as compressed protobuf payloads, one per tile coordinate. A vector MBTiles of a region holds the map's actual geometry and attributes, sliced by tile, so the reader draws and styles the map at read time: the same file can render as a road map, a muted basemap, or a hiking view, because the cartography lives in the reader rather than in pre-drawn pixels. The size arithmetic bends too, since geometry stored once replaces pictures stored at every zoom's rendering, and a country's vector file can be startlingly portable next to its raster equivalent. The constraints are the readers and the tooling: not every app that opens raster MBTiles reads vector ones, SurveyCTO Collect's raster-only caveat being the field's standing example, and creating vector files is Planetiler's and tilemaker's craft rather than a downloader's. The metadata table's format entry is where the two cargoes declare themselves, png or jpg against pbf, and checking it before shipping a file to a reader that cannot speak vector is the container's one essential courtesy. Same box, different contents: the specification's quiet strength is that the box never cared.
Verifying a File Before It Ships
A file that will be trusted in the field deserves a desk check, and MBTiles makes checking easy because the container is inspectable. Open it in QGIS and pan the corners of its declared bounds: the map should end where the metadata says it ends, with no silent truncation at the box's edge. Read the metadata table itself with any SQLite tool: name, format, bounds, and zoom range are printed there in the clear, and a file whose paperwork disagrees with its promise is caught in a minute. Check the size against the plan: a file wildly larger or smaller than the zoom arithmetic predicted is telling you the creation run did something other than what was asked, a wrong box, a runaway zoom, an empty layer. And if the file will be copied to many devices, hash it once and verify copies against the hash, because SQLite's integrity is only as good as the copy that carries it. Five minutes of this turns a download into a known quantity, and the field, which cannot re-download the world, is exactly where known quantities matter.
A last practical note on sharing: because the file is a database, it travels through channels that mangle folders unscathed, email, chat, cloud drives, and it arrives as one object whose size and hash can be confirmed in a sentence. In field logistics, where a map file passes through six hands and three networks before it reaches the phone that needs it, that boring survivability is not a detail; it is the feature the whole format exists to provide.
Related Guides
If this page answered part of the question, these GIS guides cover the rest of the same ground:
- HOT Export Tool: Filtered, Formatted OpenStreetMap Extracts: One of the main creation routes, with MBTiles among its formats.
- OpenStreetMap ZIM File: The Wiki in a File, and Maps in a File: The other great single-file container, for reference content and rendered maps.
- OpenStreetMap PBF: The Planet Format: The extract format a local creation route starts from.
- OpenStreetMap Tile Server: The z/x/y Raster Stack: The pyramid the file packs, and the usage policies that govern fetching it.
Frequently Asked Questions
What is an MBTiles file?
A single SQLite database holding a tile pyramid: a metadata table describing the file and a tiles table storing each tile's bytes keyed by zoom, column, and row. One file carries a whole map area for offline use.
Where can I download OpenStreetMap MBTiles?
Through the field-work ecosystem: the HOT Export Tool creates them for your chosen area, OpenSeaMap distributes chart bundles, and various community and commercial providers package regional files. Always learn the snapshot's date and zoom range before relying on it.
How large will an MBTiles file be?
It depends on area and maximum zoom, and the relationship is brutal: each added zoom level quadruples the tile count. A town to zoom 16 is emailable; a country to zoom 19 is a disk event. Set area and depth on paper before creating the file.
Can I create MBTiles myself?
Yes. Planetiler builds MBTiles from OpenStreetMap extracts on a laptop and is the current standard route. Packing tiles by walking a public tile server is bounded by that server's usage policy; creating from a local extract is the respectable method.
Which apps read MBTiles?
OsmAnd and Locus Map on Android, SurveyCTO Collect for form basemaps (raster files only), QGIS on the desktop for verification and use, and a range of servers and converters. The format is a specification, so any conforming reader opens any conforming file.
Photo credits: Gaspar Zaldo (Pexels); Vitaly Gariev (Pexels). Photos are served from this site; follow the credit to the library page for the original.