2026.10.26
Lockbook: An Encrypted Notebook for Private Notes and Files
Lockbook combines notes, sketches, and files in an open-source encrypted workspace with sync, offline access, a CLI, and device key transfer. Its open-beta status and recovery model need review before adoption.
What it is for
Lockbook is an encrypted notebook project for writing notes, sketching ideas, and storing files in one workspace. Its README also describes syncing and offline access, making it relevant to people who want cross-device access without relying entirely on a conventional online editor. Repository metadata describes it as an encrypted notebook, with topics covering Markdown, drawing, collaboration, offline use, privacy, and end-to-end encryption.
Who may benefit
Lockbook may suit privacy-conscious individuals, developers keeping research or work notes, and users who value open formats and automation. The project provides a CLI that the README presents as suitable for Unix-style workflows involving search, editing, and scheduled backups. Rust developers may also be interested in lb-rs, which the README says has C and Java bindings. However, the official README describes Lockbook as being in open beta, so it should not automatically be treated as a mature system for critical knowledge or operational records.
Documented capabilities
The README identifies Markdown and SVG as document formats. It says files are encrypted with the user’s private key before leaving the device; the key is generated on the device and can be transferred to another device by scanning a QR code or entering a 24-word phrase. The project also supports synchronization and sharing. Release 26.10.22 lists changes related to sharing permissions, merge edge cases, search design, Apple buttons and gestures, plus iOS pinned-document and quick-create widgets.
The repository is marked with the Unlicense and is not archived. The README lists a free tier up to 25MB and a plan up to 30GB for $2.99 per month, while capacity above 30GB is marked as coming soon. It also says compression affects usage measurement, with PDFs and images potentially counting closer to their full size.
Limits and deployment considerations
The open-beta label means behavior and feature coverage may continue to change. The key-transfer workflow uses a QR code or 24-word phrase, so adopters should plan device migration, backups, and recovery before storing important material. Encryption claims alone do not establish compliance, disaster-recovery readiness, or suitability for a particular organization. The supplied sources do not confirm minimum hardware requirements, a complete platform compatibility matrix, self-hosting procedures, or an independent security audit.
For an initial evaluation, start with non-critical material and test synchronization, offline editing, sharing, key transfer, and backups across the devices you actually use. Expand only after those workflows are understood and acceptable for your risk model.
Sources
Sources checked: 2026-10-26