laurent22/joplin

Joplin is a mature option for people who want their notes in plain Markdown files they control, across desktop, mobile and terminal, rather than locked inside a single vendor's service. Its main draw is combinable: local Markdown plus sync to storage you already pay for.

The problem

You accumulate notes on a laptop, a phone and perhaps a terminal session, and want one searchable, tagged library that is the same everywhere. Many note apps solve this by storing everything in a proprietary cloud, which makes export and self-hosting awkward. Joplin stores notes as Markdown and syncs through a target you choose. The editing and searching stay roughly the same; what changes is where the canonical data lives and how you move it between devices. The result is a notebook collection you can open in a text editor as well as in the app.

What's different

The project's distinguishing choice is Markdown-first storage combined with pluggable synchronisation. Notes are searchable, can be copied, tagged and modified from the applications or from your own text editor, and the sync layer supports several backends (Dropbox, OneDrive, Nextcloud, WebDAV among the listed topics). That matters if you already have Nextcloud or a WebDAV server and do not want another subscription: the app becomes a client over storage you administer. For a personal note archive, that also means an exit path that does not depend on a proprietary export wizard.

The trade-off arrives with end-to-end encryption and client versions. A July 2023 Hacker News report described a Joplin sync-encryption update that required every client synchronising to the same target to update before it could decrypt content pushed by newer clients; the commenter described it as a temporary morning surprise, not data loss (commenter report, on the thread). That is the ongoing care cost of this design: multiple devices mean keeping the clients roughly in step, and a stale install can appear broken until updated. Markdown storage itself is well documented (Markdown notes), but it does not remove the need to manage sync configuration and encryption state deliberately.

Who should try it

Good fit: a developer or technical user with several devices and an existing Nextcloud, WebDAV or cloud-drive account, who wants Markdown notes and is comfortable checking that each client is current after sync-encryption changes. The terminal build also suits people who already live in a shell.

Poor fit: someone who wants a zero-configuration consumer notes app and never wants to think about encryption versions or sync targets. For them, the setup and the cross-client update discipline are more overhead than the Markdown payoff. The project's documentation site is the place to confirm which sync targets and clients are currently supported before committing a large archive (project documentation).

Requirements and limitations

This is a notes application, so the real constraints are setup and upkeep, not hardware. You need to pick a sync backend and configure it on each device; the available list is long but not universal, so check yours against the docs rather than assuming. If you enable end-to-end encryption, every client that syncs to the same target must be updated together when the encryption scheme changes, as the 2023 report illustrates; that is a maintenance obligation, not a one-time setting.

Storage is Markdown, which is excellent for portability but means formatting that depends on a rich-text model may not round-trip identically, and editing through external tools can change files outside the app. A large archive also depends on the sync backend's performance and conflict handling, which the README does not evaluate. Plan for periodic checks that sync is actually completing on each device, not just that the app opens.

HotRepo's take

HotRepo's recorded history is thin: one daily-board observation, 2026-10-26, at 56,877 stars with +22 that day. That single dated snapshot cannot establish whether interest is rising, falling or steady. Separately, the project has been around since January 2017, so this is not a new experiment. The useful pre-commitment check is the documentation's current sync-target and client-version guidance, because that is where the maintenance cost actually shows up.