Shopify Introduces Canvas

Published 2 October 2026

On 1 October 2026, Shopify announced Canvas: a design surface where you see every template in your store laid out at once, and build by talking to Sidekick.

Plenty of this week’s coverage lists Canvas’s limitations. What is missing is anyone explaining what those limitations actually mean once you own the store: which trade-off you are making when you let an agent edit your theme, why Shopify drew the boundaries where it did, and how to decide whether Canvas belongs in your workflow.

The demo looks impressive but also highlights many constraints, although it is very early days.

What Canvas actually is

Shopify describes Canvas as a design surface, not a new theme editor. In practical terms it is four things at once:

• A single visual workspace showing all of your store’s templates side by side, which you can pan across and zoom into
• A live render of your actual theme code — not a static preview — with full interactivity and animation, across different products, collections and screen sizes
• A chat with Sidekick, Shopify’s AI agent, which makes changes that appear on the canvas as it works
• A conventional editor for blocks, settings and text, for the changes you would rather make yourself

Shopify says Sidekick works directly on theme files, validates its code, and reviews screenshots to see how its changes rendered before iterating and handing the result back. That is an agentic loop over your theme’s source code.

Shopify is also explicit that this is early. Ben Sehl, Director of Product at Shopify, says Canvas is not replacing the existing editor yet.

How Canvas is laid out

Canvas opens from the Themes page in the Shopify admin. There are three ways in:

• New — create a new theme in Canvas, including from a description of your brand
• Duplicate in Canvas — take a copy of a supported theme and experiment on the copy
• Edit theme — on any theme already displaying the Canvas badge

The top bar

The top bar holds the exit icon, the theme name (hover it to see whether you are in the Live theme or a Draft theme), a theme settings icon for theme-wide colours and typography, a Jump to… field for navigating straight to a template, undo and redo, a theme history icon for reviewing and restoring earlier versions, and the publish button.

That button is labelled Publish on an unpublished theme and Update on your live one. There is no save button at all — Shopify’s wording is that your changes are saved automatically in Canvas. Nothing reaches customers until you publish.

The overview

Templates open zoomed out, in a grid. You navigate by scrolling and zooming with a mouse or trackpad, or with the pan mode icon — or by holding the spacebar and dragging. Click a template to edit it, use the maximize icon for full screen, and zoom to overview to come back out.

Template headers show the URL path, and for product and collection templates they let you change which product or collection is being rendered. That is more useful than it sounds: it means you can check a template against a real edge case rather than whichever product happens to be first.

Full-screen view

Full screen adds two controls. The inspector toggle switches between editing and browsing — on, you select and edit blocks; off, you move through the template the way a customer would. The preview width icon offers Desktop, Tablet, Mobile and Full width presets, and drag handles for any width in between.

The Sidekick field

A Work with Sidekick field sits at the bottom, and it is context-sensitive. With nothing selected, it takes theme-wide requests. With a block selected, it takes requests scoped to that block. You can also run multiple chats simultaneously.

Worth pausing on that scoping. Selecting a block before you prompt is the difference between a change that lands where you meant it and a change that quietly rewrites your homepage.

The importance of the ‘design contract’

As Austin Knight, Design Director at Shopify, says: “Every theme has a unique design contract, a curated set of patterns to draw from, and a mountain of opinionated eval data.”

The reason Sidekick produces something that looks designed, rather than a wall of unstyled markup, is not raw model capability — it is constraint. Each theme supplies a defined set of patterns the agent may draw from, and Shopify has built evaluation data to judge whether the output is any good. Shopify also says it simplified theme architecture specifically so that structure, logic and design are more comprehensible to the AI.

In consequence: Canvas output quality is a property of the theme, not of Canvas. A theme with a tight design contract and thorough eval coverage will produce good results. A theme without one has nothing holding the model in shape.

Who can use Canvas today

Canvas is not yet available externally to merchants or partners, but it is meant to be rolling out over the coming days.

From Shopify’s documentation:

• Canvas is available only on desktop devices
• Canvas is available on plans that include theme customisation. Change to a plan that doesn’t, and you can still view a Canvas-edited theme — but you can’t edit or publish it
• Canvas works only with themes developed by Shopify and with custom themes. Third-party themes aren’t supported
• Staff need the Online store > Themes > Edit code permission
• Canvas is in early access and available only to certain stores

If you bought a theme from the Theme Store, Canvas won’t change it (for now)

“Themes developed by Shopify” means Shopify’s own first-party themes — Horizon, Dawn and the rest. “Custom themes” means a bespoke theme built for your store. Everything else is a third-party theme, and third-party themes aren’t supported.

Be clear about the size of that exclusion, because it covers most of the market: every paid theme in the Shopify Theme Store built by an independent theme developer. If you are running one, Canvas is not an upgrade path for your current theme. It is something to consider when planning a change.

The constraints that actually decide this

These are the limitations Shopify documents, and what each one means once you are running a real store.

A theme edited in Canvas does not receive theme updates

Shopify’s wording: “A theme that you edit in Canvas doesn’t receive theme updates.”

This is the same trade-off that has always come with editing theme code, now reached through a chat box. From Sidekick’s first change, your theme is a fork. Future improvements to the original — performance work, new sections, accessibility fixes, bug fixes — stop arriving.

What differs from hand-written customisation is volume and visibility. A developer customising a theme leaves a record of what they changed and why. An agent making forty changes across an afternoon’s conversation does not, and you have permanently opted out of upstream fixes in exchange.

You can’t download the theme files

Shopify’s wording: “You can’t download the theme files for a theme that you edited in Canvas.”

To a merchant this reads as a minor inconvenience. For anyone treating the store as a long-term asset, it is the most serious constraint in the documentation. No download means:

• You cannot put the theme in a code repository — no history outside Shopify, no diffs, no branches, no record of what changed between two points in time
• You cannot hand the files to a developer to work on locally
• You cannot export the theme to move it to another store
• Your entire change history lives in exactly one place: Canvas’s own theme history panel

We have written before about why your Shopify store needs a code repository. The short version is that when something breaks, the only question that matters is “what changed?”, and a repository is what answers it. A Canvas-edited theme cannot be put in one. Canvas’s version history is a real safety net and you should use it deliberately — but it is Shopify’s safety net, in Shopify’s system, under Shopify’s retention rules.

Sidekick clears your undo history

Shopify’s wording: “When Sidekick makes a change, your undo history is cleared.”

Undo covers changes you made by hand. The moment Sidekick acts, that stack is gone. To reverse a Sidekick change you either ask it to revert, or you restore an earlier version from theme history.

Combine that with automatic saving and there is no moment where you deliberately commit a known-good state. Version history is not a nice-to-have in Canvas — it is the only reliable way back, and you have to create checkpoints by intention rather than by habit.

No app blocks, no app embeds

Shopify’s wording: “You can’t add or configure app blocks or app embeds in Canvas.”

App blocks are how most stores get reviews, subscriptions, size guides, loyalty widgets, upsells and bundles onto a product page without custom code. In Canvas you can neither add nor configure any of them.

So for any store with apps installed, the workflow is split across two tools: Canvas for design and layout, the existing theme editor for the app layer. Better to know that before you plan an afternoon in Canvas and discover your reviews widget can’t be placed.

You can’t add a block by hand

Shopify’s wording: “You can’t add a new block to a template manually in Canvas.” To add one, you describe the content and appearance you want and ask Sidekick.

Manual editing in Canvas covers block settings, text and theme settings. Structure is Sidekick’s job. That division is deliberate, and it is the clearest signal of what Canvas is: not a faster theme editor, but a different interface in which the AI owns composition and you own refinement.

Translation and markets are out of scope

Shopify’s wording: “You can’t translate theme content directly in Canvas” — translations go through the Translate & Adapt app, under the Default theme content resource. And: “You can’t customize a theme for different markets in Canvas.”

On rollouts, the documentation is precise. You can add a Canvas-edited theme to a rollout as a replacement, but you can’t use a rollout to edit a theme you edited in Canvas, and you can’t open the theme from the rollout.

If you run multiple markets with market-specific theme customisation, Canvas does not currently serve that. This is the constraint most likely to rule Canvas out for larger international merchants — and also the kind of gap that tends to get closed. It is a gap today.

Metaobject templates are missing from navigation

Shopify’s wording: “Metaobject templates aren’t listed in Jump to… in Canvas.”

Small, but telling. Metaobjects are how structured custom content is modelled on Shopify now. If your store uses metaobject templates, part of your storefront is harder to reach from Canvas’s navigation.

Why the ‘Edit code’ permission is the tell

One requirement deserves special attention. To use Canvas, a staff member needs Online store > Themes > Edit code.

Consider what that means. Canvas is presented as the tool that lets people build a custom store without coding — and it is gated behind the permission that controls writing code.

Sidekick edits theme files, so Shopify’s own permission model treats a Canvas session as what it is: a code change. The no-updates and no-download constraints follow from exactly the same fact.

It also has a staffing consequence. If you have been careful about who holds Edit code on your store, that is the same list of people who can use Canvas. Granting a marketing hire Canvas access means granting them the power to change theme code.

So when is Canvas the right choice?

Taken together, Canvas is a strong fit and a poor fit in fairly predictable ways.

Canvas could be a good fit when

• You are starting a new store from scratch on a Shopify-developed theme
• Design distinctiveness matters more to you than long-term maintainability
• Your store is single-market and single-language
• Your storefront does not lean heavily on app blocks
• You want to explore design directions fast — Duplicate in Canvas is genuinely excellent for this: experiment on a copy, leave the original untouched
• You would otherwise have shipped a lightly configured Horizon or Dawn

Canvas is the wrong tool when

• You run a paid third-party theme — it is simply unavailable
• You rely on theme updates arriving
• Your theme is, or should be, in a code repository
• You sell into multiple markets with market-specific customisation
• Your product pages are assembled from app blocks
• The store is a business-critical asset with more than one person working on it

How to try Canvas without regretting it

If you have access and want to use it, a short discipline list:

1. Duplicate first, always. Use Duplicate in Canvas rather than editing your live theme. Shopify is explicit that the two themes are then separate: changes you make to one aren’t added to the other. That separation is the point — and also why you shouldn’t expect to merge your experiment back.
2. Download a copy of your current theme before you start. Once a theme has been through Canvas, you can’t download it. Take the files from the original while you still can.
3. Treat theme history as your commit log. Check it before any ambitious prompt and know which version you would restore to. Sidekick clears undo.
4. Scope prompts by selecting a block. Theme-wide requests get theme-wide results.
5. Check templates against real edge cases. Use the product and collection controls in the template headers — a sold-out product, a product with one image, a collection with four items.
6. Check every width. The presets are there, and the drag handles exist for the widths between them.
7. Plan the app layer for the theme editor. Don’t discover it halfway through.
8. Decide about updates deliberately. Before you publish, be clear that you are choosing a fork over a maintained theme. That is a reasonable choice for some stores and a bad one for others — the mistake is making it by accident.