Shopify Canvas: What the 20-Minute Store Won't Do

Shopify says a merchant can now build a fully custom store in twenty minutes with Shopify Canvas. We believe it. The question is what's sitting in the store when the twenty minutes are up. Shopify's own help center answers part of that, and

Shopify says a merchant can now build a fully custom store in twenty minutes with Shopify Canvas. We believe it.

The question is what's sitting in the store when the twenty minutes are up. Shopify's own help center answers part of that, and the list is longer than the launch post lets on.

Canvas puts every page on one surface and lets Sidekick edit the code

Canvas is a new design view inside the Shopify admin. You see your pages laid out together, pan across them, zoom into a section, and either click to edit or ask Sidekick in chat. Shopify's launch post says it renders the real theme code, not a static mockup.

Sidekick now works directly on the theme's files and checks its own work against screenshots. Shopify says Sidekick made more than twenty-five million theme edits in the first half of 2026. Canvas is that same engine with a face on it.

It's rolling out "over the coming days" from October 1. The help center is more cautious and calls it early access for certain stores. Don't be surprised if your admin doesn't show it yet.

The twenty-minute claim is a first-draft claim

Twenty minutes to a custom store is a time-to-first-draft number. It measures how fast the design appears. It says nothing about whether the store is fast, converts, or survives your app stack.

Design was never the expensive part of a Shopify store. The expensive part is everything that has to be true after the design is done.

Shopify says as much about its own product.

Canvas is not replacing the existing editor yet. Things will change quickly, and there are gaps we still need to close.

— Shopify, Introducing Canvas, October 1, 2026

That is an unusually honest sentence for a launch post. So let's read the gaps.

Seven limits Shopify's own docs list, and what each one costs you

Everything below comes from Shopify's Canvas requirements page and its customizing page. We checked both on October 11.

What the docs say	What it means for your store
Third-party themes aren't supported	If you paid for a Theme Store theme from another developer, Canvas can't open it
You can't add or configure app blocks or app embeds	Reviews, subscriptions, bundles and upsells live there. Canvas can't place them
You can't customize a theme for different markets	Per-market layouts stay in the regular theme editor
You can't translate theme content in Canvas	A multilingual store still needs the regular workflow
A theme edited in Canvas doesn't receive theme updates	You own every future fix yourself
You can't download the theme files	No local copy, no developer handoff through files
Sidekick changes clear your undo history	One bad edit means asking Sidekick to fix it or restoring from theme history

Add two more: it's desktop only, and it needs a plan that includes theme customization.

The updates line is the one we'd read twice. A theme that stops receiving updates and can't be exported is a theme you've chosen to maintain by conversation with a chatbot. That's fine for a fashion drop that lives six weeks. It's a worse bet for the store that pays your rent.

A custom theme plus Canvas is the combination worth testing

Shopify says Canvas works with its own themes and with custom themes. A theme a developer built for your store reads as custom, which makes it the one place Canvas could pay off for a merchandiser.

The upside is real. Your team changes a banner or reorders a section by chatting with Sidekick instead of filing a ticket. We haven't run this on a client store yet, so treat it as a hypothesis, not a result.

The catch is the same updates line. Once someone edits that theme in Canvas, it stops receiving updates and can't be exported, so decide who owns the theme before the first edit, not after.

If you sell in more than one market, Canvas is a drafting tool for now

No per-market customization and no in-Canvas translation. For a store with two currencies and two languages, that rules Canvas out as the place where the final theme gets built.

You can still use it to explore layouts on a single-market copy. Then someone has to carry the result back into the real multi-market theme. That carrying is the work.

Our own clients sell across the US, DACH, and Australia, so this is the first thing we'd check. If you only sell in one currency and one language, this limit doesn't touch you.

Apps are where the store makes money, and Canvas can't place them yet

Shopify's developer community post from October 1 is blunt: Canvas doesn't support theme app extensions yet. If a merchant creates or duplicates a theme in Canvas, an app's blocks and embeds won't be available in that theme for now.

A Shopify reply in the same thread says support is planned "within the next few weeks." Treat that as a plan, not a date.

Think about what that means in practice. Your star-rating widget, your subscribe-and-save block, your free-shipping bar: all of it is an app block. A Canvas-built page can look finished and still be missing the pieces that convert.

Your app setup is also already moving this year. If you haven't looked at which apps still rely on the old injection method, our breakdown of the March 2027 script tag cutoff is the checklist.

Pretty pages still lose to heavy pages

Here's the first-party part. We inherited a store with eleven landing pages on a page builder and rebuilt them as Shopify Horizon theme sections. Mobile LCP went from 3.8 seconds to 1.4, and the store's Meta CPM fell 38% the week after cutover.

The design barely changed. What changed was how much code the browser had to run before showing anything.

We couldn't find performance figures for Canvas-built pages in Shopify's announcement or help center, and we haven't shipped a client store through Canvas yet. So we're not claiming it's slow. We're saying nobody has published the number, and your ad spend is going to find out before you do.

Our rule: design in Canvas if you like. Before you publish, run the page through PageSpeed Insights on mobile and compare it against the live theme. If the new page is slower, the pretty version costs you more than it saves.

Agent shoppers don't see your layout

There's a second audience now, and it ignores your design entirely. Meta's Muse and the other shopping agents read your catalog fields, reviews, and policies. They don't care how good the hero section looks on a 27-inch monitor.

We covered this in what Muse reads before it recommends your store. The short version: thin descriptions and missing policy fields get you skipped, and no Canvas edit fixes that.

Canvas makes your store look better to people. The data underneath decides whether agents send you any.

How we'd use Canvas this month

We're a vendor. We sell website builds, so weigh this accordingly. We'd still tell a single-market store with three apps to try Canvas and keep the money.

Here's the order we'd work in.

1. Duplicate the live theme. Never edit the published copy.
2. Use Canvas for what it's good at: layout exploration, section copy, and a fast first draft of a new landing page.
3. List your apps and mark every one that renders a block on the page. Those blocks have to be re-placed by hand in the regular editor.
4. If you sell in more than one market, finish the multi-market work in the standard theme editor, not Canvas.
5. Test mobile LCP and your add-to-cart path on the duplicate before you publish anything.
6. Keep the old theme in the library for at least a week.

If steps 3 and 4 come back with long lists, or you're spending real money on Meta and Google traffic, that's when a person earns their fee. Not to design it. To make it fast, make the apps work, and make it hold up across markets. If you want the fuller version of that decision, here's our honest breakdown of building it yourself versus hiring.

And if you'd rather skip the six-step list, that's the job we do.