docbin vs privatebin
privatebin encrypts a paste in your browser before it ever reaches the server, so the operator cant read what you sent. docbin cant say that. here is the whole comparison, including the one place privatebin genuinely wins.
the numbers
| feature | docbin | privatebin |
|---|---|---|
| encryption | none | 256-bit aes-gcm, client-side |
| max upload | 5 MB25 MB pro | not published |
| account required | never | never |
| editing | new version, old ones kept | not published |
| markdown | renders as the page | optional, with preview |
| write rate | 15/min75/min pro | not published |
| scraping api | open, no key | exists, cant post with plain curl |
privatebins numbers come from privatebin.info and the project's faq. paste size and write limits arent published because privatebin ships as software you configure yourself - those numbers are set by whoever runs the instance.
where docbin wins
- markdown built for reading
- tables, headers and code blocks render as a real page. privatebins markdown is optional and shown inside its own viewer, not built for long documents.
- a version for every edit
- privatebin doesnt publish an edit feature at all - a paste looks fixed once its posted. docbin keeps every edit as an immutable version.
- a real api, not an encryption client
- docbins scraping api takes a plain GET, no key. privatebins api exists, but a bare curl cant post to it - you have to replicate the client-side encryption yourself first.
- many files, one link
- up to 20 files (50 pro) share one docbin url. privatebins attachment is a single optional file, off by default.
where privatebin wins
- the server cant read it
- 256-bit aes-gcm happens in the browser before upload - privatebin calls itself zero-knowledge. docbin stores plain markdown; anyone with database access can read a doc.
- burn after reading
- a paste can be set to delete itself the moment its opened. docbin has no self-destruct option.
- you can run your own
- privatebin is open-source php you self-host, so nothing touches someone elses server. docbin is cloud-only.
so which one
use privatebin when the content truly cant be read by anyone but the recipient - credentials, private data, anything a server shouldnt see in plain text. its encryption is real and docbin has none.
use docbin when you want the content to render as a page, keep a version history, or bundle a few files under one link with an open api.
npx docbin push ./file.md