Conditional Blocks allows you to create unique content for your visitors and customers. Visibility control with WordPress blocks is now easy within the WordPress Block Editor.
Be creative, build templates with dynamic content — you can change blocks to be visible or hidden, grouped blocks and each nested block even reusable blocks! We plan on having Conditional Blocks ready for Full Site Editing (FSE) themes, if you have any ideas — let us know.
What can conditional blocks do?
Conditional Blocks makes it easy to change visibility of any block with a few clicks. See the below features to get ideas for conditional content in WordPress.
Included condition types in the free version:
- Create Custom Visibility Conditions for WordPress Blocks.
- Hide blocks from everyone using the «Lockdown» condition. Great for when you are preparing new content.
- Show or Hide block based user state (logged in users or logged out users). Great for creating membership content for signed in users.
- Show or hide block on mobile screens.
- Show or hide block on tablet screens.
- Show or hide block on desktop screens.
- Modify the screen sizes to fit the devices using the CSS breakpoints of your theme.
You can create conditional widgets in sidebars using any of the built-in visibility logic. Fully compatible with WordPress block widgets and Full Site Editing themes.
Do more with Conditional Blocks Pro
We’ve designed Conditional Blocks Pro to be flexible and allow you to toggle blocks for a wide range of visibility conditions. Exclusively includes the ability to set WooCommerce conditional content.
- Show block depending on user roles (WooCommerce Customer, admin, editor, subscriber, custom roles, etc).
- Show block content for between date ranges, times, days of the week.
- Show block for any device and browser (HTTP UserAgent) (iPhone, Android, macOS, linux and Windows).
- Show block based on URL Referer (e.g if user came from Google.com or twitter.com).
- Show block based on post meta fields, including custom meta fields and data.
- Show block based on URL query strings (URL variables), You display custom confirmation content for form plugins like Gravity Forms.
- Show block based on post ID or hide block on post IDs and URL Paths.
- Show blocks based on Posts, Custom Post Types, Taxonomies and terms. Automatically detects custom taxonomies and terms.
- Show blocks for custom fields, user meta, post meta.
- Toggle blocks based on Archives.
- Create and manage presets of conditions to apply to multiple blocks across your whole site.
- Show block based on PHP Logic and custom functions. The possibilities are unlimited with custom conditions.
- WooCommerce — change the visibility of blocks based on total cart value of the current customer. Perfect for upselling.
- WooCommerce — We have even more WooCommerce conditions for blocks coming, each condition will help you create dynamic upsells for smart marketing.
- WooCommerce Products in cart, total cart value, total customer spent in store.
- WooCommerce Geo Location — toggle any WordPress Blocks based on the customers country using their IP Address.
- WooCommerce Customer Recent Order — Check the current customer has place and order within a set amount of time (days, hours, or minutes).
- Support development of new features.
Conditional Blocks Pro gives you even more control over block visibility — Ready for Full Site Editing, widget options and general content blocks.
Create content while your page is live.
You can use the Lockdown condition to create draft blocks. Once your blocks are ready to be published you can remove the condition. Safely work on your published WordPress content over multiple days by hiding the blocks that aren’t yet finished. Just make them visible on when you are ready.
Restrict block content
Restrict any WordPress Block by simply clicking on it inside the WordPress Block Editor. You can open the Condition Builder and add visibility rules to the selected block. You’ll be able to set it to appear for logged in or out users only.
Great for creating content that’s visible to members only on your site.
Control Mobile Blocks
You can select specific screen sizes to display your blocks on, and exclude them from others! Pick and choose where responsive blocks should be shown mobile, tablet or desktop. The block content will automatically be displayed or hidden for each different screen sizes.
Conditional Blocks works with any theme that uses the WordPress Block Editor (Gutenberg Block Editor).
We’ve tested Conditional Blocks with the follow plugins and themes:
- Stackable Blocks
- Atomic Blocks
- WooCommerce Blocks (Product Blocks)
- Easy Digital Downloads Blocks
- Ultimate Addons for Gutenberg
- Otter Blocks & Templates
- Kadence Blocks
- Genesis Blocks
- Twenty Twenty Two theme
- Wabi theme
- Poe theme
- WooCommerce Storefront
Please reach out for support if you are experiencing issues with another plugin.
Conditional Blocks for Gutenberg Installation Instructions:
- Upload the Conditional Blocks plugin to your /wp-content/plugin/ directory or through the plugin admin section under «add new».,
- Activate the plugin through the ‘Plugins’ menu in WordPress.,
- That’s it!
Can I conditionally hide blocks?
Yes, you can conditionally hide any Gutenberg block using any of the condition types.
Does Conditional Blocks work for block widgets?
Yes, you can use Conditional Blocks with Widget areas and sidebars using the new Widget Editor in WordPress 5.8+.
Can I toggle the visibility of nested blocks inside a Group Block?
Yes, you can apply conditional visibility rules to the WordPress Group Block. Each nested block will follow the same rules, you can also apply additional rules to each nested block.
Can I add custom conditions for my content?
You can use Conditional Blocks Pro and the PHP logic condition to create custom visibility conditions for blocks.
How do I request a feature?
We are happy to hear about your ideas! Reach out to us via support
Contributors & Developers
“Conditional Blocks — Content Visibility Control for Full Site Editing” is open source software. The following people have contributed to this plugin.Contributors
“Conditional Blocks — Content Visibility Control for Full Site Editing” has been translated into 2 locales. Thank you to the translators for their contributions.
Interested in development?
- Ready and tested for WordPress 6.1
- Fixed: Consistenty for labels and help text for conditions fields with the Conditions API.
See all the details: Release post for Conditional Blocks v3
- New: OR logic is now possible by creating multiple Condition Sets per block.
- New: Integration API to register custom conditions. Custom Conditions are added directly to the Condition Builder. See our Developer Integration Guide.
- Improved: UI has been refined.
- Improved: Automatically a default condition to reduce clicks when opening the Condition Builder.
- Tested: WooCommerce 7.0 Ready
- New: WooCommerce Customer Geo Location Condition (Pro)
- New: WooCommerce Customer Recent Order Condition (Pro)
- Improved: PHP Logic now shows all registered custom function within the Condition Builder. (Pro)
- Improved: Increased the height and width of the Condition Builder for easier navigation.
- Fixed: Typos.
- Tested and ready for WordPress 6.0 & Full Site Editing.
- Tested and ready for WordPress 5.9
- Improved: Code Refactored
- Improved: Refined the indicator when a block is conditional within the WordPress editor.
Read the full release notes
Tested and ready for WordPress 5.8
New: Lockdown Condition (Hide block for everyone).
New: Most conditions now have a selectable «Block Action» where you can choose if the block should be visible or hidden when the condition is met.
Improved: UI — easily to select your options, the modal is now slimmer, matching the current WordPress Admin UI colors.
Improved: Refactored condition checking.
Improved: Fully translatable.
Release notes: https://conditionalblocks.com/v2-3-woocommerce-condition/
- Improved and categorised the condition selector, now with «type to search» support.
Conditional Blocks Pro
* New — WooCommerce support available in Conditional Blocks Pro. Control the visibility of blocks using the customers total cart value.
- Improved performance by only including the CSS for responsive blocks on the pages they are used.
Complete rebuild of Conditional Blocks. Please read the 2.0 introduction & release notes https://conditionalblocks.com/introducing-conditional-blocks-2-0/
- Conditional Blocks 2.0 is a complete rebuild.
- Existing users can safely update, old conditions will continue to work in the background. Editing blocks with old conditions will require clicking «Convert to 2.0 conditions», when opening the new Condition Builder.
- Ready for WordPress 5.7 and Gutenberg 10.1
- Fixed: Inner blocks conditions work as expected again.
- Ready and tested with WordPress 5.6
- Improved compatibility with themes that could be overriding css. https://wordpress.org/support/topic/maybe-adds-important-css-rules/
- Tested: with GenerateBlocks.
- Fixed: Added a fix to the issue where server side rendered blocks would cause errors with Conditional Blocks. https://github.com/WordPress/gutenberg/issues/16850
- Ready for WordPress 5.5
- Added feature to modify the CSS breakpoints.
- Updated date range conditions in Conditional Blocks Pro
- Fixed issue where MomentJS could not be found in Conditional Blocks Pro
- Ready and tested with WordPress 5.4
- Pro: Fixed date conditions sometimes applying to new blocks when new dates are added.
- Minor code improvements.
- Tested with Gutenberg 7.7.1
- Improved how device size conditions are handled across all blocks.
- Fixed hiding on device sizes across could cause full-width blocks to be standard size.
- Fixed Conditional Blocks highlighting for Gutenberg 7.4+
- Fixed postmeta condition being skipped.
- Fixed postmeta condition saving incorrectly on blocks.
- Removed Freeemius and tracking.
- New Date Range Conditions for Blocks in Pro! Learn about Date Conditions
- Improved JS browser caching with file versions.
- Improved code structure.
- Fixed conflict with Yoast and other plugins which triggers Gutenberg by using React.
- initial Release of Conditional Blocks for Gutenberg.