What happens to your pages when you uninstall a page builder

Disclosure: we build Menaks, one of the tools discussed here. Every statement below about another vendor is quoted from that vendor's own documentation, with the link beside it. All pages read September 17, 2026.

What actually happens when you uninstall

There is no single answer. One builder deletes every page it created the moment you confirm. Another keeps your pages, and its own code in your theme along with them. A third gives you a grace period, then moves everything to a trash bin. Nothing in Shopify decides this. Each vendor picked its own behaviour.

Two things are at stake, and you probably only think about the first. There is the page itself: the layout and copy a shopper sees at a URL. Then there is the code the app wrote into your theme while it was installed. A builder can take away one, leave the other, or do both.

What each builder says in its own documentation

The vendor's own help centre is the source worth trusting here. It is a written commitment, not a marketing claim. Six of the larger Shopify page builders write down what happens, in a help article or a pricing-page FAQ, and the six answers differ in ways that matter. What follows is quoted directly, each line with its source page.

• PageFly — "All pages and sections created with PageFly will be removed from your store", your store "will revert to using default theme templates where PageFly was previously active", and "This deletion is immediate upon confirmation and is irreversible." The article notes this applies when you remove the app together with its data; removing it from Shopify's settings keeps it 24 hours. help.pagefly.io
• GemPages — "Uninstalling GemPages can impact your live pages by removing certain files and scripts, potentially causing display issues due to Shopify's setup." It recommends downgrading to the free plan instead; with more than one published page, re-publishing any of them "will not be permitted" there. help.gempages.net
• EComposer — "Within 48 hours, the pages/templates you created in EComposer will remain accessible and fully functional on your store. After 48 hours, the pages/templates will be moved to the ‘Trash’ of the app and will be permanently deleted after 30 days." The same article adds: "There is no way to restore them at this point." help.ecomposer.io
• Replo — publishing writes "page templates, section files, and other support files" into your theme. On removal, "Shopify does not enable Replo to clean up unused files, so they may stay around unless they're removed manually." Existing pages remain, but you can no longer publish. support.replo.app
• Shogun — published pages stay, "served up as pure HTML", but "some Shogun files & code will remain in your theme to ensure the saved content will continue to display correctly." Editing those pages outside Shogun can strip their styling. getshogun.com
• Instant — its pricing page says existing pages "will continue to be available" after an uninstall, but that "the Instant branding badge will become visible on all Instant pages and pages that use Instant sections" and that you "won't be able to edit these pages or create new ones using the Instant editor". A page you paid to keep unbranded gets the badge back. instant.so

Deletion, survival with leftovers, a grace period: these are not variations on one theme. Several smaller builders publish nothing on the subject at all. That is its own kind of answer. Compare builders on features and price if you like, but this is the line that decides what you still own in a year. Reading help centres this way settles other arguments too. It is how we established what these same vendors document about evergreen countdown timers.

Leftover code is a separate question from leftover pages

Shopify states the general case plainly: "Some apps add code to your online store theme that isn't automatically removed when you uninstall the app", and it advises contacting the developer first. Leftover files are normal, expected and documented. They are not a sign that something went wrong. help.shopify.com

There is one clean exception. When an app is built as a theme app extension, Shopify's developer documentation says that "when merchants uninstall apps, blocks associated with the apps are automatically and entirely removed from online store themes". Those blocks were never copied into your theme files in the first place. shopify.dev

The leftovers come back months later, at theme update time. Shopify's theme update guide counts "automated code changes that an app which you installed on your store has made to your theme files on your behalf" among the changes that may not carry over, and says you "need to copy them to the new version of your theme" yourself. It also warns that "some apps might not be compatible with a new theme". help.shopify.com

Why nobody can tell you how much a builder slows your store

Search for page builder performance and you will find confident scoring tables. We looked for the study behind those numbers and could not find one. There is no independent, reproducible, commercially disinterested benchmark of Shopify page builders. The figures in circulation come from agency blogs, or from companies selling a competing product. Usually with no stated method.

Those numbers also sit badly with Shopify's own rule for listed apps: "Your app shouldn't reduce Lighthouse performance scores by more than 10 points." That is a publishing requirement, and Shopify says it checks by "measuring the Lighthouse score before and after the app is installed". A blog claiming several times that figure is claiming, in passing, that Shopify's review missed it. shopify.dev, app requirements · shopify.dev, storefront performance

One more thing about that number in your admin. The Online Store Speed score is built from your home page, a product page and a collection page. A landing page is none of those. So a landing page builder can leave that score untouched and still change the page you send your traffic to.

How to measure the impact on your own store

Your store, your theme, your apps: that is the only test environment whose result applies to you. The procedure below takes about half an hour and needs nothing but Chrome. What it gives you is a number you can defend, because you can run it again against any builder.

1. Duplicate your live theme. Work on the copy. Everything below happens on the duplicate, so your storefront is never the experiment.
2. Take the "before" reading. Open the duplicated theme's preview URL in an incognito window and run Lighthouse from Chrome DevTools with the mobile preset, at least three times. Record the median score, not the best one.
3. Install the builder and publish one page on the duplicated theme — a real page with your real product, not the vendor's demo content.
4. Take the "after" reading on that same URL, same window type, same device preset, same number of runs, same median.
5. Count what was added. In the DevTools Network panel, filter by JS and CSS, reload, and look for files carrying the vendor's name; count them and add up the transferred sizes.
6. Compare against Shopify's own bar. A drop of more than 10 Lighthouse points is outside what Shopify asks of listed apps. For reference, Shopify's guidance for theme app extensions recommends keeping compressed JavaScript under 10 KB.

Treat a single Lighthouse run as noise: a developer on Shopify's own community forum reported in July 2025 that they could not reproduce a drop Shopify's review team had measured. community.shopify.dev

Five questions to ask before you install

Every answer above is easier to get before you have six months of work inside a tool. Ask the vendor these five in writing, or find them in the help centre, and keep the answers. Three of them are about the day you leave. Nobody asks about that day while choosing.

• 1. If I uninstall, do my published pages survive, and where is that written down? A link to a help article is an answer; "of course they do" in a chat window is not.
• 2. Where does the content live — in my theme, or in your database? This decides whether your page is a file you own or a record you rent.
• 3. Can I edit the page in the Shopify theme editor without your app? If not, every future edit needs an active subscription.
• 4. Which files does the app write into my theme? Ask for names or a naming pattern, so you can find them later.
• 5. What happens to those files when I update my theme? Shopify does not guarantee app-made code changes carry over, so this answer tells you what a theme upgrade will cost you in manual work.

Where Menaks sits, and what it leaves behind

Menaks publishes into your active theme as an ordinary Online Store 2.0 JSON template and hands you a direct link to it in the Shopify theme editor. The page lives on your own domain; there is no Menaks-hosted URL. Remove the app and it keeps rendering, because the sections and styles it uses are files in your theme, not calls to our servers.

Here is the other half, which follows from the same design.

• It leaves files behind. Menaks uploads 37 section files and 33 stylesheet and script assets into your theme, and they stay. Shopify revokes the app's API access the moment you uninstall, so it has no way to delete them afterwards. Removing them is a manual job.
• A theme app extension would leave more cleanly. Apps built that way have their blocks removed entirely by Shopify. Ours are theme files, so they do not get that treatment. If leaving no trace is your priority, that architecture beats ours.
• Theme updates are your job. Menaks falls squarely into what Shopify calls automated code changes an app made on your behalf — the kind that may not carry into a new theme version. Test updates on a duplicate first.
• Not every theme file is untouched. The page is written into your active theme, not a copy. Two further changes — the footer and turning your home page into a landing page — happen only if you tick the box, and the previous version is backed up first.

None of that makes the tool a bad choice. It makes it a known one, which is the point of this article. The same question about language support, what a vendor documents rather than what it markets, is answered separately.

A checklist for the day you leave

Whichever builder you are removing, switching tools or just clearing one out, the same short sequence protects you. It costs ten minutes. That is the difference between a planned migration and a Monday morning spent discovering that three product launches now return a bare default template.

• Read the vendor's uninstall article first. Look for the word "irreversible". That one word decides whether a mistake is undoable.
• Duplicate your live theme. A free snapshot of everything as it stands, including the app's files.
• Save the page outside the app. Copy the text, download the images, screenshot the full page at desktop and mobile widths.
• Check whether downgrading beats uninstalling. At least one vendor recommends its free plan over removal, because removal takes the files with it.
• Verify on the storefront afterwards. Open every affected URL in an incognito window once the app is gone.