Shopify Canvas: what it changes, and what still needs a developer
Shopify's Canvas lets a merchant ask Sidekick, Shopify's AI agent, to change a store's theme files while they watch the result. That moves some work away from developers. This article lists what Shopify documents about i
Shopify's Canvas lets a merchant ask Sidekick, Shopify's AI agent, to change a store's theme files while they watch the result. That moves some work away from developers. This article lists what Shopify documents about it, what the documentation leaves open, and which jobs I would still keep with a developer. The last part is my recommendation, labelled as such.
Sources read on 2026-11-06: Shopify's Introducing Canvas post (1 October 2026), the Canvas launch changelog (1 October 2026), and three Help Center pages: Canvas overview, requirements and limitations and customizing in Canvas. The Help Center pages carry no date. Everything here can change; Shopify's own post says "Things will change quickly, and there are gaps we still need to close."
What Shopify says Canvas is
- A design surface that shows every page of the store side by side, with the merchant able to click elements to edit them or describe changes to Sidekick in chat.
- Merchants edit "a render of the store's actual code", not a static preview. Sidekick "works directly on theme files", validates its code and checks screenshots of its work before handing it back. Scope ranges from a section change to a store-wide redesign.
- Status: rolling out. The overview page says it is "in early access and is available only to certain stores", on desktop only. The launch post says "Canvas is not replacing the existing editor yet."
Eligibility and documented limits
| Area | What the Help Center says |
|---|---|
| Themes | Works only with themes developed by Shopify and custom themes. Third-party themes are not supported. |
| Staff access | Requires the "Online store > Themes > Edit code" permission. |
| Theme updates | A theme edited in Canvas does not receive theme updates. |
| Files | Theme files of a Canvas-edited theme cannot be downloaded. The theme opens only in Canvas, not the theme editor. |
| Duplicates | Changes to a duplicated theme do not carry over to the original, and vice versa. |
| Apps | App blocks and app embeds cannot be added or configured in Canvas. A duplicated theme keeps the original's app settings, which cannot be changed or removed there. |
| Translation | Not translatable in Canvas; the page points to the Translate & Adapt app. |
| Markets | Cannot customize a theme for different markets. |
| Rollouts | A Canvas-edited theme can replace the main theme in a rollout, but a rollout cannot be used to edit it. |
| Blocks | A new block cannot be added to a template manually; you ask Sidekick. |
Controls Shopify documents for changes
- Version history: open from the theme name in the top bar. Restoring a version "replaces your current version in Canvas", and customers see it only after you publish.
- Undo: works only for manual setting changes. "When Sidekick makes a change, your undo history is cleared." To reverse a Sidekick change, ask Sidekick to change it back or restore an earlier version.
- Publishing: the dialog shows changes made since the last publish. If the theme cannot be published, it lists errors and offers Fix with Sidekick.
- Preview: unpublished changes appear in Canvas and in the theme preview. The page I read describes no way to share a preview link.
What the pages do not say
None of these is addressed in the pages I read, so I am not claiming either way:
- Whether Sidekick's validation includes accessibility or performance checks. Shopify says it validates its code and reviews screenshots.
- Whether changes are tracked in Git or any external version control. The documented inability to download theme files of a Canvas-edited theme means a team cannot pull it into a repository (that second part is my inference from the limits above).
- Any support for rolling back to a non-Canvas version of the theme.
- How Sidekick treats custom Liquid, metafield definitions or integrations a developer added earlier.
Where a developer still fits (my recommendation)
This is judgement, based on the limits above, not a Shopify statement.
| Job | Why it stays with a developer |
|---|---|
| Anything that touches apps (blocks, embeds, tracking) | Canvas cannot add or configure them. |
| Multi-market, translation, and rollout work | Documented as unsupported in Canvas. |
| Reviewing the diff before Publish | The publish dialog lists changes; someone who reads Liquid, CSS and JS should read them. |
| Accessibility and performance regression checks | Not described as part of Sidekick's validation. |
| Keeping a rollback path | Version history is the documented mechanism; a client with a Git workflow loses it for a Canvas-edited theme. |
| Third-party themes | Not supported, so theme-store themes keep the normal workflow. |
| Update strategy | A Canvas-edited theme stops receiving theme updates; someone has to own that decision. |
A review routine for a Canvas change
- Work on a duplicate of the live theme. Shopify documents that duplicate and original do not sync, so the copy is a safe place to try changes.
- Before publishing, open the dialog and read the list of changes since the last publish.
- Run the same checks you run for any theme release: keyboard navigation, mobile layout, checkout flow, tracking events, a performance check.
- Record the version-history entry you would restore to if something fails.
- Publish at a quiet time, then check the live store in a separate tab (Shopify's page suggests opening the online store in a new tab to see what customers see).
For background on theme choices and keeping Dawn-style themes fast, see how I choose a Shopify theme and speeding up Dawn: Liquid performance and app bloat on the Prateeksha blog.
Disclosure: the two prateeksha.com links above are to articles on my agency's blog.
If a client asked you to keep Git history for a theme that is edited in Canvas, what would your workaround be?
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.