Building an offline knowledge library that survives a week without internet

Try this: think of the last five things you looked up. How many of them would you have been able to answer from something in your house?

That is the actual gap. Not knowledge, which you can rebuild, but access, which vanishes the moment the network does. And unlike water or power, this one costs almost nothing to fix.

What should I download first?

In this order, because the value is front-loaded and the storage cost is not.

Layer one, medical and general reference. Kiwix is a free reader for offline copies of Wikipedia and similar collections. The file format is called ZIM. You install the app, download a ZIM file, and from then on it works with the radio off.

The subset to start with is WikiMed, the medical articles from Wikipedia. It runs under a gigabyte in the builds Kiwix currently publishes, so it fits on any phone with room to spare, and it is the highest-value gigabyte in this entire article. Sizes change as the collections are rebuilt, so take the current figure from the library page rather than from here.

Full Wikipedia with images runs around 100GB. Text-only versions are a fraction of that. Most people should take a text-only or "top articles" build first and decide later whether the images earn their space.

Layer two, maps. OpenStreetMap data is free, and readers like Organic Maps and OsmAnd will store a whole state on a phone with turn-by-turn routing that needs no signal. A US state typically runs a few hundred megabytes.

Then print a paper map of your county. This is not nostalgia. A paper map works with a dead battery, in the rain, spread on a bonnet, with four people reading it at once, none of which is true of a phone.

Layer three, your own documents. This is the layer that actually gets used, and the one everybody postpones. Ready.gov's financial preparedness pages list the set: identification, insurance policies, deeds and leases, prescriptions and medication lists, bank and account records, medical records, and photographs of your possessions for a claim.

Scan them. Encrypt them. Put them on two drives, keep one out of the house, and put a printed copy of the two or three that matter most into a folder you can grab.

Layer four, everything else. Project Gutenberg for books, repair manuals for what you own, the field guides for your region. This layer is where storage disappears fastest and returns least, which is why it is last.

What does the whole thing cost?

A single 256GB memory card holds all of it with room left over. The binding cost is not money or storage. It is the afternoon spent scanning documents, which is why that step is the one that stalls.

What most offline guides get wrong

They start with full Wikipedia. It is the impressive number, so it leads. It is also around 100GB, takes a long download, and is worth less to you at 2am than the sub-gigabyte medical subset. Do the small thing first, then decide.

They forget the reader needs power. An offline library on a phone with a dead battery is nothing. The library and the power plan are one project, and a cheap solar panel plus a power bank is the smallest version of it that works. Storage without power is a filing cabinet you cannot open.

They ignore the personal layer entirely. Wikipedia will not tell you your policy number. In a flood or a fire, the documents are the thing that determines how the next twelve months go, and they are the cheapest layer to build.

They never mention search. A 100GB archive you cannot search is a hard drive, not a library. Kiwix has full-text search built in and this is most of why it beats a folder of downloaded PDFs. Test the search before you rely on the archive.

They treat "offline" as a single state. There are several, and they need different answers: no internet but power on, no power but a charged phone, and nothing at all, which is where paper lives. Work out which one you are actually planning for.

Where AI fits, and where it does not

A local language model can answer a question you did not know how to phrase, which a search index cannot. That is a real advantage, and it comes with a real failure mode: a model with no sources will state something wrong in exactly the same confident tone it uses for something right.

The sensible arrangement is both. Keep the reference archive as the thing you check, and treat a local model as a way in when you do not know the right term. We build PrepperGPT (one of ours, paid product), which packages a local model and a reference library onto a USB drive, so treat that recommendation with the scepticism it deserves. The free path is Kiwix plus any of the open models you can run yourself, and it covers most of the same ground for the price of the storage.

The one-hour version

1. Install Kiwix on your phone and download WikiMed. Under a gigabyte.
2. Install Organic Maps or OsmAnd. Download your state.
3. Print a paper map of your county and put it in the car.
4. Photograph the front and back of every card in your wallet, plus your insurance declarations page. Put them in an encrypted folder on two devices.

That is one hour and it covers most of the value. The remaining 100 gigabytes can wait for a weekend you do not have anything better to do, which is the correct priority and the opposite of how these lists are usually ordered.