Shopify Canvas: what it does, where it stops, and what it means for developers

On October 1, 2026, Shopify introduced Canvas: a new workspace in the admin where a merchant sees every page of the store side by side and tells Sidekick, Shopify's AI agent, what to change. Sidekick then edits the theme's files itself. In the announcement, a director of product at Shopify says an entrepreneur can now build a fully custom store in twenty minutes.

If you build Shopify themes for a living, or you are learning to, that lands on a job you know well: set up a theme, adjust the sections, hand it over. This post covers what Canvas does, where it stops today according to Shopify's own pages, and what I think it does to the work developers get paid for.

What Canvas does

Canvas shows all of a store's templates in one zoomed-out view. The merchant can click into any of them and work in three ways: change a block's settings, edit text right in the preview, or describe a change to Sidekick. The Help Center puts it plainly: you can ask Sidekick for a change that is not available in a block's settings. That used to be the point where a merchant called a developer.

According to the announcement, Sidekick now works directly on the theme's files. It validates its own code, takes screenshots to see how the change landed, and repeats that loop before handing the result back. Shopify describes the range as anything from a small section change to a redesign of the whole store.

A merchant can start from nothing: click New, describe the brand, and Sidekick builds a theme and opens it in Canvas. Or they can duplicate a supported theme into Canvas and experiment on the copy while the original stays in the theme editor. Changes save automatically, there is a version history to restore from, and when a theme cannot be published the dialog lists the errors with a button to have Sidekick fix them. All of this is in Shopify's guide to creating and customizing themes in Canvas.

This is not Sidekick's first time in theme code. The same announcement says Sidekick made more than twenty-five million edits to themes in the first half of 2026. Canvas gives that a proper home and a much bigger scope.

Where it stops, as of October 5, 2026

Canvas is four days old as I write this, and Shopify says in the announcement that things will change quickly. So read this table as a snapshot. Everything in it comes from Shopify's requirements and considerations page or from Shopify staff on the developer forum.

The app gap is the one that matters most to merchants right now, and Shopify is clear that it is temporary. In the thread for app developers, Shopify says it expects to support theme app extensions before Canvas becomes the default editor, and that developers should not need to update their apps when that happens. Until then, the answer staff gave for stores that depend on apps is to keep using the theme editor.

What Shopify has not said

One thing is missing from all of these pages: what the code looks like. The announcement says theme architecture has been "simplified" so that Sidekick can understand and change a store more easily. It gives no detail. A developer asked in the forum thread whether Canvas themes are still the Liquid themes we know, with JSON templates, sections and blocks, or something built differently. As of October 5 that question has no answer from Shopify.

Shopify has also not described how a developer works on a Canvas theme outside Canvas. I am not going to guess at either one here.

Where Shopify says this is going

Canvas is not replacing the existing editor yet. That "yet" is Shopify's own word, and both forum threads talk about the moment Canvas becomes the default editor as something that is coming. So the theme editor is the present and Canvas is the plan.

For theme makers, the thread for theme partners says the Theme Store remains an important destination today, that Shopify is rethinking the role of the Theme Store, and that it expects themes to be a starting point for what merchants then build themselves. The replies from developers are mostly angry. In the app thread the two main complaints are that app blocks are missing at launch and that partners got very little notice.

The work that shrinks

From here on this is my read, not Shopify's.

The job that Canvas goes after is the first one most of us got paid for: install a theme, set the colours and fonts, arrange the sections, build the one custom section the theme does not have. Shopify's announcement says a bespoke store used to mean writing code or paying someone who could. We are the someone.

Canvas does not do all of that for every store today. The table above is long. But Shopify has said which way it is going, and the first of those limits is due to go within weeks. If theme setup is most of what you sell, I would plan for merchants paying less for it.

The work that appears

Now look at what a merchant has after an afternoon in Canvas: a store that looks the way they wanted, running on code nobody on their team has read. That store still needs things, and the request a developer gets changes from "build me a store" to "I built this with Sidekick, and now I need something more".

• The code is theirs now. A theme edited in Canvas stops getting theme updates, and Sidekick writes custom code into it. That is the position every store with a custom theme has always been in: nobody upstream maintains it. Whoever works on it next has to read code they did not write.
• A lot of a store is not in the theme. Canvas works on theme files. A discount that has to hold at checkout, a rule about who may buy what, product data that needs its own structure, a connection to a warehouse or an ERP: none of that lives in theme files. That is Functions, metafields and metaobjects, apps and APIs.
• Apps, markets and languages. Today those run through the theme editor or the Translate & Adapt app. Knowing which route fits a store, and what it costs to switch later, is advice merchants pay for.
• Judging the result. The merchant sees a page that looks right. Whether the code behind it handles a sold-out variant, a product without an image or a second currency is a different question, and it takes someone who can read Liquid to answer it.

Taking over a store that an AI built, extending it and fixing it: I expect that to become an ordinary kind of Shopify job. It asks for more than theme setup did, and it is harder to replace.

What to learn now

Liquid and theme architecture still matter, but the reason changed. You learn to write them so that you can read them. You cannot review code you could not have written yourself, which is the argument I made in do you still need to learn Shopify development in the AI era, and Canvas makes it more concrete.

After that, spend your time on the parts of a store that are not theme files: the object model, metafields and metaobjects, Functions, app extensions. And practise reviewing early. Reading a piece of generated code and saying exactly what is wrong with it is a skill you build by doing it, not by reading about it.

What to do this week

1. Use it. If one of your stores has Canvas, duplicate a theme into it and build something. The original theme stays untouched. An hour inside it tells you more than any article, this one included.
2. Read the requirements page. It is short, and it is the page that will change as the limits move. Requirements and considerations for using Canvas.
3. If you sell theme setup, split your services in two. One list of what Canvas does today, one list of what it does not. Lead with the second list when you talk to clients.
4. If you build apps with theme app extensions, you have nothing to change today. Shopify says your app keeps working in the theme editor and on existing themes, and that it does not expect you to update the app when Canvas support arrives.