Free WordPress block patterns: where to find good ones, and how to tell
Where free WordPress block patterns come from (the pattern directory, your theme, free plugins) and three checks that tell a good one from one that breaks your design.
Good free block patterns come from three places: the WordPress.org pattern directory, the theme you already have, and free pattern plugins listed on WordPress.org. A good one passes three checks you can run in a minute: it takes your theme's colours and fonts, it is built only from core blocks, and it keeps working when the plugin that supplied it is gone. Free is not the problem with a bad pattern. A pattern that fails those checks costs the same whether you paid for it or not: a section that does not match the rest of the site, and stays that way.
Your theme already has some#
Start in the inserter, under the Patterns tab, before you go looking anywhere else. A block theme registers its own patterns from its patterns/ folder, and Twenty Twenty-Five, the default theme since WordPress 6.7, ships a large set: heroes, testimonials, pricing, whole page layouts.
Theme patterns have one real advantage: they were designed against that theme's palette, fonts and spacing, so they look right on insert. The cost arrives when you change theme. Patterns you already inserted stay on the page, because insertion copies the markup into the post, but the theme's other patterns leave the inserter with it.
The WordPress.org pattern directory#
The pattern directory is free and open to anyone with a WordPress.org account. The editor loads a curated selection of it into the Patterns tab, a theme can name more in the patterns key of its theme.json, and anything else you copy from the directory page and paste into the editor. Submissions are moderated, and the directory's guidelines ask for core blocks only, so a directory pattern should not depend on a plugin.
The quality varies, because the contributors do. Some patterns state colours and font sizes of their own, which is allowed and is the most common reason a directory pattern looks wrong in your theme. Treat a directory pattern as a starting point you will check, not a finished section.
Free pattern plugins#
A plugin can register patterns into the inserter under its own category, and several free ones on WordPress.org do. Our own, Pattern Paste Block Patterns, adds 64 Core Patterns that state no colour and no font of their own.
A plugin is the source that most needs checking, because a plugin can supply blocks as well as patterns. A pattern made of the plugin's own blocks is a pattern that stops rendering properly when the plugin is deactivated. That is fine if you decided to depend on the plugin. It is a problem if you only wanted a hero.
Where block patterns come from goes further into what each source leaves in your page, including synced patterns and remote loading.
Check one: does it take your theme's colours and fonts?#
Insert the pattern, then switch your theme's style variation under Styles in the Site Editor. A pattern that follows your theme changes with it. One that keeps its own navy band or its own typeface has those values typed into it.
To see why, open the Code editor (the three-dot menu, then Code editor) and look at the block comments. Theme presets look like this:
<!-- wp:group {"backgroundColor":"accent-1","textColor":"contrast"} -->
A colour typed in looks like this, and it wins over your theme everywhere it appears:
<!-- wp:group {"style":{"color":{"background":"#1b2a4a","text":"#ffffff"}}} -->
The same goes for fontFamily and a fontSize stated in pixels inside style. One or two can be swapped for presets in the sidebar. A pattern full of them is a design for someone else's site. theme.json colour presets explains how the preset version works.
Check two: is it core blocks only?#
In the Code editor, read the block names. Core blocks are written without a namespace (wp:group, wp:columns, wp:cover) or with core/. Anything else, such as wp:somevendor/container, comes from a plugin.
A plugin block is not a defect, but it is a dependency you should choose on purpose. The page will need that plugin installed and updated for as long as the section exists.
Check three: what happens when the source goes away?#
Deactivate the plugin that supplied the pattern, on a staging copy, and reload the page. A core-block pattern looks exactly as it did: its markup is in the post and its styles come from WordPress and your theme. A pattern built on plugin blocks shows its saved HTML without the plugin's styling, or, for blocks rendered on the server, nothing at all, and the editor reports a block your site does not support.
Also look for a pattern that loads something: a <script>, a <style> inside a Custom HTML block, a web font from a third-party server. Each one is a request on every page view and a thing that breaks when its host changes.
What free patterns are not good at#
Free sources are good at common sections in neutral styling. They are weaker at depth: a dozen ways to lay out a pricing table, an FAQ that reads as a ledger, a footer for a site with forty links. That is where a paid library earns its place, and where you should hold it to the same three checks.
What to do on Monday#
Open the Patterns tab in your own site and see what your theme already gives you. For anything from elsewhere, insert it on a draft, switch the style variation, read the block names in the Code editor and deactivate its plugin on staging. Keep the patterns that pass all three, and delete the rest from the draft before they reach a live page.
Every Pattern Paste Core Pattern, free or paid, is core-block markup with no colour or font of its own, checked for legibility in Twenty Twenty-Five and Twenty Twenty-Four; the free plugin puts 64 of them in the inserter under the Pattern Paste Core category.






