← All use cases

Pastebin replacement

Replace Pastebin with a self-hosted version on your WordPress site

Self-hosted Pastebin clone with the same workflow but no third-party ads, no privacy leakage, no public-only default. 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 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
  • Tracking pixels + third-party scripts that fire when anyone views your code
  • Code is held by a US company subject to subpoena + takedown without notice
  • Public-only default unless you pay - which leaks proprietary snippets
  • No backup - if Pastebin loses your account or the URL changes, the snippet is gone
  • 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, 1 hour, 1 day, 1 week, 1 month
  • Password protection per paste
  • Burn-after-read (paste self-destructs after first view)
  • Revision history with side-by-side diff
  • Download as ZIP
  • Forking + starring + tagging

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

The 10-minute setup

  1. Install the free SnipShare plugin on any WordPress site.
  2. Run the setup wizard - pick which features to enable (default: all). Pick the URL slug (default: /pastes/).
  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. Enable private pastes by default for your team role (Settings - Permissions)
  2. Set the default visibility to Unlisted so links work but the public archive does not list them
  3. Create a team Collection to organize all client-facing pastes by project
  4. Use revision history when iterating on a snippet during a back-and-forth with a client

Migration from Pastebin

Pastebin offers an account-level export of all your pastes. Process:

  1. Log into Pastebin, go to My Pastes
  2. Export individually (Pastebin has no bulk export in the free tier)
  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 the Pastebin scraping API + SnipShare’s REST endpoint. SnipShare exposes a POST /wp-json/snipshare/v1/pastes endpoint that accepts the same fields. 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.
  • Forgetting to disable public archive on private sites. If you do not want pastes findable on Google, set the default visibility to Unlisted and the /pastes/ archive to noindex (Settings - Appearance).
  • 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 upgrade to Pro

The free plugin replaces Pastebin completely for solo use. Pro adds:

  • Collections - group related pastes into named, public or private bundles
  • Advanced moderation - reported-paste queue + admin paste management
  • Rate limits per role - prevents abuse on public-facing sites
  • Enhanced BuddyPress / bbPress integration - activity feeds, oEmbed previews
  • Hooks + filters for developers - extend paste behavior programmatically

If you are the only user, free is enough indefinitely. Pro starts mattering when other people use the site.

Ship checklist

  • Plugin installed + permalinks flushed
  • Setup wizard completed, features 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.