FAQ

Yes. Pastepile is free to use and shows no ads.

No. There is no sign-up. When you create a paste you get an edit key shown once; keep it if you want to edit or delete the paste later.

Yes. Every paste is created with a one-shot edit key shown to you once at creation time. Anyone holding that edit key can edit or delete the paste. Save it somewhere safe; if you lose it we cannot recover it. Pastes are also deleted automatically when they hit their chosen expiry, and burn-after-read pastes self-destruct on the first view.

No. Pastepile tells search engines not to index paste pages (noindex, nofollow on /p/, /raw/, and embed URLs), so a paste is reachable only by its direct link, not by searching for its contents. If you want stronger guarantees, pick unlisted visibility, add a password, use end-to-end encryption, or seal it as a time capsule.

For regular pastes, yes - they are stored as plain text in our database so we can serve them back to you. For end-to-end encrypted pastes, no: the decryption key lives in the URL fragment (after #), which browsers never send to the server. We store only ciphertext.

Until their expiry, until you delete them with your edit key, or - if you chose burn-after-read - until the first view. An hourly job deletes expired pastes.

Pastepile highlights 267 programming languages, markup formats, and config files. See the full list at /languages. Pastepile also auto-detects the language from your filename when you upload.

A paste that cannot be opened until a future time you pick. It uses the public drand timelock beacon - nobody, including us, can decrypt it before the unlock time.

Yes. See the API docs for the public REST endpoints and the CLI.

Every paste has a report button. For things you cannot flag in-page, see /abuse. Copyright claims go to /dmca.

Not currently. It is not self-hostable today.