VoidPaste vs PrivateBin

PrivateBin is the self-hosted gold standard for browser encryption. VoidPaste offers optional client encryption on a hosted service plus accounts and API keys.

This comparison sticks to documented, shipped VoidPaste behavior — no fake migration stats or features we do not run.

Create a VoidPaste · All alternatives · privatebin.info

Side-by-side

	VoidPaste	PrivateBin
Primary job	Hosted paste with optional client encryption, accounts, API/CLI	Self-hosted paste where the server stores ciphertext by design
Account	Optional identity for private ACL pastes and history	No VoidPaste-style SaaS accounts — you run the instance
Privacy	Optional AES-256-GCM; also password/private/unlisted modes without encryption	Client encryption by design; optional password; burn-after-reading
Expiration / burn	Presets, max views, burn — API-enforced	Configurable expiry including forever and burn-after-reading
API / CLI	REST + Go CLI — First-class REST + Go CLI on voidpaste.com	Instance HTTP API / tooling varies; primarily a self-hosted web app
Cost / limits	Free hosted; we pay ops	Free software; you (or a public instance operator) pay hosting

Choose VoidPaste when

You want hosted convenience with optional encryption, not another VM to patch.
You need accounts, collections, versions, and scoped API keys.
Ephemeral sharing for a team that will not self-host PrivateBin.

Choose PrivateBin when

You must control the instance and accept operating PHP/web stack yourself.
Your threat model requires self-hosted zero-knowledge-style paste as the default.
You already run a PrivateBin you trust for your org.

Trusting JavaScript either way

Client encryption on VoidPaste or PrivateBin still means trusting the JavaScript the page serves. PrivateBin wins when you control that delivery path. VoidPaste is not a drop-in PrivateBin replacement. See /security and /private-paste for modes we actually ship.

Try it

Create a paste · Security model · Private & encrypted pastes