Frequently asked questions

Do I need to know how to code? #

Only to write new snippets. Importing, organising, adding conditions and switching snippets on and off is point and click. Many snippets are copy and paste: a tracking tag, a CSS tweak, a snippet from a tutorial.

Will switching from my current snippet plugin break my site? #

No. Importing changes nothing: the copies arrive switched off. Switching over turns each snippet off in the old plugin and on in Snipfire, then test-loads your site. Anything Snipfire can't match exactly is left running in your old plugin until you've checked it. See Switching from another plugin.

Do my old shortcodes still work? #

Yes: [wpcode], [code_snippet], [fluent_snippet], [hfcm], Woody's [wbcr_…] shortcodes and Post Snippets' shortcodes keep working after switching over, even after you delete the old plugin. The shortcode finder shows where they're used.

What happens if a snippet has an error? #

A syntax error is caught before the snippet goes live. If a snippet crashes the site when you switch it on, it's switched straight back off. If it fails later, on the live site, it's switched off automatically and you're shown the error and its line. And safe mode always gets you back in. See How Snipfire keeps your site safe.

Does it slow my site down? #

No. Snippets are loaded from one cached file with no database queries, and CSS and JavaScript can be served as cached, minified files. What your snippets themselves do is up to them, of course.

Does it work with my theme or page builder? #

Yes, with any theme and any page builder. CSS can also load in the block editor, and shortcode snippets work in any builder's shortcode element.

Does it work on multisite? #

Yes. Each site has its own snippets. Only super admins have full access on a network.

What do I need? #

WordPress 6.5 or newer and PHP 8.1 or newer. See Requirements.

Does Snipfire contact any outside service? #

The free plugin doesn't. The only request it makes is to your own site, for the test load when you switch a snippet on. Snipfire Pro contacts its licensing service for your licence and updates, and GitHub or GitLab if you set up Git sync.

Where are my snippets stored? #

As files in wp-content/snipfire/, protected from web access, with compiled CSS and JavaScript in wp-content/uploads/snipfire/. See Storage.

What happens to my snippets if I uninstall? #

They're kept, because they're your code. To delete them too, add define( 'SNIPFIRE_DELETE_DATA', true ); to wp-config.php before deleting the plugin.

Can I manage snippets from the command line or a script? #

Yes: WP-CLI (wp snipfire …) and a REST API. AI assistants can work with your snippets too, through WordPress abilities, once you allow it.

Can I keep my snippets in Git? #

Yes, with the Agency plan: two-way sync with GitHub or GitLab, for the whole library or one folder. See Git sync. With any plan you can also export snippets as JSON.

Can my designer edit CSS without being able to touch PHP? #

Yes, with Snipfire Pro's team access: give their role CSS, JS and HTML (no PHP).

Can clients see the snippets without changing them? #

Yes, with Snipfire Pro's View only access. They can see snippets, their history and the activity log.

Is it GDPR-friendly? #

Snipfire itself sets no tracking cookies and sends no data anywhere. With Snipfire Pro, your tracking scripts can wait for cookie consent from your consent banner, and marketing scripts respect Global Privacy Control. Whether a particular script needs consent is a question for your own legal advisor.

What's the difference between the free plugin and Pro? #

The free plugin is complete for adding and managing snippets safely. Pro adds SCSS/LESS, testing mode, cookie consent, the hook finder, team access, the activity log, more conditions and longer history; the Agency plan adds Git sync. See What Snipfire is and Plans.

Is there a free trial of Pro? #

Yes, of the Agency plan, with no card needed. See Plans.