The 21-Kilobyte Lifeline: Why Plain Text Survives When the Network Fails

On the morning of October 10, 2024 — hours after Hurricane Milton made landfall — the full homepage of WUSF, Tampa's public radio station, took 8.5 megabytes to load. Its text-only page took 21.5 kilobytes: roughly 400 times less. When the network fails, the web retreats to plain text.

The measurement is Joshua Benton's, made for Nieman Lab that morning as NPR stations across Florida switched on bare-bones, text-only versions of their sites.¹ His explanation carries the whole story: "Text-only news sites are a niche interest at best in normal times. But a natural disaster is not normal times."²

The storm before Milton had just demonstrated the stakes. On October 1, 2024, after Hurricane Helene, the FCC reported that 48.7% of cell sites were out of service in the areas of North Carolina impacted by the hurricane, down from a previously reported 54.0%.³ A connection that frail cannot move 8.5 megabytes of homepage. It can move 21.5 kilobytes of text.

This essay is about why the web keeps re-learning that lesson, one named storm at a time, and what the same arithmetic means for the notes, contacts, and documents you keep.

Why news sites go text-only during disasters

News sites go text-only during disasters because disasters break the infrastructure the modern web assumes. Cell sites fail, bandwidth collapses, batteries drain — and a multi-megabyte page stops loading exactly when people need it. A text-only page still fits through what remains. News organizations have been re-learning this for twenty years.

The pattern is older than the smartphone. NPR's text-only site, Melody Kramer wrote at Poynter in 2017, "is likely the oldest example of a working text-only news site that's still in existence. It originally launched as thin.npr.org back in June 2005, in response to the September 11th attacks — when many news sites struggled to stay online amidst record traffic numbers."⁴

It resurfaced for Hurricane Irma in September 2017, when CNN stood up a text-only version of its site with no ads or videos and announced it in a tweet: "In Hurricane #Irma's path with a weak phone connection? Stay up to date with the text-only version of our website."⁵ The same week, NPR began promoting text.npr.org to readers with limited connectivity.

Then came Helene.

Josh Winn, a web developer at Sparkbox who lived through Hurricane Helene in western North Carolina, spent the outage trying to load emergency information over a dying connection. His verdict: "At that time, even a plain text site with barely any styles or images would have been better."⁶ One government emergency site he later tested scored 40 out of 100 and 26 out of 100 on Google PageSpeed Insights.⁷

The most useful artifact of his disaster was not a website at all. It was a plain bulleted list in a daily email from a local state representative: food and water, power and gas, shelter locations, road and cell-service updates. "I was struck by how something as simple as text content could have such a big impact," he wrote.⁸

By Milton, the response had become systematic. NPR shipped "a small change in Grove — its content management system that powers more than 200 local stations' websites — that allowed them to publish bare-bones, text-only versions of their sites," as Benton reported.⁹ Jonathan Butler, NPR's director of station digital solutions, said the feature exists "to support [stations'] ongoing efforts to serve their local communities with critical information, especially during crises or emergencies."¹⁰

Availability is a property of format and location

A page is available when two things hold: the format is light enough to travel over whatever connection survives, and the copy lives somewhere you can still reach. Format and location — not brand, not budget, not design. Plain text wins the first; where the bytes sit decides the second.

Format first. Benton makes the arithmetic vivid: "War and Peace has more than 560,000 words, but you can cram them all into 3.2 megabytes as plain text."¹¹ The weight of a modern page is everything wrapped around its words: images, video, ad scripts, fonts, trackers. In a disaster, the wrapping is what fails to arrive.

The words were never the weight.

The discipline is measurable today: as of June 10, 2026, NPR's text-only front page transfers about 5,900 bytes — under six kilobytes for a national news summary.¹² Terence Eden, a UK government technologist, stated the ethic behind that kind of number in 2021: "But the GOV.UK pages are written in simple HTML. They are designed to be lightweight and will work even on rubbish browsers. They have to. This is for everyone."¹³

Location is the half a lite site cannot fix. Even a 21-kilobyte page must still travel from a server, through the very infrastructure the disaster is dismantling. When nearly half a region's cell sites are dark,³ some readers reach nothing at all. The only copy of a document that needs no network is the one already on your device.

The lesson outlived the storms: the 2026 lite-site wave

The lesson now resurfaces between disasters, not just during them. Across the first half of 2026, four separate front-page Hacker News threads — a Helene survivor's account, an under-10-kilobyte emergency site, a plain-text retrospective, an HTML-first rebuild — carried the same argument: the lightest version of the web is the one that works.

Winn's Helene retrospective reached the Hacker News front page on January 5, 2026, under the title "During Helene, I just wanted a plain text website," collecting 346 points.¹⁴ In February, a Show HN presented safe-now.live, an ultra-light emergency-information site whose title promised under ten kilobytes; it measures about 10 kilobytes as of this writing.¹⁵

In April, an essay by the designer Marcin Wichary, author of Shift Happens, drew 319 points under the title "Plain text has been around for decades and it's here to stay." His case reaches past emergencies: "There is a certain power and longevity of monospace plain text that's worth celebrating – not just because the file format is portable, but because text editing as interface is so well-known and potent."¹⁶

And on June 10, 2026, "Building an HTML-first site doubled our users overnight" sat on the front page at 490 points.¹⁷ Its author, Alistair, the developer behind mohkohn.co.uk, is writing about an unnamed utility client, so read the numbers as texture rather than benchmark. His principle stands on its own: "It is not acceptable to bounce users on old browsers, users with bad network connections, users using assistive technologies."¹⁸

None of these threads ran during a hurricane.

What began as emergency response is settling into design principle: build the light version first, because the light version is the one that reaches everyone.

What this means for the records you keep

The same two properties decide whether your own records are available in an outage: what format they are in, and where they live. A plain-text file stored on your own device needs no connection, no server, and no company's uptime. That is not a feature you subscribe to — it is a property of the file.

News organizations solved their half of the problem by changing format. You can solve yours by changing location too. A note that lives behind a login on someone else's server is available only at the intersection of your connection and their uptime. A note that lives as a plain Markdown file on your own device is available whenever the device is.

The point is structural, not survivalist.

Honest scope matters here. An app that stores notes locally, including a browser-based one, works offline once it has loaded; the first visit still needs a connection. And no note app is emergency infrastructure: this is not disaster-preparedness advice, and for actual emergencies you should follow official guidance such as ready.gov. The durable claim is smaller: plain files you can open with anything, kept where there is no network between you and them.

Three moves carry the principle home:

• Keep the records you would actually reach for (key notes, contact lists, reference documents) as plain text or Markdown on a device you control, not only behind an account.
• Copy substance, not pointers. A bookmark is a dependency on a server; the text itself, saved into a note you own, is not. Link rot is the slow-motion version of the same failure this essay describes.
• Choose tools that read and write open formats, so the file outlives the app as well as the outage, the same instinct behind the plain-files revival.

Frequently asked questions

Why do news sites go text-only during disasters?

Because disasters break bandwidth exactly when demand for information spikes. After Hurricane Helene, the FCC reported 48.7% of cell sites out of service in the impacted areas of North Carolina.³ A multi-megabyte homepage cannot cross a connection like that; a 21-kilobyte text page can. Text-only versions keep the news reachable.

Which text-only news sites still exist?

NPR's text.npr.org, launched as thin.npr.org in June 2005 in response to the September 11th attacks,⁴ and CNN's lite.cnn.com, created during Hurricane Irma in 2017,⁵ are the standing answers. NPR's Grove platform, which powers more than 200 local stations' websites, added a text-only mode ahead of Hurricane Milton in 2024.⁹

How small can a useful page be?

Smaller than almost anything the modern web ships. NPR's text-only front page transfers about 5,900 bytes as of June 10, 2026.¹² The safe-now.live emergency site measures about 10 kilobytes.¹⁵ For scale: Joshua Benton notes that War and Peace, at more than 560,000 words, fits in 3.2 megabytes as plain text.¹¹

Does a text-only site work when the network is completely down?

No — and that is the honest limit. A lite site fixes format, not location: its bytes must still travel from a server through whatever infrastructure remains. When a connection exists but is weak, light pages get through. When there is no connection at all, only the copies already on your device are available.

Will my notes work offline in an outage?

It depends on format and location. Notes stored as plain files on your own device are readable without any network. Apps that store notes locally, including browser-based ones, keep working offline once loaded, though the first load needs a connection. Notes that live only on a server are unavailable whenever it is.

Is keeping plain-text records the same as emergency preparedness?

No. This essay describes a structural property of formats and storage, not a disaster plan. For actual emergency preparedness, follow official guidance such as ready.gov and FEMA. Plain local files simply remove one dependency: the network. That property is useful on any ordinary day, not only on a bad one.

Every few years a storm strips the web down to what actually works, and what survives when the network fails is always the same thing: plain text, small and close. Availability is not a feature you subscribe to. It is a property of format and location — and you can choose both.

If you want your notes to carry that property, mnmnote.com keeps them as open Markdown stored locally on your own device — readable offline once loaded, exportable as plain files that open anywhere.