Drupal Layout Builder vs Paragraphs — when to use which
Two common approaches to flexible page building in Drupal. Here is what sets them apart and when to use which.
Why this question comes up
Most Drupal projects need flexible page building at some point — editors need to add different blocks, sections, text and images without calling a developer every time.
The two most common solutions are Paragraphs (a contributed module) and Layout Builder (a Drupal core feature since 8.5). Both work, but in different ways.
Paragraphs — what it is
Paragraphs is a module that adds a list field to content types where different types of "paragraphs" can live — text block, image block, quote, video block, CTA, etc.
Editors build a page by adding paragraphs in sequence. Each paragraph is a separate entity with its own fields.
Strengths:
- Simple for editors to understand — the order is clear
- Good revision history
- Content is structured, not free HTML
- Works well for simple single-column pages
Weaknesses:
- Multi-column layout is complex (requires extra work)
- Nested paragraphs get complicated quickly
- Content is tightly coupled to presentation
Layout Builder — what it is
Layout Builder is a Drupal core feature that lets you define section layouts visually. Sections can be added, removed, and given different column counts. Any Drupal block can be placed into each section.
Strengths:
- Visual, drag-and-drop interface
- Native support for multi-column layouts
- Page-specific layout overrides
- Core feature — no extra module required
Weaknesses:
- More complex to develop and steeper learning curve
- Access control requires an extra module (
layout_builder_restrictions) - Revisions still maturing (improving in Drupal 10/11)
- Can be overwhelming for non-technical editors
When to choose Paragraphs
- Simple pages with a linear structure
- Editors who are not technically inclined
- Strong revision history is a requirement
- Multilingual site where translation workflow matters
When to choose Layout Builder
- Marketing pages, landing pages where design varies widely
- Client wants to control page layout without a developer
- Multi-column layout is a hard requirement
- New Drupal 10/11 project (Layout Builder is actively developed)
Third option: both together
On some projects a combination makes sense — Paragraphs for structured article content, Layout Builder for marketing pages. This requires a clear architecture, otherwise it gets confusing.
Practical recommendation
In most cases:
- Paragraphs — for the majority of information sites where content matters and editors are non-technical
- Layout Builder — for marketing-heavy sites where design flexibility is the priority
In both cases it is the developer's job to constrain the choices so editors cannot accidentally break the layout.
If you need advice on architecture for a specific project, get in touch.
Kaido Toomingas
WebPro Company OÜ
Need Drupal help?
If the article describes your situation, you do not have to read everything first. A real person will help you choose the next step.