← All posts

Self-Hosted Pastebin Without a Second Server to Run

A self-hosted Pastebin-style paste site does not need its own server. If you already run WordPress, here is the case for adding it there, and the limits.

A self-hosted paste site does not have to mean a second server. If you already run a WordPress site, you can add paste sharing to it as a plugin, keep the code on your own domain and skip the extra box, the extra login and the extra thing to patch. This post is the business case for that choice, the situations where it is the wrong one, and what to check before you commit.

We make SnipShare, the plugin that does this, so weigh our view with that in mind. We have tried to be plain about where a separate application is the better answer.

What does self-hosted really cost you?

Most people start by looking for software, and the software is free or cheap. The real cost of a self-hosted tool is the box it lives on and the person who looks after it.

A stand-alone paste application needs somewhere to run. That means a server or a container host, a database, a web server, a certificate, backups and a way to update it. Someone has to own all of that. If you already do this for your main site, you are doing it twice. If you do not, you are about to learn how much work it is.

Each extra system also adds a login, a place for things to break and a thing to forget. A tool that nobody remembers is a tool that quietly falls behind on security updates. The question is not whether you can run another service. It is whether the paste site is worth one.

For most small teams, communities and publishers, it is not. What they want is a place to put a snippet and get a link, on a domain they own, with some control over who sees it. That is a small feature, and it fits comfortably inside a site that is already running.

Why does the WordPress route make sense?

If your site already runs on WordPress, you already have the parts a paste site needs. You have hosting, a database, accounts, roles, backups and a way to update plugins. Adding paste sharing means one more plugin on a stack you already maintain.

That brings some practical gains.

One login. Your members or team sign in once. A paste belongs to a real account on your site, so it shows up on their profile and in your user list.

One domain. A paste lives at an address on your own domain, such as yoursite.com/paste/abc123. Links you share keep working as long as your site does, and the traffic and search value stay with you.

One update routine. You update plugins the way you already do. You do not add a second application to the patch list.

One backup. Your pastes sit in the same database as the rest of your content, so the backup you already take covers them.

The community is already there. If you run BuddyPress or bbPress, SnipShare plugs into them. With BuddyPress active, each member gets a Pastes tab on their profile and a paste link renders inline in activity. A paste link also works in a bbPress reply. We cover that in the developer community playbook.

None of this is clever. It is the ordinary advantage of adding a feature to a system you already run, instead of standing up a new one.

What do you get with a paste plugin?

A paste site is a short list of features done reliably, and it helps to be exact about what SnipShare includes so you can compare it with what you need.

A paste can hold more than one file, with syntax highlighting for more than twenty languages. Each paste has one of three visibility levels: public, unlisted or private. Public pastes appear in the archive. Unlisted pastes can be read by anyone with the link and stay out of the archive. Private pastes are readable only by their author. You can add a password, set the paste to burn after it is read, or give it an expiry date.

Members can fork a paste to make their own copy and star the ones that helped them. Collections group pastes into named sets, so a library stays navigable. Every file has a raw address that returns plain text, which is handy for a command line, and a paste can be downloaded as a ZIP.

On the Developer tier and above, you also get full revision history with diffs, a REST API and oEmbed support for forums, a per-user hourly cap on new pastes, and a reports and moderation queue. Those are the features that matter once strangers can post, which is the subject of our guide to running a public paste site without a dumping ground.

If you want the full setup for replacing a third-party paste service, the self-hosted paste replacement use case walks through it step by step.

Who should not do this?

A plugin inside WordPress is not the answer to every situation, and it is better to say so.

You do not run WordPress and do not want to. Then the plugin has nothing to attach to. A small stand-alone application is a reasonable choice, and the second server is the price of it.

You need a paste service that is not tied to any site. If the goal is an anonymous, no-account service that stands alone, a dedicated application is closer to what you want. SnipShare pastes belong to the accounts on your site.

You want to run code, not just share it. A paste site stores and shows text. It does not execute it. If you need an environment to run snippets, that is a different kind of tool.

You need strict secrets management. A paste is plain text in your database. Do not store passwords or keys in one, however private it is set. A secrets manager is built for that job.

You have no one to look after WordPress. A plugin is only as safe as the site it runs on. If nobody on your side will keep it updated, a hosted service is a better choice than a neglected site.

If none of those fits you, the plugin route is probably the lightest one.

What does the upkeep look like week to week?

The honest answer is that it looks like the upkeep of the WordPress site you already have, plus a little.

Each week, update plugins as you normally would and glance at the paste archive for anything odd. Each month, check free disk space if people upload larger files, and confirm your backup includes the database that holds the pastes. Each quarter, if the site is a team library, clear out snippets that mention things that no longer exist, and rotate anything that should not have been written down.

If the site is public, add one more habit: look at the moderation queue. On the Developer tier and above, reports land there, and the per-user hourly cap slows down anyone who posts too fast. Five minutes a day in the first month is usually enough to learn what your community does with a paste site.

Compare that with a separate application, where the same list also includes the operating system, the container image, the certificate and the application’s own upgrade path. That list is not hard, but it is longer, and it belongs to nobody unless you give it to someone.

What does a paste site do for your own traffic?

A public paste is an ordinary page on your domain, with the title, description and code on it. That is a real difference from sending people to someone else’s paste service, where the page and any search value belong to that service. Pastes on your own domain build your site’s pages and keep readers on it.

We cannot promise search traffic, because it depends on what people paste and what they search for. A site that fills with careful, well-described snippets gives search engines more to read. A site that fills with unlabelled dumps does not, which is another reason to ask for a title and a description and to keep an eye on what gets posted.

Unlisted and private pastes are a different case. They are meant for people with the link or for one author, so plan on them as sharing tools and not as publishing.

What does it take to set up?

Less than a stand-alone application, and the steps are the ones a WordPress owner already knows.

  1. Install the plugin on a site you already run, and run the setup wizard.
  2. Choose the default visibility. Public suits an open paste site. Unlisted or private suits a members-only community.
  3. Decide who can create pastes. By default any logged-in member can. Editors and administrators also moderate.
  4. Pick a code theme and decide which options, such as burn after read, you want to offer.
  5. Add the archive to your menu so people can find it.
  6. Test it logged out. Make sure private and unlisted pastes behave the way you expect before you tell anyone.

The from install to first paste guide walks through the same steps from installation to a first shared paste.

How should you handle privacy?

A paste site holds code, and code often holds things you would rather not publish. A few habits keep it safe.

Keep the default visibility at the level that matches your audience. A site for a team behind a login can default to public inside that login. An open community should think about unlisted as the default so that nothing is published by accident.

Remember that unlisted is not secret. Anyone who has the link can read it, and links get shared. Use private for anything that must stay with one person, and use a password for something you want to share with a single reader.

Treat every paste as plain text. Do not store secrets in it. Put the command that fetches a secret in the paste, not the secret itself.

If you let strangers post, set an hourly cap and watch the moderation queue for the first weeks. The guide we linked earlier covers the settings in detail.

How does the cost compare over time?

We do not quote prices in a post like this, because they change, and you can read current terms on the pricing page. The structure of the cost is worth understanding, though.

A stand-alone application has little or no licence cost and a continuing cost in hosting and attention. A paste plugin has a licence cost and almost no extra hosting cost, because it runs on a site you already pay for. SnipShare is licensed by the number of sites, so there is no per-user fee and no commission on anything you do with it. A team of five and a community of five thousand cost the same in licences.

The honest comparison is your time. If you are already comfortable running a server, a stand-alone tool may cost you very little. If you are not, the time you save by not running one is the larger number.

What should you do next?

Start by asking whether you already run WordPress and whether you want to keep it. If the answer to both is yes, the lightest way to get a self-hosted paste site is to add one to that site. Try the live demo on the product site to see the paste form and a paste page before you decide.

If you want a broader view of sharing code on your own domain, the code snippet sharing overview covers the options for teams, tutorial writers and communities. If you are weighing it against a hosted service, our post on whether a paste site is safe for code sets out what to think about.

The decision comes down to a simple trade: one more thing to run, or one more feature on something you already run. For most WordPress owners the second is the better deal.