SnipShare installs like any WordPress plugin and has sensible defaults out of the box - but a handful of settings decisions made in the first 10 minutes determine how the tool behaves for you long-term. This post walks through the full setup sequence from a fresh install to a working paste you can share.
What you are installing
SnipShare is a self-hosted Pastebin/Gist alternative. The core workflow: create a paste (one or more files, each with syntax highlighting), get a URL, share it. The paste lives on your WordPress install, not on a third-party server.
What ships in Personal, the $49 entry tier:
- Multi-file pastes with per-file language and filename
- 20+ syntax languages via CodeMirror
- Three visibility levels: Public, Unlisted, Private
- Password protection and burn after read per paste
- Expiration controls: Never, 10 minutes, 1 hour, 1 day, 1 week, 1, 3 or 6 months, 1 year
- Forking, starring, and tagging
- Public archive at
/pastes/with filter by language and tag - Raw URLs at
/paste/<hash>/raw/and/paste/<hash>/raw/<filename>for curl and programmatic access - ZIP download
Step 1 - Install and activate
- Download the zip from your account on the store.
- From your WordPress admin, go to Plugins - Add New - Upload Plugin and upload it.
- Activate. The plugin creates its database tables and rewrite rules, then opens the setup wizard.
- Go to Settings - Permalinks and hit Save Changes (no change needed, just flush). This ensures
/paste/<hash>/resolves correctly.
Step 2 - Run through the settings that matter on day one
From admin - SnipShare - Settings:
Setup wizard. It sets default visibility and the editor and code themes, and can add a few sample pastes so the archive is not empty on day one.
Who can create pastes. Any logged-in member can create pastes; guests cannot. The Permissions tab lists which roles hold each ability, read-only. Developers change that mapping through the WordPress user_has_cap filter.
Default visibility. If your primary use is sharing code publicly, leave this as Public. If your primary use is a private team archive, set the default to Private - authors always override per-paste, but a sensible default saves clicks. See the team intranet use case for private-library configuration.
Default expiration. For a permanent personal library, set this to Never. For a public site where you want pastes to age out, set a sensible default (1 month) while allowing authors to override.
Code theme. Under Settings - Appearance, pick one of six: Tomorrow, Okaidia, Twilight, Dark, Coy or Solarized Light. This is cosmetic but people notice. Line numbers live under General - Editor.
Step 3 - Create your first paste
Navigate to /pastes/create/. The create form:
- Add a file. Give it a filename (e.g.
config.yaml) and pick the language from the dropdown. - Paste your code in the editor. Syntax highlighting applies immediately.
- Add a second file if needed. SnipShare treats a paste as a container for multiple related files - the same model as a GitHub Gist. A bash script with its configuration file, or three component files that belong together, all go in one paste.
- Set visibility. Public (shows in the archive), Unlisted (anyone with the link can view, not listed) or Private (only you). Add a password or burn after read (self-destructs after the first view) if you need them.
- Set expiration. For code you intend to reference later, leave this as Never.
- Add a description and tags. Both are optional but improve searchability. Tags let you filter by topic in the archive.
- Hit Create.
You land on the paste view page. The URL is /paste/<hash>/.
Step 4 - Understand the paste URLs
Each paste has three useful URLs:
| URL | What it does |
|---|---|
/paste/<hash>/ | The rendered paste view with syntax highlighting |
/paste/<hash>/raw/ | Plain text, no HTML - useful for curl and scripting |
/paste/<hash>/raw/config.yaml | Raw text for a specific file in a multi-file paste |
The raw URL is worth bookmarking as a workflow pattern. When you reference a paste in a terminal session or want to pipe it into a command, the raw URL is the one you use:
curl https://yourdomain.com/paste/abc123/raw/deploy.sh | bash
Step 5 - Share the paste
Copy the paste URL from your browser. That is the shareable link. For Unlisted pastes, only people you send the URL to can view it - it will not appear in the archive or search results.
If you need the raw URL for a specific purpose (pasting into a documentation site, linking from a code comment), use /paste/<hash>/raw/.
What revision history looks like in practice (Developer and up)
Every time you edit a paste and save, SnipShare creates a new revision. The paste view lists each version with the file, author, date and edit note, plus a Diff link that compares it with the version before.
The diff lives at /paste/<hash>/diff/1...2/ and shows the two versions side by side, per file. Change the numbers in the URL to compare any two versions. This is useful when:
- You iterate on a script over several days and want to see what changed
- You want to check exactly what an edit note describes
Quick-reference: visibility mode decision table
| Mode | Who can view | In archive? | Use case |
|---|---|---|---|
| Public | Anyone | Yes | Sharing broadly, tutorials, open code |
| Unlisted | Anyone with the URL | No | Client-sharing, internal links, not-for-public |
| Private | Owner only | No | Personal scratch, drafts |
| Burn after read (add to any level) | First viewer, then gone | No | Secrets, temporary credentials, one-time shares |
What you have after 10 minutes
- A working paste archive at
/pastes/ - A create form at
/pastes/create/ - Your first paste with syntax highlighting at
/paste/<hash>/ - A raw URL at
/paste/<hash>/raw/for scripting use - Forking, stars and tags on every paste you create from here
That is the entry tier, and it already includes the BuddyPress integration and collections that people usually expect to pay extra for. The Developer tier at $79 a year adds what you need once other people are posting: revision history with diffs, the REST API with oEmbed for forums, an hourly cap on new pastes, and a queue for reported pastes.