Shopify previews Liquid blocks and partials for theme pages

Shopify has opened a Liquid July '26 developer preview that changes how theme teams can structure storefront pages. The preview adds native {% block %} and {% partial %} tags, so page composition and refreshable server-rendered regions can live directly inside Liquid templates instead of being split across JSON templates, section schemas, and custom JavaScript.

This is not a forced migration. Shopify says existing sections, theme settings, and JSON templates keep working, and the new Liquid-first model runs alongside the current theme architecture. The practical signal is narrower and useful: theme developers can start testing a composition model that is easier for humans and coding agents to read in one place.

Liquid gets page composition inside the template

The new {% block %} tag renders a reusable theme block from a Liquid template. Developers name the block, pass inputs, and provide body content in a pattern Shopify compares to {% render %}. That makes the structure of a page visible where the page is authored, instead of pushing core layout decisions into a separate JSON layer.

Shopify's current Liquid template documentation still describes the old limitation clearly: Liquid templates could control page layout, but they could not use sections; JSON templates were required for section-based composition. The July preview does not delete that model. It adds another path for teams that want a more direct Liquid file as the source of truth.

Partials target refreshable storefront regions

The {% partial %} tag is the more workflow-changing piece. Shopify describes it as a named region of server-rendered HTML that JavaScript can refresh without a full page reload. For storefront teams, that targets a familiar gap: dynamic product, cart, filter, or merchandising regions often pushed developers toward custom fetch-and-swap code or heavier client-side rendering.

The preview's promise is not that partial refresh suddenly becomes possible. It is that Shopify is defining a native Liquid contract for the region being refreshed. That matters for maintainability, especially on stores where theme files, app embeds, and JavaScript have accumulated over multiple agency handoffs.

Theme Check adds guardrails for Liquid-first work

Shopify says the preview also expands Theme Check coverage for Liquid-first themes. The rules cover syntax errors, excessive complexity, oversized files, invalid schema structure, and mismatches between block arguments, schemas, and {% doc %} declarations.

That guardrail matters because putting more structure inside Liquid templates can make a file easier to reason about, but also easier to overload. Theme teams should treat the preview as a chance to test file organization, naming, and review practices, not as permission to turn every page into one giant template.

The preview status is the main caveat

The release is explicitly a developer preview. Shopify has not published a general availability date in the changelog, and production stores should avoid hard dependencies on preview-only behavior unless the risk is acceptable. The safer move is to create a development store with the Liquid July '26 preview enabled, test against the skeleton theme release candidate, and compare the new tags with the existing JSON-template architecture.

For agencies and Shopify app builders, the larger platform direction is clear. Shopify is making its native storefront stack friendlier to coding agents and component-style editing without requiring a full headless build. That does not replace Hydrogen or custom React storefronts, but it weakens the argument that headless is required just to get clearer composition and partial page updates.

Sources and status

The primary source is Shopify's July 21, 2026 developer changelog entry for the Liquid block and partial tag preview. Shopify's Liquid template documentation provides the baseline for how Liquid templates previously related to sections and JSON templates. Digital Applied's independent writeup corroborates the release timing and frames the preview alongside Shopify's same-day developer-platform updates.

The open question is stabilization: Shopify has opened the path, but teams should wait for a stable API or GA signal before treating Liquid-first blocks and partials as a production architecture standard.