Part of our Section Store Alternative — the Honest Comparison.
If you are shopping for a Section Kit alternative, it is worth separating two questions that get bundled together: which library has the sections I want, and which approach keeps those sections working as my store changes. The first is a matter of taste and catalog. The second is architecture, and it is the one that determines whether you are re-doing work after your next theme update.
Section Kit is a well-known library of pre-built Shopify sections. Like most section libraries, it installs sections by copying files into your theme. That is a reasonable, widely used design — but it carries a specific trade-off that only shows up later, when you update or switch your theme. This article lays that out without spin and shows the alternative architecture, so you can choose on how your store actually operates.
Start with the mechanism, not the section count
Two apps can offer nearly identical catalogs and still behave completely differently the day you update your theme, because the difference is not the sections — it is where the section's code lives.
- File-based apps write
.liquidfiles into your theme'ssections/folder when you add a section. The section becomes part of your theme code. - App-based apps render the section from the app through a Theme App Extension. Your theme only stores a small reference; the markup stays in the app.
Both make the section appear in the theme editor. Both let merchants configure it with no code. The divergence is entirely in what happens when Shopify replaces your theme files — which it does on every theme update and every theme swap.
The one comparison that matters
Everything else is downstream of this table.
| File-based (copies into theme) | App-based (renders from app) | |
|---|---|---|
| Survives an app uninstall | Yes | No |
| Survives a theme update / swap | Not reliably | Yes |
| Code location | Your theme files | The app |
| After you update the theme | You may need to re-add the section | Nothing to do |
A file-based section is genuinely yours after install — uninstall the app and the file remains. But when you update the theme, Shopify publishes a fresh copy of the theme's files, and hand-added or app-copied files in the previous copy are not merged in. That is standard Shopify behavior, documented in does a theme update delete your customizations, not a defect in any particular library.
An app-based section reverses both outcomes: a theme update or swap leaves it untouched, but it renders only while the app stays installed.
Choosing your alternative
Pick the architecture that matches your update habits, not the one with the longest feature list.
- Set-and-forget on a stable theme. File-based is fine, and the no-dependency property is a real benefit. Keep a short list of every section you added so you can re-apply them if you ever update or change themes.
- You update or redesign regularly. App-based removes the re-apply chore. The section is one object that persists across every theme version, so theme updates stop being a moment where things quietly break.
- The section is critical. For anything you cannot afford to lose to a routine update — a spec table, a legal disclosure, a revenue-driving upsell — app-based rendering is the safer default.
There is no universally correct answer, and it is fair to run a file-based library for disposable, one-off blocks while using an app-based approach for the sections you depend on.
Where SectionGuard fits
SectionGuard is the app-based choice. It renders your custom sections from the app via a Theme App Extension instead of copying them into your theme, so a theme update or theme swap does not wipe them — while merchants keep configuring everything in the standard theme editor. The honest limitation is the one shared by every app-based option: the sections render while the app is installed.
If surviving every theme update is the property you are optimizing for, that is the trade SectionGuard is built around — see what it does. If you want a fuller side-by-side of the two models before deciding, read file-based vs. app-based sections or the closely related Section Store alternative breakdown.