Local-First Apps: What They Are and Why They Matter
A few months ago, Capacities had a server issue. I was working on a note, the app couldn’t sync, and when things came back online, part of what I’d written wasn’t there. It wasn’t a major loss, but I panicked.
Not just when the app went offline—more so when I realized some of my notes were gone.
That experience stuck with me. I still use Capacities for personal journaling because I like the app and how it handles daily notes. But it’s part of why I moved my work-related notes to Obsidian. With local storage, there’s no server to go down. My notes are on my device, and I don’t have to worry about whether the company is having a good day.
This idea has a name: local-first. More people have started paying attention to it, especially in the note-taking space. If you’ve seen debates about Obsidian vs Notion or heard someone mention “owning your data,” local-first is usually what they’re talking about.
What does local-first mean?
Local-first (sometimes called offline-first) is a way of building software where your data lives on your device as the primary copy. The app stores everything locally first, then syncs to other devices or the cloud in the background.
The term comes from a 2019 Ink & Switch paper. Martin Kleppmann, one of the authors, later summed it up this way:
“In local-first software, the availability of another computer should never prevent you from working.”
That’s the key idea. If the company’s servers go down, your notes are still on your laptop. If your internet cuts out, you can keep working. If the app stops being developed or the company disappears, your files remain in a folder you control.
Local-first doesn’t mean local-only. These apps can still sync across devices. Some even support collaboration. The difference is that sync is a secondary feature, not a requirement. Your device holds the real data, not a temporary cache that depends on a server.
How is this different from cloud-first apps?
Most apps today are cloud-first. Your data lives on the company’s servers. The app on your device is a way to view and edit that data, but the server is the source of truth.
Cloud-first has real advantages. You can log in from any device and see your notes. Teams can collaborate in real time. If your laptop dies, your data is still on the company’s servers—you don’t lose everything just because a device failed.
But there are trade-offs.
If the server is down, you can’t access your notes. If the company shuts down or changes their pricing, you might lose access entirely. And because your data lives on someone else’s infrastructure, you’re trusting them with your privacy.
Some cloud-first apps offer offline mode. This lets you view and sometimes edit notes without an internet connection. But offline mode isn’t the same as local-first. In offline mode, the app caches data locally, but the server remains the source of truth. When you reconnect, the app tries to sync your changes back.
This is where sync conflicts happen. I’ve run into this with Capacities more than once. I’d have a note open on my phone, forget about it, and then edit the same note on my laptop. When both devices synced, the app had to decide which version to keep. Sometimes it handled it fine. Other times, whatever I wrote on my phone disappeared.
Sync conflicts aren’t unique to Capacities. They can happen with any cloud-first app that supports offline editing. The problem is structural; when two devices edit the same data without talking to each other, something has to give.
Why are more people choosing local-first?
A few reasons keep coming up.
You can access your notes anytime.
No server dependency means no waiting for a connection. Open your laptop, open the app, and your notes are there. This matters if you travel, work in places with unreliable internet, or just don’t want to depend on external infrastructure.
Your data survives the app.
Local-first apps typically store notes as plain text files, often Markdown. If you stop using the app, you still have readable files in a folder. You can open them in another app, a text editor, or just keep them as an archive. With cloud-first apps, you usually need to export your data before leaving, and the export might not preserve everything.
Speed
Reading and writing to local storage is faster than waiting for a server response. This makes local-first apps feel snappier, especially for large vaults or quick capture.
Privacy
Your notes stay on your device—or in cloud storage you control, like iCloud or WebDAV—rather than on the app company’s servers. No company is scanning your data for features or advertising. For personal journals, health notes, or work documents, this matters to a lot of people.
Sync conflicts are easier to resolve
Local-first apps that support sync are usually designed with conflict resolution in mind. Because each device has a complete copy of the data, the app can merge changes more intelligently. It’s not perfect, but the architecture handles conflicts better than cloud-first offline mode.
What are the downsides?
Local-first isn’t without trade-offs.
You’re responsible for backups
This is true for cloud-first apps too—most don’t automatically back up your data, just store it on their servers. But with local-first apps, if your laptop dies and you didn’t have your notes folder synced or backed up somewhere, they’re gone. There’s no server copy to fall back on. You need to think about redundancy from the start, whether that’s syncing to cloud storage, using a backup service, or keeping copies on an external drive.
Setup can be more involved
If you want to access notes on multiple devices, you need to configure sync yourself. That might mean setting up iCloud, Dropbox, or Syncthing, paying for the app’s own sync service, or even self-hosting your own sync server if you want full control. It’s not hard, but it’s not instant either.
Mobile can be finicky
Some local-first apps have solid mobile experiences, but syncing between desktop and phone often requires extra steps. Obsidian on mobile, for example, works well once configured, but getting there takes a few minutes of setup depending on your sync method.
Collaboration is harder
Real-time editing with teammates is where cloud-first apps still win. Local-first collaboration exists—some apps use CRDTs (conflict-free replicated data types) to merge edits intelligently—but it’s not as seamless as Google Docs or Notion.
There’s a learning curve with some apps
Obsidian and Logseq are powerful, but they assume you’re comfortable with files, folders, and maybe some light configuration. Many local-first apps also rely on plugins for features that cloud-first apps include natively. Want a kanban board, calendar view, or better table editing? You might need to find and install a community plugin first.
If you just want to open an app and start writing without thinking about setup, cloud-first apps are more user-friendly.
You need to install the app on every device
Cloud-first apps typically have web versions—open a browser, log in, and you’re working. Local-first apps usually require downloading and installing software. That’s fine on personal devices, but if you’re using a company-owned computer with IT restrictions, you might not be allowed to install third-party apps at all.
For anyone who needs to access notes on a work machine, this can be a dealbreaker.
Best local-first note-taking apps in 2025
If you’re considering the switch, here are the main options worth looking at.
Obsidian is the most popular local-first note-taking app right now, and it’s what I use for work notes. It stores everything as Markdown files in a folder you choose. The app is essentially a powerful editor sitting on top of those files—bidirectional linking, graph visualization, and a massive plugin ecosystem. Sync is available through Obsidian’s paid service or your own cloud storage, like iCloud or Dropbox.
Logseq takes an outliner approach while staying local-first. Notes are stored as Markdown or org-mode files, and the app emphasizes daily journals and block-level referencing. It’s open source with an active community. A database version is currently in development alongside the file-based storage—you can try it now, but it’s not officially released yet.
Joplin is a solid choice if you’re migrating from Evernote. It’s open source, supports end-to-end encryption, and syncs via your choice of cloud services, including Dropbox, OneDrive, or self-hosted options. The interface is straightforward without the learning curve of Obsidian or Logseq.
SiYuan stores notes as JSON files with Markdown content. It offers block-level editing, bidirectional links, and a built-in sync service while keeping local storage as the primary source. It’s particularly popular in Chinese-speaking markets but has a growing international user base.
Anytype combines local-first architecture with end-to-end encryption and peer-to-peer sync. Your data never touches company servers unless you choose their backup service. It’s open source and supports self-hosting if you want full control over your infrastructure.
On the cloud-first side, apps like Notion, Evernote, and Google Keep store your data on their servers. Some offer export options, but the primary copy of your notes lives in their infrastructure.
Capacities falls into the cloud-first category, though they’ve added offline support. You can work without internet, but the app still syncs to their servers as the source of truth. For me, that’s fine for personal journaling where I’m not worried about losing a few lines. For work notes, I prefer something local-first.
Is local-first right for you?
It depends on what you value and what you’re storing.
- Choose local-first if you work alone, care about data ownership, or want your notes to survive the app. If you’ve ever worried about vendor lock-in—losing access to your notes because a company changes pricing, shuts down, or alters their terms—local-first removes that concern. Your files stay with you.
- Choose cloud-first if you collaborate frequently in real time, want zero-friction sync across devices, or prefer not to think about where your data lives. Cloud-first apps handle the infrastructure so you can focus on the work.
There’s also a middle path. Some people use local-first for important or sensitive notes and cloud-first for quick capture or collaborative projects. That’s roughly what I do—Obsidian for work notes where I need reliability and long-term access, Capacities for daily journaling where I enjoy the experience and can tolerate the occasional sync hiccup.
Neither approach is objectively better. The right choice depends on how much control you want, how much setup you’re willing to do, and how much you can compromise.
