Shopify’s Liquid-first developer preview lets developers and coding agents read page structure directly in a template instead of reconstructing it from JSON and sections. The change introduces reusable blocks and partial page updates alongside existing themes; the reported 93% reduction concerns a new theme’s code, not measured storefront speed.
What is Shopify changing in its theme architecture?
Shopify’s developer preview moves page composition into Liquid templates, where HTML can sit alongside reusable blocks and snippets.
Shopify describes the existing arrangement as a JSON template assembling sections separately from the Liquid that renders them.
The preview’s stated benefit for coding agents is being able to read the whole template rather than reconstruct a page from a JSON file and a tree of sections.
What does the reported 93% reduction measure?
The Register reported on July 25, 2026 that Shopify’s new, then-unnamed base theme had 93% fewer lines of code than Horizon, with code mostly in HTML interpolated by Liquid.
The reported 93% figure is a source-code comparison with Horizon, not a reported reduction in page-load time, inference cost, or merchant operating expense.
Why did Sidekick influence the redesign?
The Register reported that 20% of Shopify merchants were using Sidekick to edit their themes and had made 25 million edits in 2026 at the time of its July report.
Shopify storefronts product director Ben Sehl described HTML as expressive, local, and token-efficient, according to The Register; these are his architectural arguments, not Endroid benchmark results.
The Register quotes Sehl explaining the earlier trade-off: The moment templates became JSON, they stopped being a great developer surface. They became an auto-saved output.
Sehl’s criticism was not that JSON is inherently bad, but that serialized configuration has a constrained vocabulary.
How do Liquid blocks and partials work?
Shopify’s July 21 preview announcement introduces a block tag for rendering reusable theme blocks and a partial tag for refreshing named regions of server-rendered HTML without a full page reload.
| Concern | Existing model | Liquid-first preview |
|---|---|---|
| Page composition | JSON template assembles sections | Liquid template composes blocks and HTML |
| Existing theme compatibility | Sections, settings, and JSON templates remain supported | An additional composition model, not a required replacement |
| Partial refresh | No claim here that existing themes lack dynamic behavior | Named server-rendered regions can be refreshed with JavaScript |
| Release status | Existing themes continue to work | Developer preview; behavior can change before general availability |
Shopify’s preview documentation places browser behavior in web components and describes partials as server-rendered regions that JavaScript can fetch and replace.
The preview adds Theme Check rules for syntax errors, excessive complexity, oversized files, invalid schema structure, and mismatches between block arguments, schemas, and documentation declarations.
Are JSON templates and existing themes being retired?
No: Shopify explicitly says existing themes keep working and that sections, theme settings, and JSON templates remain supported alongside the Liquid-first preview.
The Register described Shopify’s compatibility approach as a forever API
for existing Liquid themes, while Shopify’s own announcement describes the preview as an addition to the existing architecture.
How can developers try the Liquid preview?
Shopify instructs developers to create a development store with the Liquid July ’26 preview and start from the skeleton theme release candidate or add the new tags to their own theme.
Shopify warns that tag behavior and JavaScript helpers can change before general availability, so the preview should not be described as a completed platform-wide migration.
About the Author
