Pautio See pricing

Home / Compatibility

Which WordPress builders Pautio has been tested with

We have tested Pautio on 15 free builders and block editors. This page says what was tested, how, and what is still untested.

Result by builder

BuilderEditionWidget visible to the guestComment saved on 4 element typesPins on reload (desktop and mobile)
Classic editorCoreYesYesYes
Gutenberg (block editor)CoreYesYesYes
ElementorFreeYesYesYes
Beaver BuilderFreeYesYesYes
BrizyFreeYesYesYes
Kadence BlocksFreeYesYesYes
GenerateBlocksFreeYesYesYes
Otter BlocksFreeYesYesYes
PagelayerFreeYesYesYes
SiteOrigin Page BuilderFreeYesYesYes
SpectraFreeYesYesYes
StackableFreeYesYesYes
Visual ComposerFreeYesYesYes
Live ComposerFreeYesYesYes
Themify BuilderFreeYesYesYes

Tested with Pautio 0.4.2. “4 element types” are a heading, a paragraph, a button and an image.

How it was tested

  1. A clean WordPress 7.1 install with the builder active and a test page made with it.
  2. One open round and one guest with a magic link.
  3. The guest comments on the four elements and we check that each comment is saved with its anchor.
  4. The page is reloaded on desktop and on mobile (390 px) and we count the pins that reappear in place.

These are automated tests in a lab environment, with the free version of each builder available on 1 October 2026. They do not replace testing on your own site.

What is not tested

  • Elementor Pro, Beaver Builder Pro, Divi, Bricks, Breakdance, Oxygen and WPBakery. They are paid products and we have not been able to test them yet.
  • Combinations with caching, security or optimization plugins.
  • Full-site-editing themes other than the default theme.

The same is expected on those builders, since Pautio relies on the page's final HTML, but we do not claim it until it is tested.

Inside the editors

Pautio does not load the widget inside visual editors (Elementor, Bricks, Divi, Beaver Builder, Brizy, Visual Composer, Live Composer, Themify, SiteOrigin, Pagelayer and others), so it stays out of your way while you edit.

During this test run we found that the widget was loading inside several of those editors. It is fixed in the code and will ship in the next plugin release.

Open your first round with your next client