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. The snippet library has ready-made ones, and generators make post types, redirects, schema and tracking codes from a form.

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, and Snipfire adds no database queries to your pages. CSS and JavaScript can be served as cached, minified files. Loading a switched-on snippet costs about 17 microseconds, so even a site with 3,000 snippets switched on adds about 50 ms, and the editor stays quick with thousands of snippets.

What your snippets themselves do is up to them, of course. With Snipfire Pro, snippet performance shows what each one costs.

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. Elementor has a Snipfire snippet widget, Bricks an element (beta), and CSS autocomplete offers your theme's and builder's colours and fonts: see Page builders.

Does it work on multisite? #

Yes. Each site has its own snippets. Only super admins have full access on a network. With the Agency plan, super admins can also write network snippets that run on every site.

What do I need? #

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

Does Snipfire contact any outside service? #

Only for updates. Twice a day Snipfire asks snipfirewp.com which version its download link serves: one request that sends nothing about your site. When you update, it downloads the zip and its signature. Turn the check off with define( 'SNIPFIRE_DISABLE_UPDATE_CHECK', true ); (see Updating Snipfire). The only other request 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, GitHub or GitLab if you set up Git sync, your client sites if you use the agency hub, and your AI provider only when you click a button of the AI assistant.

Some library snippets and generators add a service's code to your pages (Google Analytics, Meta Pixel…). They only run once you add your own ID and switch them on, and then your visitors' browsers load that service, as with any tracking code.

How do I update Snipfire? #

Like any plugin: new versions show on Dashboard → Updates and the Plugins screen, and automatic updates work. Snipfire's own updates are signed (from 0.17.0 on), and Snipfire checks the signature before anything is installed; Snipfire Pro's updates come from Freemius. Coming from 0.15 or earlier, update once by uploading the new zip. See Updating Snipfire.

What if I want to stop using Snipfire on a site? #

Export your snippets as a plugin: a normal WordPress plugin that runs them without Snipfire. Or export them as JSON to keep them.

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 run a snippet on a schedule? #

With Snipfire Pro, yes: a PHP snippet can run every N minutes, hourly, twice a day, daily or weekly, with a run log. See Scheduled snippets. Without Pro, the Scheduled task generator runs code with WP-Cron.

Where do I put API keys? #

Not in the code. With Snipfire Pro, keep them in the secrets vault, encrypted, and read them in PHP snippets with snipfire_secret( 'name' ). They never appear in exports, Git or the history.

Can AI help me write snippets? #

Yes, in two ways. With Snipfire Pro, the AI assistant in the editor explains snippets, fixes errors and writes new ones, with your own API key. And any AI assistant that speaks MCP, such as Claude Desktop, can work with your snippets through WordPress abilities, once you allow it.

I look after many client sites. Can I manage their snippets from one place? #

Yes, with the Agency plan's agency hub: push snippets to your clients' sites, see which version runs where, roll back, and check their health. No cloud service in between.

Can I use Snipfire with the keyboard, a screen reader or a phone? #

Yes. See Keyboard, screen readers and small screens.

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.

Can a client change a setting without touching the code? #

Yes. Give the snippet a settings form (a colour, a text, a list of redirects…). With Snipfire Pro, people with CSS, JS and HTML access can then change only the values, even of a PHP snippet, and click Save settings.

Can I add code to just one page? #

Yes. Open the page in the block editor and use the Snipfire panel in the sidebar, or the box under the content in the classic editor. See Page code.

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, with the library, generators, settings forms, smart tags, page-builder elements and export as a plugin. Pro adds SCSS/LESS with a live preview, settings forms on any snippet and values-only editing for clients, WooCommerce order smart tags and GA4 events, testing mode, cookie consent, the hook finder and element picker, scheduled snippets, snippet performance, the secrets vault, the AI assistant, team access, the activity log, more conditions (including Custom PHP) and longer history; the Agency plan adds Git sync, the agency hub and network snippets. See What Snipfire is and Plans.

Is there a free trial of Pro? #

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