← All use cases

Pastebin replacement

Self-hosted pastebin on WordPress: a pastebin clone you own

Self-hosted Pastebin clone with the same workflow but no third-party ads, no privacy leakage, no paywall on private pastes. Your domain, your control.

What you are building

A self-hosted code-sharing destination that behaves like Pastebin - share a URL with code on it, with syntax highlighting, expiration controls, password protection, and burn-after-read - but on your own domain.

Same workflow as pastebin.com/<hash> but at yourdomain.com/paste/<hash>/. No ads. No tracking. No paid quota. No surprise paywall.

Why move off Pastebin

Pastebin works, but the cost adds up over time:

  • Ads everywhere - including on raw code views shared in technical discussions
  • Code is held by a third-party company under its terms, not yours
  • Private and unlisted pastes are capped on free accounts, which pushes proprietary snippets toward public
  • No backup you control - if you lose access to the account, the snippets go with it
  • Brand mismatch - your sites and tutorials send readers to a third-party domain that does not look like yours

For a solo developer, the personal cost is privacy. For an agency, the cost is brand consistency + IP control.

What you get instead

SnipShare on your own WordPress install gives you:

  • /paste/<hash>/ URL pattern (Pastebin-compatible mental model)
  • /paste/<hash>/raw/ direct-link to plain text for curl / programmatic fetch
  • 20+ language syntax highlighting via CodeMirror
  • Multi-file pastes (one URL, multiple files - like GitHub Gist)
  • Visibility controls: Public, Unlisted (link-only), Private (owner only)
  • Expiration: Never, 10 minutes, 1 hour, 1 day, 1 week, 1, 3 or 6 months, 1 year
  • Password protection per paste
  • Burn-after-read (paste self-destructs after first view)
  • Revision history with side-by-side diff (Developer and up)
  • Download as ZIP
  • Forking + starring + tagging

All running on your WordPress install. Zero third-party JavaScript.

Pastebin clone features checklist

If you are comparing pastebin clones, these are the features worth checking for. Here is where SnipShare stands on each, so you can tick them off.

FeatureIn SnipShare
Syntax highlighting20+ languages through CodeMirror, with no third-party JavaScript
ExpiryNever, 10 minutes, 1 hour, 1 day, 1 week, 1, 3 or 6 months, or 1 year
Burn after readYes. The paste is marked expired after a reader who is not the owner opens it
Password protectionYes, per paste, stored as a hash
VisibilityPublic, Unlisted (link-only) or Private (owner only)
Raw URL for curl/paste/<hash>/raw/ returns plain text
Multi-file pastesYes, one URL with several files
APIREST endpoint to create pastes, on Developer and up
Forking, starring, tagsYes

Two checks are worth making before you choose any clone. First, does it put the useful features behind a paid quota? Here there is none: no quota on private pastes and no ads. Second, can you add people later? Because this is a WordPress plugin, members are ordinary WordPress users, so logins, profiles and a community can sit next to the pastes when you want them.

Self-hosted pastebin vs a standalone app

Most self-hosted pastebin tools are small standalone apps that you run in a container or on a spare server. They are a good fit when you want one narrow tool, you are comfortable running another service, and you do not need accounts or a community around it.

A WordPress plugin fits a different situation, and it is worth being honest about which. It fits when you already run WordPress and would rather not run a second server. It fits when you want logins, profiles and a place for people to discuss the code, because WordPress already has them. And it fits when the pastes should live on the same domain, under the same brand and backup routine, as the rest of your site.

If you do not run WordPress and want the lightest possible paste page, a standalone app is probably simpler, and that is a fair reason to choose one. SnipShare is for the person who has a WordPress site and wants pastes on it. There is no per-user fee and no commission, and nothing goes through a third-party host.

Private pastes: who can see what

The word “private” covers three different protections here, and it helps to pick the one that matches the worry.

Private visibility means only the owner can open the paste while logged in. Use it for notes and snippets nobody else should read.

Unlisted visibility means the paste is not in the archive, but anyone with the link can read it. It suits a snippet you send to a client.

A password puts a gate in front of a paste, public or unlisted, so a reader has to enter it first. Send the password by a different route from the link.

You can combine these with expiry and burn after read when a link will travel. One limit applies to all of them: SnipShare does not encrypt paste content, and it is not a zero-knowledge tool. Pastes are stored as text in your own database, so the people who can reach your database or backups can reach them. The settings control who can view a paste through the site. They do not scramble it. For the wider picture, read is Pastebin safe for code.

The 10-minute setup

  1. Install SnipShare on any WordPress site.
  2. Run the setup wizard - it sets default visibility and the editor and code themes, and can add sample pastes. Every feature is on by default; switch any off later in Settings - General.
  3. Create your first paste at /pastes/create/. Verify the URL pattern is what you want.
  4. Update your existing Pastebin links if you maintain a tutorial blog - SnipShare runs alongside, so retire links gradually.
  5. Bookmark your /pastes/create/ URL or pin it to your nav so paste creation is one click away.

That is the minimum to replace Pastebin for personal use. Add BuddyPress / bbPress integration later if you want a community layer.

For agencies: brand-consistent paste sharing

If you run client work and frequently share code snippets with clients (during onboarding, in proposal docs, in support tickets), Pastebin links look unprofessional. SnipShare lets you send clients agency-site.com/paste/abc123/ which:

  • Matches your brand
  • Carries your contact info in the footer
  • Is permanent (you control the lifecycle)
  • Has no third-party tracking they can complain about
  • Routes attribution back to your site

Internal team configuration:

  1. Set the site’s default visibility to Unlisted so links work but the public archive does not list them (Settings - General). Switch a paste to Private when it is internal only.
  2. Create a team Collection to organize all client-facing pastes by project
  3. On Developer and up, use revision history when iterating on a snippet during a back-and-forth with a client

Migration from Pastebin

Pastebin lists your pastes under My Pastes. Process:

  1. Log into Pastebin, go to My Pastes
  2. Open each paste you want to keep
  3. For each paste, copy the code + title + language
  4. In SnipShare, Create Paste, paste the content, set the matching language
  5. Set visibility (most ported pastes can stay Unlisted)

For accounts with 50+ pastes, write a curl script against Pastebin’s developer API + SnipShare’s REST endpoint (Developer and up). SnipShare exposes a POST /wp-json/snipshare/v1/pastes endpoint that takes a title and a files array (files[0][content], files[0][language]), authenticated with a WordPress application password. Full schema: store.wbcomdesigns.com/snipshare/docs/developer-guide/rest-api/.

Common pitfalls

  • Permalinks not flushed. After install, go to Settings - Permalinks and click Save Changes. SnipShare adds rewrite rules; if they do not register, paste URLs 404.
  • Public pastes on private sites. If you do not want pastes listed in the archive, set the default visibility to Unlisted or Private. There is no noindex setting in SnipShare, so if the whole library should stay out of Google, put the site behind a login or membership plugin.
  • Burn-after-read assumes one viewer. If two browsers hit the URL within a second of each other (e.g. preview + actual click), one of them sees the paste, the other gets a 404. Plan messaging accordingly.
  • Image-only “pastes” do not belong here. SnipShare is text-only. For screenshots, use the WordPress media library.

When to move up a tier

Personal at $49 replaces Pastebin completely for one site, collections and the BuddyPress integration included. Developer at $79 covers five sites and adds:

  • Full revision history with diffs - see what changed between versions of a paste
  • REST API and oEmbed - post pastes programmatically, embed them in forum replies
  • A per-user hourly cap on new pastes - keeps a public-facing site from being flooded
  • Reports and a moderation queue - somewhere for reported pastes to land

If you are the only user, Personal is enough indefinitely. Developer starts mattering when other people are posting and you need history, limits and somewhere for reports to land.

A paste page is the start, and the same plugin covers a few neighbouring jobs. A developer who wants a private place for their own snippets can read the solo developer notebook setup. A team keeping code samples internal can use the team snippet intranet pattern. Writers who embed code in tutorials will want the Gist replacement for tutorials, and a community that talks about code can add the BuddyPress developer community layer. All of them run on the same install, so you can start with plain pastes and add the rest later.

Questions people ask

Is SnipShare a pastebin clone? It does the same job: you paste code, get a short link and share it. It runs as a WordPress plugin on your own domain, so the pastes live in your own database instead of on a third-party site.

Do I need a separate server? No. It runs on the WordPress site you already have. There is nothing to deploy beyond installing the plugin and flushing permalinks.

Can I keep the pastes out of Google? Use Unlisted or Private visibility so pastes are not listed in the archive. SnipShare has no noindex setting, so if the whole library should stay out of search results, put the site behind a login or a membership plugin.

Can I embed a paste in a forum reply or a post? Yes, on Developer and up, which includes oEmbed. A pasted link then renders as a paste.

How do I move my old pastes over? Copy each one into SnipShare by hand, or use the REST endpoint for a large account. The migration section above has the steps.

Ship checklist

  • Plugin installed + permalinks flushed
  • Setup wizard completed, defaults chosen
  • Default visibility + expiration set per your use case
  • First paste created + URL verified
  • Old Pastebin bookmark replaced with /pastes/create/
  • Migration plan for legacy Pastebin URLs (if any)

Then start pasting. Your code stays on your domain.