Drupal
Drupal Canvas vs Layout Builder in 2026
Drupal Canvas is Drupal's official visual page builder, and in 2026 I treat it as a new surface next to Layout Builder and Paragraphs, not as a button that converts the old pages. I am Alan Vo, a Gold Coast web developer with 18 years on CMS and storefront work. Canvas 1.0 shipped at the end of 2025. Drupal CMS 2.x made Canvas the default editing experience for new marketing sites. Existing Layout Builder sites still run the web. There is no official one-click migration path I will bet a museum homepage on.
This note is for teams on Drupal 10 or 11 who have Layout Builder (or Paragraphs) in production and are being asked to "just switch to Canvas". Pair it with Drupal CMS recipes for how structure gets installed, and with migrating classic Drupal sites to Drupal CMS for the wider product move. The project page for Drupal Canvas is the source of truth for releases and issue status.
What Drupal Canvas changed in 2026
Drupal Canvas changed the editor from "sections and blocks in an admin layout UI" to "components on the page with live preview". Layout Builder, in core, still thinks in section grids and placeable blocks. Paragraphs still think in stacked fieldable entities. Canvas thinks in components and props: Single Directory Components (SDC), nested components, and in Drupal CMS a Mercury-style library of heroes, cards, and accordions.
That is a real upgrade for campaign pages. It is also a new content model. Canvas pages are not "Layout Builder with a nicer theme". They have been built around a page entity and a component tree. Editors who learned "add section, add block, save layout" are not automatically Canvas editors. Developers who encoded spacing in Layout Builder section settings will not find a 1:1 mapping.
I use Canvas on greenfield Drupal CMS marketing builds when the brief is visual landing pages and the theme is component-based. I keep Layout Builder on sites where every project page must share a strict template, or where legal review depends on a locked view mode. Hybrid is the production pattern until migration tooling exists: Canvas for a landing_page type, Layout Builder or view modes for project, exhibition, provider.
AI helpers that generate a Canvas page from a prompt are a Drupal CMS product feature. I treat them as a first draft generator, not as IA. A listed real-estate site and an outdoor brand site still need components that match brand CSS, not a random testimonial row the model invented.
How Drupal Canvas actually works next to Layout Builder
Drupal Canvas actually works as a component engine with an on-page editor. You expose SDCs (and code components) that declare props. Editors drag those components, nest them, and save. The front end renders the tree. Layout Builder still stores section and component (block) configuration on an entity view display or per-entity override. Both can live on one Drupal, on different bundles.
Practical split I recommend:
- Layout Builder: content types with a stable skeleton (header region of the node, two columns of fields, a related block). Editors may rearrange within rules. Good for project listings, bios, product families that must look like a system.
- Paragraphs: linear, structured slices (quote, spec table, download) where the value is the data, not free-form art direction.
- Drupal Canvas: home, campaign, and landing URLs where marketing needs to compose without a ticket.
Drupal CMS pairs recipes (structure) with Canvas (presentation). A recipe can create a content type. Canvas is how a non-developer lays out an instance. On a classic theme without SDCs, Canvas has nothing honest to drag. You cannot drop Canvas onto a 2019 custom theme and expect Mercury components to appear. You either adopt a component theme or you stay on Layout Builder.
No official Layout Builder-to-Canvas migrator as of the work I am doing in 2026 means I do not quote a date. Community tools may appear. Until they are boring, I copy content by hand for a handful of URLs or I leave LB pages in place. Rewriting 400 project nodes as Canvas trees is a content project with a QA budget, not a module enable.
Nested components are powerful and easy to make inaccessible. A hero inside a card inside an accordion is a keyboard trap waiting to happen. I constrain the library: which components may nest, max depth, and which are page-level only.
Drupal Canvas vs Layout Builder vs Paragraphs on real sites
Drupal Canvas vs Layout Builder is not a purity contest. Immobel-style corporate project libraries need repeatable project templates more than they need a free-form canvas on every node. IASO-style product storytelling often wants a few campaign landers and a lot of structured product fields. I would rather ship Canvas on five URLs than break 200 Layout Builder overrides.
Paragraphs still win when the slice is data: a spec row, a downloadable PDF with a title and a file field, a quote with a required source. Putting that in Canvas as untyped text is how you lose listings and translations. Keep the entity. Optionally display it inside a Canvas slot if the product supports that later. Do not delete the field because the homepage is now Canvas.
Performance differs. Layout Builder can already get expensive with many sections per node and many blocks. Canvas adds a richer editor (React in admin) and a component runtime on the front. I measure the published HTML, not the editor. A marketing page with video backgrounds will be slow in any builder. The builder is not an excuse to skip image dimensions.
Permissions differ. Layout Builder has layout permissions and block placement permissions you may already have audited. Canvas needs a new permission story: who may create Canvas pages, who may add raw HTML components, who may publish. I do not give "full Canvas" to every authenticated role on a government site.
Production checklist for hybrid Canvas adoption
- Inventory bundles that use Layout Builder overrides vs default layouts vs Paragraphs.
- Pick one bundle for a Canvas pilot (usually a new
campaignorlandingtype), not the node type with 5,000 records. - Confirm the front theme can expose SDCs. If not, Canvas is a later phase after a component refactor.
- Build a small component library: hero, rich text, image, cards, CTA, FAQ. Stop there for v1.
- Write nesting rules. Test keyboard and headings in the worst nested page an editor can make.
- Keep Layout Builder templates on the structured types. Do not dual-enable both UIs on the same view mode without a written rule.
- Train editors on Canvas with the pilot type only. Do not train on production homepage first.
- Set up preview and workflow (draft, published) the same as the rest of the site. Visual builders love to skip moderation.
- Check multilingual: component strings and images need translation paths. A Canvas tree that only exists in English will duplicate the old locale trap.
- Measure TTFB and LCP on a Canvas URL vs an LB URL with similar media.
- Document rollback: how to unpublish a Canvas page and what still serves.
- Watch the Canvas issue queue before a major Drupal core jump. Visual builders move fast and break config.
I never enable Canvas "everywhere" because a demo looked good. Everywhere is how you get three layout systems and no owner.
What breaks in a Canvas plus Layout Builder hybrid
A hybrid breaks when editors cannot tell which UI a URL uses, when the homepage is Canvas and the inner pages are LB with different spacing, and when SEO modules read the wrong entity fields.
Failure modes:
- Metatag and canonicals on Canvas page entities not configured, while nodes are fine. Title in the tab says the site name only.
- Two H1s: Canvas hero plus the node title block you forgot to hide.
- Path aliases that still point at Layout Builder nodes you unpublished but did not redirect.
- Search API indexes node body and misses Canvas component text, so campaign pages are invisible in site search.
- CSS from Mercury or a starter colliding with the old theme when you try to run both.
- "No migration path" used as an excuse to freeze forever, or as an excuse to delete Layout Builder before the new pages exist. Both are wrong. Freeze the old, add the new, move URLs when they are ready.
I also see accessibility regressions: components without labels, carousels in the library that cannot be paused, colour contrast that passed in Figma and failed in a nested card.
How to measure Drupal Canvas adoption
Measure Drupal Canvas adoption with editor time-to-publish on the pilot type, with field Core Web Vitals on those URLs, and with a content audit: how many live URLs are still Layout Builder, Paragraphs, or Canvas. If everything is still LB after six months except one demo page, you did not adopt Canvas. You installed it.
I also check:
- Whether campaign pages appear in the XML sitemap and in Search Console.
- Whether translations exist for Canvas URLs you claimed were multilingual.
- Whether the component library grew past what you can QA. Thirty components with no tests is a new Paragraphs problem.
Do not invent a conversion rate for a corporate Drupal rebuild. These sites are not always shops. The metric is publish speed without breaking the system.
Related work on this site
Corporate Drupal is where layout discipline shows. The Immobel Group site is Drupal for a listed European real estate developer: projects and corporate content that must look like a system, not like fifty unrelated landing pages. The IASO site is Drupal for outdoor products and corporate storytelling. Both were contract development on an agency team. That is hybrid territory: structured project or product templates stay strict, and Canvas (when the theme is ready) is for the campaign URLs that used to generate a Layout Builder ticket every time marketing wanted a new hero.
FAQ
Is Drupal Canvas replacing Layout Builder in core?
Drupal Canvas is the direction Drupal CMS is taking for visual pages. Layout Builder remains in core and remains what thousands of sites store layouts in. I do not uninstall Layout Builder because Canvas 1.0 exists. I add Canvas where the theme and the brief support it.
Can I migrate Layout Builder pages into Drupal Canvas today?
You cannot rely on an official Layout Builder-to-Drupal Canvas migrator today. Some teams rebuild high-value URLs by hand. Some wait. I do not bulk-destroy LB overrides on a promise. Track the Canvas project and core initiatives, then budget a content move.
Does Drupal Canvas work without Drupal CMS?
Drupal Canvas can be used with standard Drupal if you add the module and a component-capable theme. Drupal CMS is where it is pre-wired. A classic custom theme with no SDCs is the wrong host.
Should I put every page on Drupal Canvas?
You should not put every page on Drupal Canvas. Structured types with fields, listings, and translations stay on templates, Layout Builder, or Paragraphs. Canvas earns its keep on pages where composition is the product. Mixing three systems on one bundle is how editors hide.
Keep reading
Contact if you want this kind of work on a live store.