Offline has a file format, and its name is ZIM. Built for carrying encyclopedias into places the network does not reach, the ZIM format compresses whole libraries of interlinked pages into a single archive, read by the Kiwix software on nearly every platform. OpenStreetMap lives in that world twice, and the two lives are different enough to confuse anyone who searches the phrase once and downloads the wrong species. In one, the OpenStreetMap wiki, the project's vast documentation, is packaged as ZIM files for offline reading. In the other, map data itself, rendered and packed, travels as ZIM, in projects such as StreetZim that put a working map into the same kind of file. Same extension, same reader, entirely different cargo. This guide separates the species, shows where each is published and how each is read, and teaches the freshness discipline the format demands, because an offline archive's date is part of its content.
Home / GIS and Open Map Data for Beginners
OpenStreetMap ZIM File: The Wiki in a File, and Maps in a File

Photo: Zetong Li / Pexels
Pack the Library: The ZIM Checklist
Check off each step as you finish it. Your progress stays on this page.
0 of 7 complete
0% done
Species One: The Wiki, Packaged
The OpenStreetMap wiki is where the project's knowledge lives: every tag's meaning, every editor's manual, every proposal and country guide. Packaged as ZIM, it becomes a reference library that works in a field camp, on a ship, or in a classroom without connectivity. The builds are published through the Kiwix download library under names of the form openstreetmap-wiki_en_all, and they come in variants whose suffixes are the whole decision: the maxi variant carries the wiki complete with its images, and the nopic variant omits images for a fraction of the size. The choice between them is a bandwidth judgment, not a quality one: the text, which is where tag definitions and mapping guidance live, is identical, so a slow connection argues for nopic and a field laptop with room argues for maxi. For a mapper, this species is reference: when the question is what a tag means or how a feature is conventionally mapped, and the answer must not wait for a signal, the wiki in a file is the project's memory made portable.
Species Two: Maps in the Archive
The second species packs the map itself. StreetZim is the name to know: a project that renders OpenStreetMap data with the MapLibre rendering stack and packs the result into a ZIM file, so a Kiwix reader can present an explorable map from one archive, no tile server, no network. The idea generalizes the ZIM promise from documents to geography: the archive holds the compressed substance, the reader supplies the interaction. Judge this species by the map questions you bring to it: it serves looking, browsing, and orienting from packaged data, and it is not a routing engine, a live editor, or a substitute for the tile and extract ecosystems when analysis is the job. Its home ground is the same as the wiki ZIM's, the disconnected place, where a browsable map of your region in a single file is the difference between having geography and not having it. The two species can share a device and a reader, and a well-prepared field kit carries both: the wiki for what things mean, the map for where things are.

The Reader: Kiwix
Both species are read by Kiwix, the ZIM reader maintained by the project of the same name, available for desktop systems, Android, and iOS, with a server variant that can serve an archive collection to a local network, a pattern used by schools and field offices to give many readers one library. Kiwix behavior is uniform across the species: open the file, and its contents present with search and internal links, the wiki reading like the website it was, the map presenting through its embedded viewer. Two habits make a Kiwix library a tool rather than a pile of downloads. Organize by purpose: keep the reference archives and the map archives named and foldered so the file you need at a trailhead is findable without a search party. Record what you carry: a note of each file's build date, which the next section teaches you to read, turns the library from a snapshot you hope is current into one you know the age of. Kiwix itself is free and open source, and its library at download.kiwix.org is the canonical shelf from which both species are fetched.
Freshness: Read the Date in the Filename
An offline archive cannot update itself, so its age is a fact the user must supply, and ZIM builds make that possible honestly: the builds are dated, and the filename carries the build's date stamp. The discipline is a habit of three seconds: read the date before you rely on the content. The OpenStreetMap wiki's own offline documentation illustrates why: the builds listed there are dated, and a wiki snapshot from a given month knows nothing of tags agreed the month after, just as a map ZIM knows nothing of the bridge built since its rendering. This guide deliberately prints no current build date, because any date printed here would age exactly like the files it describes; the standing rule travels better: a ZIM is as fresh as its filename says, and no fresher. In practice: refresh the field kit's archives before a deployment, not during; teach every user of a shared Kiwix library to check the stamp; and where freshness is the difference between a right and a wrong decision, treat the archive as a starting point and verify against a live source when one appears. The format's honesty about its dates is a feature; the failure mode is only ever a reader who did not look.
ZIM Beside the Other Containers
The offline shelf holds several single-file answers, and placing ZIM among them sharpens when to reach for it. MBTiles, taught in its own guide here, packs a tile pyramid into SQLite: the right container when an app must draw tiles natively, in OsmAnd or a GIS. Offline app downloads, OsmAnd's regions and their kin, are the right answer when one app owns the whole job. ZIM's distinct ground is the archive that a general reader opens: reference libraries, documentation, whole wikis, and experimental map packages like StreetZim, all shelved in one Kiwix library beside whatever other knowledge the place without network needs, from medical references to textbooks. The formats are complements in a serious offline kit, not rivals: tiles for the navigation app, ZIM for the library, each doing the job its reader was built for.
Building the Field Kit
Assembled, the practice is short. Choose the wiki variant by bandwidth: maxi where storage allows, nopic where the download is the constraint. Add the map ZIM for your region if your work is among StreetZim's covered ground. Read every filename's date as you download, and write the kit's refresh date somewhere a successor will find it. Install Kiwix on the devices that will actually travel, and open every archive once before departure, because a file verified at home is a tool and a file first opened in the field is a hope. That is the whole craft: the right species, a known date, a reader that works. The network's absence stops being an emergency when the library was packed before it was needed.
The Local Library Pattern: Kiwix as Infrastructure
The ZIM idea reaches its full stature when Kiwix stops being one reader on one laptop and becomes a place's library. The pattern, proven by schools, clinics, ships, and field offices, runs Kiwix's server form on a small local machine or hotspot device: one computer holds the archive collection, the wiki ZIMs, the map ZIMs, and whatever else the library carries, and every phone and laptop in range browses it over the local network with no internet involved. The pattern changes the freshness discipline's scale: one librarian, formal or accidental, refreshes the collection when a connection appears, and every reader in the building benefits at once, which is why the date-in-the-filename habit belongs to the collection's keeper most of all. It also changes the collection's curation into a real editorial act: a library for a mapping deployment carries the OSM wiki and the region's map package beside its medical and agricultural references, chosen for the work the place does. OpenStreetMap's presence in that company is the project's offline philosophy made concrete: the map and its memory, shelved next to humanity's other reference works, readable in the dark at the end of the road.
What ZIM Is Not
A boundary-setting section, because the format's enthusiasts oversell it in predictable directions. A ZIM is not a database: you cannot query it like PostGIS, extract a region like an Overpass call, or update a single entry; it is a published edition, fixed at build time, and treating it as a data source for analysis mistakes a book for a filing cabinet. It is not a backup of the live project: the wiki ZIM omits the wiki's machinery, its histories and discussion apparatus arrive flattened into pages, and the map ZIM is a rendering, not the underlying vectors. And it is not current, ever, in the way a live service is current, a point the freshness section makes as a discipline rather than a complaint. Within those boundaries the format is superb: a portable, searchable, self-contained edition of knowledge that asks nothing of a network. Most tools fail by being asked to be other tools; ZIM, asked to be a library, has been succeeding at it for years.
There is also a quieter reason the wiki species matters to mappers specifically: the wiki is where OpenStreetMap's conventions are argued into existence, and carrying it offline means carrying the argument's current settlement into places where the argument cannot be consulted live. A mapping decision made in a disconnected camp, from the packaged wiki, is made from the same text the whole project reads, and that shared text is a large part of what makes a crowd's map one map.
The two species also age differently, which is worth a planner's sentence: the wiki's knowledge moves at the speed of tagging debates, slow enough that a months-old snapshot stays serviceable, while a map's territory can change with one road crew, which is why the map ZIM's date deserves the stricter reading of the two.
Related Guides
If this page answered part of the question, these GIS guides cover the rest of the same ground:
- OpenStreetMap MBTiles Download: One SQLite File Holding a Whole Map: The tile container, for apps that draw tiles natively.
- OpenStreetMap WMS: The Request-Driven Map Service: The opposite pole: maps rendered live, per request, when a network exists.
- OpenStreetMap Tags: The Grammar of the Database: What the wiki ZIM documents, tag by tag, summarized on this site.
- HOT Tasking Manager: Coordinated Mapping, Square by Square: The field operations these offline kits so often support.
Frequently Asked Questions
What is a ZIM file?
An offline archive format that compresses interlinked content, whole wikis, documentation, even packaged maps, into a single file, read by the Kiwix software. It exists to carry libraries where networks do not reach.
What are the two kinds of OpenStreetMap ZIM?
The OpenStreetMap wiki packaged for offline reading, published via the Kiwix library as openstreetmap-wiki_en_all builds in maxi (with images) and nopic (text only) variants, and map ZIMs such as StreetZim, which pack rendered OpenStreetMap data viewable in Kiwix.
How do I read a ZIM file?
With Kiwix, the free reader for desktop, Android, and iOS; a server variant can serve a collection to a local network. Open the file in Kiwix and its contents present with search and links.
How fresh is a ZIM file?
Exactly as fresh as its build date, which the filename carries. A snapshot knows nothing published or built after that date, so read the stamp before relying on the contents, and refresh field kits before deployment.
Should I choose the maxi or nopic wiki build?
Maxi includes the wiki's images and is the complete reference; nopic omits images for a much smaller download with identical text. Choose by your bandwidth and storage, not by content quality.
Photo credits: Zetong Li (Pexels); Zetong Li (Pexels). Photos are served from this site; follow the credit to the library page for the original.