Requirements and where snippets are stored

Requirements #

• WordPress 6.5 or newer
• PHP 8.1 or newer
• A writable wp-content folder (Snipfire stores snippets there)
• Any theme and any page builder

For SCSS and LESS (Pro), PHP needs the mbstring extension. Almost every host has it; if yours doesn't, Snipfire says so when you save a stylesheet.

Git sync (Agency) talks to GitHub or GitLab over HTTPS from your server. It doesn't need the git program.

Where snippets are stored #

Snipfire keeps snippets as files, not in the database:

The folders are protected against direct access from the web. Loading your snippets on a page view is one cached file read, with no database queries.

Tools & Safe Mode → Storage shows the folders on your site, whether Snipfire can write to them, how many snippets you have and whether OPcache is on. If it says Not writable: snippets can't be saved, ask your host to make wp-content/snipfire/ writable by the web server.

On a multisite network each site has its own folder (wp-content/snipfire/site-2/ and so on).

Developers can move the storage folder with a constant: see Storage, export format and constants.

Backups #

Because snippets are files, make sure your backup includes wp-content/snipfire/. Most backup plugins include all of wp-content by default. You can also keep a copy with Export all (a JSON file of every snippet), see Export and import.

Uninstalling #

Deleting Snipfire removes its settings but keeps your snippet files: they're your code. To delete the files too, add this line to wp-config.php before you delete the plugin:

define( 'SNIPFIRE_DELETE_DATA', true );