Snoq vs CryptPad

CryptPad is an impressive piece of open-source software. It's a full collaboration suite — documents, spreadsheets, whiteboards, kanban boards, surveys — and it encrypts everything end-to-end in the browser before sending it to the server. You can use the hosted version, run your own instance on a server you control, or use it without an account for basic tasks. For privacy-conscious users who need to collaborate, CryptPad occupies a genuinely unique position.

Snoq does none of that. There's no server, no collaboration, no web interface, no account. It's a native Windows app that encrypts your notes with AES-256 and Argon2id before writing them to disk. Nothing is transmitted anywhere, ever. There's not even a network connection in the application.

These tools are genuinely different in what they're for. The interesting comparison isn't which one is better — it's about understanding which definition of "encrypted notes" matches your actual situation.

What "encrypted in the browser" actually means

CryptPad's end-to-end encryption works: the cryptographic operations happen in your browser before data reaches the server, and the server genuinely cannot read your documents. This is technically sound and has been independently reviewed. It's a meaningful improvement over services that encrypt in transit but store data in plaintext.

That said, browser-based encryption involves a subtlety worth understanding. The JavaScript code that performs the encryption is delivered to your browser from a server each time you visit. If that server were compromised, it could theoretically serve modified JavaScript that exfiltrates your data before encrypting it. CryptPad mitigates this with open-source code you can audit and with self-hosting, but the trust model is more layered than local-only encryption.

Snoq's encryption happens on your machine, from code that was installed once and runs locally. There's no server delivering encryption logic, no network request during operation, and no opportunity for a remote actor to interfere with the encryption process. The tradeoff is that you can't collaborate with anyone — but the trust model is as simple as it gets.

Collaboration vs personal notes

CryptPad is fundamentally a collaboration tool with strong privacy properties. Real-time co-editing of encrypted documents, shareable links, multiple document types, team drives — these features exist because CryptPad is designed for people who need to work together on sensitive material. Journalists, lawyers, activists, research teams. The collaboration is the point.

Snoq is designed for one person writing notes they don't want anyone else to read. There's no sharing, no co-editing, no shareable links. If you tried to use Snoq for what CryptPad does, you'd immediately hit walls. If you tried to use CryptPad for what Snoq does — a private, offline-first encrypted notepad — you'd be using a complex collaboration platform for a simple personal use case, and you'd be doing it in a browser tab.

Web app vs native desktop

CryptPad's web-based nature is one of its strongest features: it works on any operating system, any device, without installation. You open a browser and you have an encrypted collaborative workspace. For cross-device access and cross-platform compatibility, this is genuinely hard to beat.

It also means CryptPad requires a browser, and the cloud version requires an internet connection. The experience is a web app — very good for a web app, but with the startup time, browser overhead, and offline limitations that implies. CryptPad can be used somewhat offline once loaded, but it's designed around connectivity.

Snoq is a native Windows application. It starts in a second, uses minimal memory, works completely offline, and integrates with Windows as a first-class citizen. It will never work on Linux or macOS. That narrow focus on Windows is what lets it feel like a real desktop app rather than a web page.

Side-by-side comparison

Where CryptPad has the edge

• Real-time collaboration on encrypted documents. Share an encrypted document link, edit together in real time, and neither the server nor any eavesdropper can read the content. This is something Snoq cannot do at all.
• Cross-platform via the web. Any browser, any OS, any device. No installation. This is the widest possible reach for a private notes tool.
• Open source and self-hostable. Run your own CryptPad instance on a server you control, audit the code, and remove the need to trust the cryptpad.fr infrastructure entirely.
• Multiple document types. Rich documents, spreadsheets, presentations, whiteboards, kanban boards, surveys — all encrypted. CryptPad is a full encrypted productivity suite, not just notes.
• No install required. For users who can't or won't install software, the web interface provides access from any computer.

Where Snoq has the edge

• Truly offline — no network connection, ever. Snoq doesn't make any network calls. There's no server to breach, no JavaScript to tamper with, no traffic to analyze. The encryption happens entirely on your machine.
• Native app, not a web app. Faster startup, no browser overhead, lower resource use. Feels like a desktop app because it is one.
• Simpler trust model. The code runs locally from a binary you installed. No server delivers the encryption logic to your browser on each session.
• No account required, ever. Not even for basic use — Snoq has no concept of accounts or user identities.
• Zero telemetry. Snoq doesn't collect any usage data. There's no infrastructure to run such collection because there's no network connection.

So which one should you pick?

If you need to work collaboratively on sensitive documents — with colleagues, clients, or collaborators who need to access and edit the same material — CryptPad is the right tool. It's doing something genuinely important in the privacy space: making encrypted collaboration accessible without requiring everyone involved to use the same app or trust a central server with their data.

If you need personal private notes on Windows that never touch a network under any circumstances, Snoq is the more direct answer. The absence of network connectivity is an architectural guarantee, not a policy. No configuration can accidentally enable it because it doesn't exist.

These tools are doing different jobs, and recommending one over the other without knowing your situation would be misleading. The question to ask is simple: are you writing alone, or with others? That single answer points you to the right tool.