Rolling back

Every conversion can be undone. Rollback removes the Bricks version and leaves the page as it was in Elementor.

Roll back one page

Expand the page’s row and click Rollback. The Bricks version is removed and the page renders from Elementor again, exactly as before.

Your Elementor data was never modified, so there’s nothing to restore, it has been sitting there untouched the whole time.

Roll back everything

Rollback all reverts every conversion on the site in one pass, and asks first: Roll back every Bricks version on this site? When it finishes it reports how many posts were reverted, and confirms your Elementor data was untouched throughout.

Batch rollback also restores the site-wide settings the engine wrote during conversion, which single-page rollback deliberately does not, putting global settings back while other converted pages are still rendering would turn a one-page undo into a site-wide change.

Pages you edited in Bricks

This is the part worth knowing before you click.

If you converted a page and then edited it in Bricks, rollback treats that page differently: it is kept, not removed. The dashboard marks it Edited in Bricks and tells you the Bricks version was kept because you’ve worked on it since converting.

The rule is simple: rollback only removes conversions you haven’t touched. It will not delete work you did after the conversion. If you genuinely want that page’s Bricks version gone, remove it in Bricks yourself, the engine won’t make that decision for you.

Rollback and the free trial

On an unlicensed site you can have three converted pages at a time. Rolling a page back is the ordinary way to move on to a different one, you choose which pages you convert, and the Rollback button is right there. Your header and footer sit outside that count, rolling them back frees nothing, because converting them cost nothing, and the same goes for a single template that came along free with a converted page. Other templates, like popups, archives and 404s, occupy a slot just as a page does, and rolling one back frees that slot.

Re-converting instead of rolling back

If your goal is a fresher conversion rather than no conversion, you changed the Elementor original, or updated the plugin, use Convert again rather than rolling back first. Re-converting rebuilds the Bricks version from your Elementor page directly.

If you edited that page in Bricks, re-converting replaces those edits and the engine warns you before it does. Rollback keeps them; re-converting replaces them, that’s the difference between the two buttons.