What Local-First Software Means for the Files You Own

A plain guide for readers: what the label promises, what it costs in return, and a checklist you can run on any reading app in a few minutes.

The label shows up quietly. It sits somewhere between "works offline" and "privacy-first" in an app description: local-first.

It commits the app to more than the copy suggests. Underneath the label sits a question worth asking before you hand over a single book: who holds the primary copy of your library? Your device, or a company's server? The answer decides what happens when the service changes its terms, raises its price, or shuts down.

This guide answers the question in plain language: what is local-first software, and what does it promise the files you own? From there it covers the four promises the definition makes to readers, the trade-offs those promises cost, and a short checklist for judging any reading app before you trust it with your library. Including ours.

What is local-first software? A plain definition

Local-first software keeps the primary copy of your files and data on the device you own. The app works directly on what belongs to you. The network is optional, not required: core features keep working on a plane, in a subway tunnel, in a cabin with no signal.

The contrast is cloud-first software. There the server holds the master copy, and your phone or laptop shows a view of it. Open the app and it renders data from somewhere else. Cut the connection and the view goes stale or blank.

Local-first is a design philosophy, not a badge. It grows out of two older ideas: privacy by design, where data stays where you put it unless you move it, and offline-first design, where an app is built to work without a connection before sync is even considered. When an app takes the label seriously, the question shifts from "which app has my books?" to "where do my files live?" On hardware you control, in formats you can open elsewhere.

Most explanations of local-first assume you build software for a living. Readers deserve a shorter version. Local-first apps explained in one line would read: your device holds the real copy; the network is a bonus.

The four promises of local-first reading

The definition breaks into four promises, and each one is concrete enough to test.

First, files on your device. Your books and notes live in storage you control, not just inside one app's private database. You can say where they are.

Second, offline-first reading. Airplane mode, subway, cabin: the library keeps working because it was already local. Offline-first reading apps treat the network as an enhancement, not a prerequisite.

Third, no account. You can start reading without an email address, a password, or a profile. Where there is no account, there is no account data to leak or breach. If you have ever wondered why reading apps want an account before you read page one, this promise is the alternative.

Fourth, an easy exit. Your library is not hostage to a subscription, a shutdown, or a terms change. You can take the files and leave whenever you want.

Keep these four in view. They double as evaluation criteria, and the checklist at the end of this post tests exactly them. The benefits and the tests are one and the same.

Own your ebook files: open formats make it possible

Local-first rests on file ownership, and ownership needs portable formats. To own your ebook files means keeping books as TXT, Markdown, EPUB, or PDF: file types any compatible app can open, on any platform, years from now. Copy protection changes that math. If you buy from DRM-locked storefronts, what ebook DRM means for privacy and ownership is worth a separate read.

The workflow is bring your own reading. Import files you already have, paste a passage, fetch an article link. The material was always yours; the app is a window onto it, not a warehouse.

Open formats are what make ownership durable. Books you hold as plain files survive app shutdowns, canceled subscriptions, and company pivots, because a file does not know or care which app opened it last.

One limit is worth knowing in advance. Portability sometimes trades fidelity. PDF import extracts text; it does not preserve the original page layout, and it is not a scanner. For a novel or a report, that is fine. For a textbook with diagrams arranged across columns, it is not.

The practical habit is simpler than the theory. Keep your books in ordinary folders, or in a storage location you choose. You decide where the files live. The app reads them.

The honest trade-offs

Local-first is not a free lunch. Here is what it asks in return.

Multi-device sync is the biggest real cost. Cloud tools make reading the same book across phone, tablet, and laptop feel effortless, and a local-first app does not get that for free. Some add sync between your own devices. Many leave it to you. If your reading life spans three devices, weigh this one carefully.

Feature breadth is the second cost. Mainstream cloud readers layer on cross-device highlight syncing, social features, and integrations. Minimal local-first apps skip these on purpose. Fewer moving parts is the point; fewer features is the price.

Backup becomes your responsibility. A local library lives and dies with its device, so copying your files to a second location is part of owning them.

And there is no reading in any browser. Progress and bookmarks save on the device where you read. Sit down at a borrowed computer and your place in the book is not there.

None of this is a flaw. It is a trade-off worth making for some readers and skipping for others, and what matters is choosing it on purpose. That is what the checklist is for.

Cloud-first versus local-first: a fair comparison

The cloud-first model is easy to describe. You create an account. Articles and books are saved to the company's servers. Your devices sync views of a server-side library. Pocket, Instapaper, and Readwise Reader are the familiar names in the cloud read-later category, and the model delivers: seamless multi-device sync, your reading list in any browser, zero file management.

The cost is structural. Your reading list becomes account data held by someone else, and account data can be profiled, monetized, or lost when a service shuts down or changes its terms. Reading history is intimate data. It shows what you study, what you believe, and what you are working through. None of it needs to leave the device to be useful.

Neither model is universally right. A reader on three devices may accept an account as the price of sync. A privacy-minded reader may accept manual file management as the price of ownership. Both positions are reasonable, as long as they are chosen.

Test any reading app before you trust it

Labels are claims. Tests are proof. Each of these takes a few minutes and probes one of the four promises.

1. The account test. Open the app and try to read a file. Can you, without creating an account or handing over an email address?
2. The airplane-mode test. Turn off Wi-Fi and cellular. Does the app still open your books and save your progress?
3. The file test. Can you find your books as real files on the device? Can you import your own EPUB, PDF, TXT, or Markdown?
4. The exit test. Can you export or copy your full library, files and notes, without emailing support?

Two bonus checks round it out: review which permissions the app requests, and skim the privacy policy for statements about what data leaves the device. For a deeper version of this exercise, see our ten-point checklist before you switch reading apps.

Run the tests on every reading app you evaluate, whatever its label says.

Local-first in practice: no account, no ads, no feed

SReader is a local-first focus reading app. No account · no ads · no feed. Settings, bookmarks, and reading progress stay on your device.

The reading model is pace-controlled. Import TXT, Markdown, EPUB, or PDF, paste a passage, or fetch an article link, then choose Word, Line, or Book mode and set your pace. In Line mode a complete highlighted line acts as the reading rail: it stays centered while the surrounding text keeps context visible, so your eyes hold one spot instead of hunting for it. Book mode behaves like an ordinary page when you want one. PDF import extracts text; it does not preserve the original layout or attempt OCR.

Because everything is local, your place in a book is saved where you read it, and you resume exactly where you stopped. The app is available on iPhone, iPad, Mac, and Android, and there is an interactive browser demo for trying the reading modes before you download anything.

Run the checklist on SReader first. That is the fair test. If the model fits your reading life, Try SReader.

Trust reading apps by what they do, not what they say

Local-first is a verifiable behavior, not a vibe. It means files on your device, offline-first reading, no account required, and an easy exit: four promises, each testable in minutes.

The trade-offs are equally real. Sync, browser access, and backup are things you may have to arrange yourself. Choose them consciously rather than drifting into them by default.

Your reading history is data worth protecting. Pick tools whose architecture treats it that way, and prove it to yourself with the tests. The label is a claim. The airplane-mode toggle is the answer.