Paste Share
Share code, logs, or configs via an expiring link, with optional encryption (server can't read it).
Without the encryption option, the content, title, and language are sent as plain text and stored that way on the server until the paste expires — the simplest mode, meant for code without sensitive information, and the only one that can be edited later on the management page. With encryption on, everything is encrypted here in your browser before sending (same technique as Secret Share): the server only stores encrypted blobs, and the key travels in the link's fragment (after the #), which never reaches it — so once created, that content can't be edited on the management page (only the expiry and burn-after-reading option stay editable). The full mechanism is in "How Paste Share works", below.
Visible to anyone with the link.
How Paste Share works
Paste the code, log, or configuration and choose the link's options (title, language, expiry, encryption, and burn after reading). By default, the content is sent as plain text and stored that way on the server until it expires — the simplest mode, just like a regular pastebin. If you turn on encryption, the browser generates a random key and encrypts everything locally with AES-256-GCM before any upload; the generated link then combines two things: the paste's address (which the server knows) and the decryption key in the fragment, after the # (which the server never sees).
Why encryption is optional (and what it actually protects)
Unlike Secret Share — whose only reason to exist is confidentiality —, Paste Share exists first to share code and reference text, a use case that's rarely sensitive. Encryption here has a specific scope: it protects the content against the server itself — not even Nexinon can read it, even if the database were compromised — but it doesn't restrict who can see the link. The decryption key travels inside the link itself (in the fragment, after the #), so encrypted or not, anyone with the link reads the same content. Whoever needs real access control — a password shared separately from the link, given only to the people who should see the content — should use Secret Share, built exactly for that.
Expiration and burn after reading
Every paste has an expiry (1 hour to 30 days) — there's no "never expires" option. By default, reading is unlimited: the link can be opened as many times as needed until it expires, the expected behavior for a reference paste. The "burn after reading" option flips that for anyone pasting something more sensitive: the first time the content is revealed, the paste is deleted from the server immediately — in that case, the page requires an explicit click on "Reveal", so a link-preview bot (WhatsApp, Slack, Teams) never consumes the only read before you actually open it.
Deleting a paste before it expires
When you create a paste, you also get a management link with a management token — shown only once, never recoverable afterward. That link leads to a page where you can edit the content, title, and language (only when the paste is in plain text — an encrypted one never has the key on the management page), toggle "burn after reading", renew the expiry, or permanently delete the paste. Lost the management link? There's no way to recover it: the paste stays up until it expires on its own.
Frequently asked questions
No — it's optional, off by default. Without it, the content stays in plain text on the server, like a regular pastebin. Turn on encryption when you want the same zero-knowledge guarantee as Secret Share: not even Nexinon can read the content, title, or language.
No. The decryption key travels inside the link itself (in the fragment, after the #) — so anyone with the link, encrypted or not, can read the content. Encryption only protects against the server (not even Nexinon can read it); it's not access control. If you need only specific people to be able to view the content (a password shared separately from the link), use Secret Share.
Secret Share exists only to share secrets with guaranteed confidentiality — always encrypted, always with limited views. Paste Share exists to share code and reference text — plain text by default, unlimited reads by default — and gains encryption and burn-after-reading as optional features, for whoever needs them.
Yes, always — every paste has an expiry, from 1 hour to 30 days. There's no "never expires" option. With "burn after reading" on, it also disappears the first time it's revealed, whichever comes first.
There's no way to delete it early without the management link — it's the only credential for that, and it isn't recoverable. The paste stays accessible via its link normally until it expires on its own.
A set of common languages (JavaScript, TypeScript, Python, JSON, HTML/XML, CSS, Bash, SQL, YAML, Markdown, Java, C#, C, C++, Go, Rust, PHP, Ruby), picked manually from the dropdown when creating the paste — no auto-detection in this version. Outside that list, "Plain text" shows the content with no coloring at all.
Depends on the mode: a plain-text paste can be edited (content, title, language) on the management page at any time. An encrypted one can't — the management page never has the decryption key (it lives only in the sharing link), so rewriting the content while preserving zero-knowledge is impossible; in that mode, only expiry and "burn after reading" are editable.