Shopify · PageFly · GemPages
How to remove PageFly or GemPages from Shopify without breaking your pages
TL;DR
Don't uninstall first. Uninstalling PageFly deletes every page it published from your live store, immediately. Uninstalling GemPages can break your pages or switch them to draft. Rebuild each page with your theme's own sections, then uninstall, then remove the leftover code.
- PageFly: its uninstall removes all published content, immediately and irreversibly. What happens ↓
- GemPages: its uninstall can strip out the files your pages need, and "Uninstall Safely" sets them to draft.
- Export won't save you: neither builder exports HTML. Why ↓
- Safe order: duplicate your theme, rebuild with native sections, keep the same URLs, switch over, uninstall, clean up. The seven steps ↓
- Afterwards: search the theme code for "pagefly" or "gem",
and remove each
includeline before deleting the file it loads. Leftover code ↓
Rather not touch your theme? I'll do it for $495, paid once it's live What's included ↓
Below: what each builder actually does when you remove it, the steps in the order that keeps your store working, and the leftover files to look for afterwards.
What happens if you uninstall PageFly or GemPages?
This is the part most forum answers get wrong, because the builders have changed their behavior. Here is what each one's own documentation says today:
| Builder | Your live pages after uninstall | Source |
|---|---|---|
| PageFly | Using its in-app uninstall, all published content is removed from your theme immediately and irreversibly, and the store reverts to default templates. Closing the browser mid-way can leave a half-deleted theme. | PageFly help |
| GemPages | Uninstalling "can impact your live pages by removing certain files and scripts." Version history is erased for good. Its "Uninstall Safely" option removes the code but switches GemPages templates to Draft. | GemPages help |
| Shogun | Pages stay up as plain HTML, but forms stop working and your page data is deleted after 14 days. | Shogun help |
| EComposer | Pages keep working for 48 hours, then move to trash, and are deleted permanently after 30 days. | EComposer help |
| Replo | Pages stay live but can no longer be edited. Theme files may be left behind. | Replo help |
Checked against each vendor's help center, September 2026. Vendors change this. Re-read the linked page on the day you uninstall.
If you read "your pages will stay live", that's out of date
PageFly's help center used to say published pages would keep showing after uninstall, just without editing, and that line still turns up in search snippets and old forum threads. The current page says the opposite. Plan around the current one.
Can you export PageFly or GemPages pages?
Both builders have an export button, and neither gives you HTML.
PageFly exports .pagefly files (without images), and GemPages exports
.gempages files (v7 pages, paid plans only). Both only import into
another store running the same app. There is no "export to Shopify sections".
(PageFly,
GemPages)
Dropping to the free plan isn't a way out either, unless you have only one page: both free plans allow a single published page.
How to remove a page builder from Shopify in seven steps
1. List every page the builder controls
In the builder's dashboard, write down every published item. For each one, record:
- its URL (
/pages/about, or the product and collection templates it's assigned to) - the SEO title and meta description
- full-page screenshots on desktop and on a phone
- any forms on it, and where their submissions go
Product and collection templates are the ones people miss. If a builder template is applied to 40 products, all 40 fall back to the default layout the moment it goes.
2. Duplicate your theme
Online Store → Themes → the live theme's … menu → Duplicate. Do all the rebuilding on the copy. Customers see nothing until you publish, and you can share a preview link to check it on your own phone. (Shopify help)
3. Rebuild each page with your theme's own sections
On an Online Store 2.0 theme (Dawn and most themes from 2021 onward), each page can have its own JSON template holding up to 25 sections, which you edit by dragging them around in the theme editor. Create one template per page (Customize → Pages → Create template), then rebuild the layout from native sections:
| In the builder | Native section (Dawn names) |
|---|---|
| Hero image with heading and button | Image banner |
| Text block | Rich text |
| Icons or features in columns | Multicolumn |
| FAQ accordion | Collapsible content |
| Image beside text | Image with text |
| Product grid | Featured collection |
| Contact form | Contact form |
| Newsletter sign-up | Email signup |
| Embedded video | Video |
Two traps from doing this on real stores:
- Older themes don't have these sections. Vintage themes like Debut have no collapsible-content section, so an FAQ needs a custom section with its own schema. Check your theme's section list before you promise anyone a date.
- PageFly accordions aren't in the page source. They're assembled by JavaScript in the browser, so tools that read a page's source HTML don't see the questions at all. Copy FAQs by opening every panel on the live page, not from "view source". When I scanned PageFly stores, more than a third had accordions that source-reading tools had counted as plain text.
4. Keep the same URLs
Rebuild each page under the same page handle, so
/pages/about stays /pages/about. Nothing moves for
Google or for links in old emails. Copy the SEO title and meta description
across. If a handle does have to change, add a redirect from the old path
(search "URL redirects" in your Shopify admin).
5. Switch over in one sitting
One Shopify detail catches people out here: a page's template choice is stored on the page, not on the theme. Changing it on a page changes it on the live store too, even while you're working on the duplicate. So do the switch in one sitting:
- assign each page its new template
- publish the duplicate theme
- then check each page on a phone, send a test through every form, and search your store's HTML for the builder's name
If something looks wrong, your old theme is still in the theme list. Republish it.
6. Now uninstall the builder
Only once every page is running on native sections. Use the app's own uninstall flow (PageFly: Preferences → Account; GemPages: run "Uninstall Safely" first, then remove the app), and don't close the tab until it has finished.
7. Remove leftover PageFly and GemPages code from your theme
Shopify removes app blocks automatically, but page builders are allowed to write straight into your theme files, and an app loses access to your store the instant it's uninstalled, so it can't tidy up after itself. (Shopify help) In Online Store → Themes → Edit code, search for the builder's name and clear out what you find:
| Builder | What to look for |
|---|---|
| PageFly | snippets/pagefly-head.liquid, layout/theme.pagefly.liquid,
any file with "pagefly" in its name, PageFly lines in
layout/theme.liquid, and the "pagefly": {…} block in
locales/en.default.json |
| GemPages | v7: templates like page.gem-…-template.json. v6: files such as
gem-app-header-scripts.liquid, gem-app-footer-scripts.liquid,
page.gem-template.liquid. GemPages' own advice is to restore the
original version of any file it edited, and delete files matching "gem" |
| Replo | replo-head.liquid and its references, and files beginning "replo" |
Remove the reference before the file. If you delete
pagefly-head.liquid but leave the line in theme.liquid
that loads it, every page on your store shows
"Liquid error: Could not find asset snippets/pagefly-head.liquid".
Delete the render/include line first, save, check
the store, then delete the file. Do this on a duplicate as well if you're
unsure: "gem" matches more than GemPages, so read each file before you
delete it.
When to keep the builder
Keep paying if you build new landing pages every week for campaigns. That is what page builders are for, and hand-building each one would cost you more. The rebuild makes sense when your builder pages are finished: an About page, an FAQ, a couple of product layouts that haven't changed in a year, and a monthly bill to keep them showing.
If your only builder pages are Privacy, Refund, Terms or Contact, you don't need anyone. Shopify generates the policy pages for free (Settings → Policies), and every theme ships a contact template.
Removing PageFly and GemPages: FAQ
- Will uninstalling PageFly delete my pages?
- Using PageFly's own uninstall flow, yes. Its help center says all content published through PageFly is removed from your theme and no longer visible on your live store, immediately and irreversibly. Older advice that pages stay live but uneditable is out of date. Rebuild the pages natively first.
- Will uninstalling GemPages break my pages?
- It can. GemPages says uninstalling can remove files and scripts your live pages depend on, and that version history is erased permanently. Its Uninstall Safely option removes the code but switches GemPages templates to Draft, so those pages stop showing either way.
- Can I export PageFly or GemPages pages as HTML?
- No. PageFly exports
.pageflyfiles and GemPages exports.gempagesfiles, and both only import into another store running the same app. There's no export to HTML or to Shopify theme sections. - Will I lose SEO when I remove a page builder?
- Not if the pages keep the same URL and content. Rebuild each page under
the same handle so its
/pages/address doesn't change, carry the SEO title and meta description across, and add a URL redirect for any page whose handle does change. - Why is there still PageFly code in my theme after uninstalling?
- Shopify removes app blocks automatically, but page builders write
directly into theme files, and an app loses access to your store the
moment it's uninstalled, so it can't clean up. Search the code editor for
"pagefly" and remove what you find, starting with the include lines in
theme.liquid. - How do I fix "Liquid error: Could not find asset snippets/pagefly-head.liquid"?
- The snippet was deleted but
theme.liquidstill calls it. Openlayout/theme.liquid, search for "pagefly", and remove therenderorincludeline. Always remove references before deleting the files they point at. - Can I just drop to the free plan instead?
- Only if you have one page. The free plans of both PageFly and GemPages allow a single published page, so a store with several builder pages has to keep paying or rebuild them.