Drupal Blocks vs Content Blocks: Stop Paragraph Duplicates

If a block shows up twice on your page, Drupal is not misbehaving — you have given it two valid render instructions, one from a theme region and one from your Paragraph, and it is obeying both.

This is the single most common "bug report" I get about component-based Drupal builds, and it is never a bug. It comes from two separate block systems that look identical in the admin UI and behave completely differently once a component layer sits on top of them. Once you can name which system you are looking at, the fix takes about five minutes.

Drupal has two block systems, not one

Both are core. Both are supported by component modules. They are not interchangeable.

That admin path matters. If a tutorial tells you to go to Structure > Block layout > Custom block library, it predates Drupal 10.1. In Drupal 11.4 the listing lives under Content, at /admin/content/block, and the entity is called a content block, not a custom block.

Why the duplication happens

A theme region and a component are two different placement systems, and neither one knows the other exists.

When you place a plugin block in the Header region, Drupal renders it in the Header on every page. When you then embed the same block inside a Paragraph, Drupal renders it there too. Two instructions, two outputs. Nothing suppresses the first because nothing was ever asked to.

Paragraphs does not override region-based rendering, and it should not. A component module that silently unplaced your blocks would be a far worse bug than the one you are looking at.

The exact sequence that triggers it

1. You enable a block and assign it to a visible region so it appears in the block plugin list.
2. You add that same block inside a Paragraph.
3. The page renders it twice — once from the region, once from the component.
4. You clear cache repeatedly. Nothing changes, because caching was never involved.

That last step is the expensive one. The behaviour is structural, not a stale render array, so every cache rebuild returns the same duplicated markup and reinforces the wrong theory.

The fix: a hidden region

The pattern is simple — keep the block enabled so the plugin manager loads it, but place it somewhere that never renders.

Here is the part most write-ups get wrong: this is not something every theme gives you. Olivero, Drupal 11's default front-end theme, defines thirteen regions in olivero.info.yml and none of them is a hidden region. If you are on Olivero or a stock sub-theme, you have to add one before this fix is available to you.

The Solo theme, which I maintain, does ship one — the last entry in its regions: block is hidden: 'Hidden Region'. If your theme has no equivalent, add one:

# YOUR_THEME.info.yml
regions:
  header: 'Header'
  content: 'Content'
  footer: 'Footer'
  hidden: 'Hidden Region'

Then never output {{ page.hidden }} in page.html.twig. A region that is declared but never printed is exactly what you want: real to the block system, invisible to the browser.

The three-step workflow

1. Enable the block. Go to Structure > Block layout and place it. A plugin block that is not placed is not available to embed.
2. Assign it to the hidden region, not Header, Sidebar or Content.
3. Place it in your component where you actually want it.

One instruction, one output. This works identically for content block entities: if a block should only ever appear inside a component, it must not also sit in a visible region.

Which bundles are affected

I maintain the Paragraphs Bundles module, so the naming below is read straight from the source rather than remembered. Version 2 declares core_version_requirement: ^11.3 || ^12 and depends on paragraphs, entity_reference_revisions and field_group alongside several core modules.

• block_bundle, from the paragraph_bundle_block submodule — embeds a plugin-based block. Duplicates if that block is also in a visible region.
• block_content_bundle, from the paragraph_bundle_block_content submodule — embeds a content block entity. Same trigger, different system.
• node_reference_bundle, from the paragraph_bundle_node_reference submodule — embeds a node reference. Never duplicates, because nodes do not render through theme regions at all.

Notice the pattern: only the block-based bundles have this failure mode, and only when the block is also region-placed. The same reasoning applies to Layout Builder blocks and to any custom Twig that calls a block directly.

If you are choosing components for a build in the first place, the overview of Paragraph bundles covers what each one is for. And if this is one symptom of a layout that has grown past what you want to hand-manage, that is what a Drupal architect is for.

Sub-themes inherit the problem

Region definitions live in the theme's .info.yml, and a sub-theme does not inherit its parent's regions — core copies only a couple of housekeeping keys from the base theme, and the region list is not among them. A sub-theme written from scratch therefore has no hidden region until you add one. Solo's shipped solo_subtheme already declares the full region list with hidden among them, so if you started from that there is nothing to copy. Block placement, however, lives in configuration keyed by theme — block.block.* entities carry a theme property. Switching themes does not move your blocks; it leaves the old placements in config and creates new ones. Review block placement per theme after any theme switch, or you will chase the same duplicate through a second theme.

What clean block placement buys you beyond the visual fix

• Layout stability. A block rendered twice occupies space twice. Removing the duplicate removes an unnecessary contributor to cumulative layout shift.
• Accessible landmarks. Screen readers navigate by landmark. Two identical navigation blocks in the accessibility tree is a genuine usability defect, not a cosmetic one.
• Cacheability. A block that renders in two places carries its cache tags into two render subtrees, so an invalidation does twice the work.

Common questions

Can I just disable the block instead of hiding it?

No. A disabled plugin block is not instantiated, so the component has nothing to render. Enabled-but-hidden is the state you want.

Why does clearing cache never fix this?

Because nothing is stale. Drupal is correctly executing two placement instructions. Cache rebuilds reproduce the same correct output.

Does this happen with Layout Builder too?

Yes. Any system that renders a block outside the region pipeline can duplicate a region-placed block. The hidden-region fix applies unchanged.

My theme has no hidden region — is adding one risky?

No. Adding a region to .info.yml and never printing it in page.html.twig has no effect on anything else. Clear caches after the edit so the theme registry picks it up.

How do I find which blocks are duplicating?

View source and search for the block's markup or its id="block-*" attribute. Two matches means two placements; then check Structure > Block layout for the region assignment.

Fixing it on a site you already have

Identify the duplicated block in page source, find its region in Structure > Block layout, move it to the hidden region, add that region to your theme first if it does not exist, and rebuild caches. On a site with a handful of components this genuinely is a few minutes of work.

If your build has dozens of components and the duplication is scattered across content types, that is an architecture review rather than a config edit. Drupal development services covers the component and theme work, or tell me what you are seeing and I will tell you which of the two it is.