Shopify Canvas: Themes, Apps & Hydrogen

Shopify Canvas turns an entire online store into a visual workspace. Merchants can move between pages, work with Sidekick, and inspect changes as they land. Sidekick edits theme files, validates code, and checks screenshots. Shopify says Canvas is rolling out, is still early, and does not replace the existing editor yet.[1]

That is a meaningful step for merchants and for people who build Shopify themes. It is not an announcement that every Shopify storefront now needs to be headless, or that Canvas edits Hydrogen applications. Those are different architectural decisions.

Canvas improves the theme workflow, not every storefront workflow

Canvas works with Shopify's theme architecture, where Liquid templates, sections, and settings define the storefront. Hydrogen is Shopify's separate path for teams building a custom storefront application. Shopify's Canvas announcement describes Sidekick changing theme files, not editing Hydrogen code.[1][2][3]

That distinction matters more than a feature checklist. If a native theme can deliver the design, integrations, and merchant workflow a store needs, the merchant should not have to take on a custom frontend just to get better editing. Hydrogen is worth the responsibility when the business needs an experience, integration, or application workflow the theme model cannot comfortably support. A custom storefront also means owning its code, deployment, and maintenance. For a closer look at that trade-off, read our Hydrogen theme vs. custom build guide.

Shopify is still investing in headless commerce. Its new Hydrogen developer preview is a separate, agent-oriented toolkit, while existing Hydrogen storefronts remain supported.[3] The fact that both paths are improving is good news; it does not make them interchangeable.

What happens to the Shopify theme market?

Our view: theme developers still have a market, but the work that stands out will change. Shopify says Sidekick uses each theme's design contract and curated patterns to guide its decisions.[1] A strong theme can become a coherent design system an agent extends, not just a collection of pages that merchants have to configure by hand.

Generic sections may become easier to reproduce. Distinctive design, commerce-specific behavior, accessibility, performance, and dependable support will be harder to replace. This is our forecast about where value may move, not a measured outcome of the Canvas launch. The Liquid developer preview is another signal worth watching, but it is a separate initiative from Canvas.

Theme studios do not need to choose between building for native Shopify and exploring Hydrogen. The right starting point remains the merchant's actual requirements. For a store that needs headless, a reusable Hydrogen theme and a thoughtful component system can make the custom route less costly to adopt.

What changes for Shopify app developers?

Theme app extensions provide Liquid app blocks and embeds inside compatible Shopify themes. They do not automatically render in a separate Hydrogen storefront.[7][3] Installing an app does not prove its storefront features support headless. Check each surface separately: admin workflows, checkout behavior, storefront UI, data APIs, and required customer events.

There is another, distinct opportunity inside native Shopify. Apps can expose data and actions to Sidekick through app extensions.[10] That is useful for merchants working in Shopify, but it is not a Canvas-to-Hydrogen compatibility bridge.

For storefront-facing apps, a documented API and a tested Hydrogen integration can open another route to merchants. The details matter: rendering a widget is not enough if the app also relies on Liquid, ScriptTags, storefront events, or behavior that only exists in the theme runtime. Headless compatibility needs an app-by-app check, not a universal badge.

Where Weaverse fits today

Weaverse Studio gives teams that choose Hydrogen a visual editing surface for developer-built components. Developers implement and register components and choose the properties editors can change; merchants can compose supported sections, edit content, and preview the result within those boundaries.[5][6]

Weaverse Studio interface showing page outline, live storefront preview, and component settings

Weaverse Studio today. Screenshot from the Studio interface guide, not the forthcoming Sandbox.

That does not turn configuring an existing section into building a new feature. New storefront logic, an unusual data flow, or an app integration still requires development. The value is that routine content and layout work can happen without reopening that development loop every time.

Two storefront paths: Shopify theme → Canvas and Sidekick as Canvas rolls out. Custom Hydrogen storefront → Weaverse Studio today; Weaverse Sandbox is in development. These are different runtimes, not feature-for-feature substitutes.

A practical starting point for theme and app builders

We have already built the SDK packages @weaverse/core, @weaverse/react, and @weaverse/hydrogen for turning developer-created components into editable Hydrogen experiences. Our component guide explains the implementation boundary, and our Shopify Hydrogen agent skills publish task-specific guidance for building, upgrading, and working with Weaverse components.[6][8][9]

Weaverse Agent Skills page showing installation choices and storefront development tasks

Our Agent Skills page in September 2026; the catalog may change. Use the published skills repository for the current material.

These SDKs and skills, along with our existing Hydrogen themes, are available now.[4][8][9] They are a starting point, not a claim that a theme or app will become headless-compatible without integration work.

We want to grow an ecosystem where theme creators bring reusable design systems and storefront components, and app developers bring headless-ready APIs and integrations. That is an invitation to help shape the market with us, not an announcement of a finished theme or app marketplace. We already work with agencies and technology providers through the Weaverse partner program.[11]

Where the Weaverse Sandbox is headed

We are working toward a browser-based Sandbox for Hydrogen projects: a place to build and preview a storefront with an AI collaborator, while keeping a real codebase and merchant editing in the loop. We want developers to build with AI, merchants to edit with AI, and eventually more of the store-building process to be accessible from the first idea onward.

For theme studios and app developers, the intended benefit is a shorter path from code and integration work to a preview a merchant can evaluate. Sandbox is a direction we are building toward, not a feature available today. We are not announcing a release date or promising that a prompt can produce a production-ready store.

The hard part is not getting AI to generate a page. It is making the result work with a brand's products, accessibility requirements, integrations, and maintenance process after launch. Those are the standards an AI-assisted Hydrogen workflow has to meet.

Which path should you take?

Your Shopify theme meets your needs: Stay with it and evaluate Canvas when it becomes available to your store.[1]
Your storefront needs a custom frontend: Compare the ongoing cost of Hydrogen with its flexibility. Try a Weaverse Hydrogen theme and evaluate the Studio editing workflow against your real use case.[4][5]
You build Shopify themes or apps: Explore our SDK component guide and agent skills. Test every app integration; Liquid app blocks are not portable by default.[6][9][7]

Canvas makes native theme building more approachable. Headless remains a choice for storefronts that actually need it. If you build themes or apps and want to help make that path more useful, talk to Weaverse about building together.[11]