Share almost anything with one link
A paste site is the shortest path between "here is the thing" and "here is a link". No attachment, no account, no formatting rules. What changes between content types is not the tool, it is what you have to remove before you send it and how long the link should live.
This is the index of that. Pick the content type you are about to share and read the two or three paragraphs that matter for it.
Pick by content type
Meeting notes, error messages, a block of prose. Plain text, no formatting surprises.
Syntax highlighting for 30+ languages, plus a raw endpoint for curl and diff review.
The redaction checklist that matters most: tokens, IPs, emails, and a size limit.
Pretty-print first, share the exact bytes, keep the response intact for the reader.
Indentation is the bug. Preserve spaces exactly and watch for inline secrets.
Source is shown as text and never rendered, which is why it is safe to paste.
Env files, nginx, docker-compose, SSH. Strip, replace with placeholders, then share.
README drafts and notes with fence highlighting — no rendering, so nothing executes.
Capture your screen straight into the paste, or send the text instead of pixels.
Share a URL with the context the recipient needs, without a redirect in the middle.
One site, a few deliberate options
- Expiry — 10 minutes to one year, set at creation. The paste is deleted when it passes.
- Burn after read — deleted on the first successful read, browser or API.
- Password — stored as a bcrypt hash, never in plaintext. Send the password over a different channel.
- Unlisted — reachable only by its link, never in Recent or Trending.
- Raw text —
/raw/<id>returns the exact bytes astext/plain, so pipes and scripts work.
None of these are paid features. There is no plan to upgrade to.
What a paste is not
| You need | Use instead |
|---|---|
| Multi-file project with history | Git — a paste holds one block of text |
| A rendered document with images | A doc editor or a real Markdown host |
| A secret vault | A password manager — pastes are encrypted in transit, not end-to-end |
| A permanent archive | Your own storage — anonymous pastes are tied to a link, not an account |
| A file transfer | A file host — the screenshot attachment is the only binary upload |
Frequently asked questions
Do I need an account to share something?
No. Creating and reading pastes works without signing up. A free account adds a dashboard, folders, edit history, a public profile and API keys.
How long does a paste stay online?
Until you delete it (if you own it), until the expiry you chose passes, or until the first read for burn-after-read pastes. Anonymous pastes with no expiry stay until removed.
Can I share a screenshot without an image host?
Yes. The editor can capture your screen or a window and attach it to the paste as a JPEG. It is capped at roughly 500 KB of encoded data, so very large displays get downscaled.
Can two people edit the same paste?
No. A paste is a snapshot. Signed-in owners can edit and keep up to 20 revisions, but there is no live collaboration.