Home/Blog/How to Prepare a Laptop for Internet Outages
Field Notes

How to Prepare a Laptop for Internet Outages

A practical guide to offline AI, local docs, maps, manuals, and what to download before an outage hits. Real setup steps, storage estimates, and honest tradeoffs.

2026-04-07 · 9 min read · 1953 words
How to Prepare a Laptop for Internet Outages

How to prepare a laptop for internet outages

Preparing a laptop for internet outages comes down to one discipline: deciding what you need to know, then making sure that knowledge lives on the machine before the connection dies. Downloads, local apps, offline maps, cached docs, and a local AI that actually works without a server. That's the list. Everything below is how to work through it without overcomplicating it.

---

Why most laptops fail the outage test

The average laptop in 2024 is a thin client pretending to be a computer. The browser loads, the calendar syncs, the notes app saves to someone else's hard drive. Pull the ethernet cable and half the software stops responding. The other half just silently fails to update and pretends to work.

How to Prepare a Laptop for Internet Outages detail scene 1
Field note illustration.

This is not a conspiracy. It's just the economic logic of cloud software. Keep the data upstream, charge for access, make the device disposable. Reasonable for most days. Completely useless when a storm takes out your ISP for 72 hours, or you're working in an area with no signal, or you're traveling somewhere with restrictive network filtering.

The fix is not complicated, but it does require doing the work ahead of time. You cannot download an offline Wikipedia mirror during an outage. You cannot cache your maps once you're already lost. The setup window is now, when the connection is fine and you're not under any pressure.

---

How to Prepare a Laptop for Internet Outages detail scene 2
Field note illustration.

Start with your local model and offline AI

This is the part most people skip, and it's the part that makes the biggest difference. A local AI that runs entirely on-device means you still have a functional research assistant, a document explainer, a writing helper, and a question-answering tool when every cloud service is unavailable.

Wisdoom handles this as a complete package: local model management, a built-in offline knowledge vault, and citation-backed answers that point to your local sources. It runs on macOS, Windows, and Linux. You install it, pull down the models while you have a connection, load your knowledge library, and then the internet becomes optional.

The key technical piece here is local retrieval, sometimes called RAG. The model doesn't just answer from training data. It searches your local document vault first, then generates an answer grounded in what's actually stored on your machine. That means you can load it with medical references, legal documents, field manuals, or anything else you've saved, and get answers that cite the specific source rather than making things up.

For hardware, a modern laptop with at least 16GB of RAM handles a capable local model without much pain. 8GB works for smaller models but you'll feel it. An SSD speeds up retrieval noticeably compared to spinning rust.

---

What to download before the internet goes down

This is the practical checklist people actually want. Here's how to think through it by category:

Reference libraries

  • Wikipedia offline via Kiwix. The English Wikipedia ZIM file is roughly 85GB for the full version with images, or about 22GB for text only. Both are indexed and searchable without any connection.
  • Wiktionary, Project Gutenberg, and Stack Overflow dumps are also available through Kiwix if you need them.
  • OpenStreetMap exports or offline apps like OsmAnd for local area maps.

Documents and manuals

  • PDF copies of any manuals for equipment you own. Medical devices, generators, vehicles, tools. Manufacturer sites often delete old documentation. Get it now.
  • First aid references. The Merck Manual has a free online version you can save as a local archive. Wilderness medicine guides in PDF format are widely available.
  • Legal documents relevant to your situation: lease agreements, insurance policies, property records. These should be local copies regardless of outage planning.

Software and tools

  • Installer files for any software you rely on, stored offline. If you need to reinstall something without a connection, the download server being unreachable is a real problem.
  • Calibre for managing an offline ebook library. Load it with reference books, technical manuals, and anything you read regularly.
  • VLC for offline media playback. LibreOffice for documents if you don't want to depend on cloud office tools.

Maps and navigation

  • Download your region in whatever offline maps app you use. Most phones handle this, but your laptop should have it too. OsmAnd or Maps.me both work offline once you've pulled the regional data.
  • Paper maps of your local area are not ridiculous to have. They do not require a battery.

Read more about sizing your offline library in our guide to how much storage offline AI needs.

---

How to prepare a laptop for internet outages: the storage layout

Most people underestimate how much space a useful offline setup takes. Here's a realistic breakdown:

Content typeApproximate size
Wikipedia (text only)~22 GB
Wikipedia (with images)~85 GB
Local LLM (small, 7B)4-8 GB
Local LLM (medium, 13B)8-16 GB
Offline maps (regional)1-5 GB per region
PDF document libraryVaries, 5-50 GB
Offline Wisdoom vaultDepends on your docs

A 1TB SSD gives you comfortable room to work. A 512GB drive is workable if you're selective. The mistake is building a setup around your laptop's smallest drive and then wondering why everything feels cramped.

Partition or organize your offline content deliberately. Keep a dedicated folder for your knowledge vault, a separate one for installers and reference archives, and make sure your local AI app knows where its library lives.

---

Power and hardware considerations

The laptop itself is only part of the picture. An outage long enough to matter usually involves power disruption too. A few things worth sorting out:

Battery condition. Check your battery cycle count and actual capacity versus design capacity. A laptop that claims eight hours but actually delivers two is a liability. Replacement laptop batteries are cheap and available for most common models.

External power options. A USB-C power bank with enough capacity to fully charge your laptop gives you meaningful extension. Anker and similar brands make laptop-rated power banks in the 20,000-26,800 mAh range. Check wattage requirements for your specific machine.

Solar charging. For longer outages, a folding solar panel that feeds a power station can keep a laptop running indefinitely in daylight conditions. Overkill for a 24-hour storm, worth considering for rural or off-grid situations.

Display brightness. Running at 50-60% brightness instead of full extends battery runtime significantly. Turn off keyboard backlighting. Close tabs and background apps. Local AI is CPU and RAM intensive, so don't run it at full tilt on battery if you're conserving.

---

Local docs and file organization

Your laptop's outage readiness is only as good as your file organization. An unindexed pile of PDFs helps nobody.

Set up a folder structure that makes sense offline. Something like:

`` /Offline Library /Medical /Legal /Maps /Manuals /Reference /Software-Installers ``

Everything in that structure should be locally stored, not cloud-synced shortcuts. Right-click any synced folders and make sure they're set to be available offline, not just linked to a remote drive.

If you're using Wisdoom, point your local vault at the reference folders you care most about. The app indexes your documents so the local AI can actually retrieve and cite from them, not just sit there next to them on the same hard drive. That's the difference between having a filing cabinet and having a research assistant who has read everything in it.

For people who want to go deeper on building a structured offline knowledge base, the how to build an offline knowledge base post covers the architecture in more detail.

---

What a realistic outage scenario actually looks like

It's worth being honest about what you're preparing for, because it affects what you prioritize.

Short outage (hours to a day). ISP issue, storm, local grid problem. You need your laptop to stay functional, documents accessible, and basic reference available. No exotic setup required. Make sure your files are local, your battery is good, and you have cached maps.

Extended outage (days to a week). Regional infrastructure event. Power disruption is likely. You want offline AI with a real knowledge library, power backup, offline maps for your full area, and local copies of anything you'd normally look up online. This is where the Wisdoom setup earns its keep.

Long-term disruption (weeks or longer). Rural areas, severe weather events, infrastructure repair delays. At this point you're thinking about offline software for every task you'd normally rely on the cloud for. Medical references matter. Legal templates matter. Technical manuals for equipment you depend on matter. The offline AI library stops being a nice-to-have.

You don't need to build for the worst case to benefit from any of this. Even the short-outage setup makes your laptop more reliable for travel, slow rural connections, and day-to-day privacy. See our AI without internet post for a realistic breakdown of what changes and what doesn't when the connection drops.

---

FAQ: Preparing your laptop for internet outages

How much storage do I need for a solid offline setup? Realistically, 256GB is the floor if you're selective. 512GB to 1TB gives you comfortable room for a local AI model, offline Wikipedia, maps, and a document library without constantly making tradeoffs.

Can I use ChatGPT or other cloud AI tools during an outage? No. Cloud AI tools require a live internet connection to every API call. If your connection is down, they stop working entirely. A local model running on your own machine is the only AI option that works offline.

Do I need technical skills to set up offline AI? It depends on the tool. Wisdoom is built for normal users, not just homelabbers. You download it, it manages the model installation, and you point it at your documents. It's more setup than a cloud app, but it's not sysadmin-level work.

What's the most important thing to download before an outage? If you can only do one thing: download your regional offline maps and an offline Wikipedia mirror. Maps because navigation goes wrong in real outages. Wikipedia because it covers a wide enough range of reference topics to answer most general questions without any other tools.

Does a local AI actually give useful answers, or is it just a demo? Small local models are genuinely limited compared to frontier cloud models. They're slower, sometimes less accurate on complex reasoning, and worse at obscure topics. But with a well-loaded document vault and retrieval built in, they give grounded, cited answers on the content you've stored. For most outage scenarios, that's more useful than a smarter model with no internet connection.

How do I keep my offline library current without active maintenance? Schedule an update window monthly. Refresh your Wikipedia mirror, check for updated PDF versions of reference documents, and pull any new model updates if available. The content decays slower than you'd think, but it does decay.

---

Get this set up before you need it

The only bad time to prepare a laptop for internet outages is after the connection is gone. The good news is that none of this requires heroic effort. A few downloads, some file organization, a local AI app with a real offline library, and a charged laptop with a decent battery cover most scenarios.

Wisdoom exists specifically for this use case: offline AI that stays useful when the cloud isn't an option, with citations so you can actually trust the answers. Check out the Field Notes blog for more on offline knowledge setups, local model comparisons, and building a machine that works when the internet doesn't.