Title: RenderWhen for Blocks Author: Abhishek Kumar Published: May 17, 2026 Last modified: May 17, 2026 --- Search plugins ![](https://ps.w.org/renderwhen/assets/banner-772x250.png?rev=3534394) ![](https://ps.w.org/renderwhen/assets/icon-256x256.png?rev=3534394) # RenderWhen for Blocks By [Abhishek Kumar](https://profiles.wordpress.org/abhishekfdd/) [Download](https://downloads.wordpress.org/plugin/renderwhen.1.0.0.zip) * [Details](https://wordpress.org/plugins/renderwhen/#description) * [Reviews](https://wordpress.org/plugins/renderwhen/#reviews) * [Installation](https://wordpress.org/plugins/renderwhen/#installation) * [Development](https://wordpress.org/plugins/renderwhen/#developers) [Support](https://wordpress.org/support/plugin/renderwhen/) ## Description RenderWhen for Blocks adds conditional visibility to every block in the WordPress block editor. Decide who sees what, and when, with a panel that reads exactly how you’d say it out loud: > _Show this block when the user is logged in._ > _Show this block when the date > is between March 1 and March 31._ _Show this block when the device is mobile._ RenderWhen is built around two ideas that set it apart from other visibility plugins: * **Server-side rendering only.** When a block is hidden by a condition, it is not rendered into the page output at all. No CSS `display: none`, no DOM bloat, no leaked content in view-source. Search engines, screen readers, and your page weight all benefit. * **Public Conditions API.** The three built-in conditions are registered through the same public API your plugin or theme can use to add your own. No hacks, no internal-only code paths. In the editor, a subtle dashed border marks every block that carries a visibility rule, so a rule-bearing block never disappears from the published page as a surprise. A “Preview as audience” sidebar lets you simulate a logged-out visitor, a specific role, or a different device class right in the editor — blocks whose rule would hide them fade out with a clear badge, no save-and-reload cycle required. #### Built-in conditions (v1.0) * **User state** — show to logged-in users, logged-out users, or specific roles * **Date range** — show between two datetimes, timezone-aware * **Device type** — show on desktop, tablet, or mobile #### Designed for * Agencies and freelancers building client sites who want a clean, predictable visibility tool * Developers who need an extension point, not another walled garden * Anyone who cares about page weight and SEO hygiene #### What this plugin deliberately does NOT do It does one thing well rather than ten things adequately. Out of scope in v1.0: * Multi-condition AND/OR groups (planned for v1.1) * URL / cookie / referrer / geolocation conditions * WooCommerce, ACF, or membership integrations * A settings dashboard If you need those today, [Conditional Blocks](https://wordpress.org/plugins/conditional-blocks/) and [Block Visibility](https://wordpress.org/plugins/block-visibility/) are excellent and well-established choices. #### For developers Register a custom condition in three steps. Implement the interface, add it to the registry, ship. ``` add_action( 'renderwhen_register_conditions', function ( $registry ) { $registry->register( new My_Plugin\\Conditions\\Country_Condition() ); } ); ``` Your condition class implements `RenderWhen\Conditions\Interface_Condition`: ``` namespace My_Plugin\Conditions; use RenderWhen\Conditions\Interface_Condition; class Country_Condition implements Interface_Condition { public function get_id(): string { return 'country'; } public function get_label(): string { return __( 'Visitor country', 'my-plugin' ); } public function get_schema(): array { return array( 'type' => 'object', 'properties' => array( 'countries' => array( 'type' => 'array', 'items' => array( 'type' => 'string' ), ), ), ); } public function evaluate( array $settings, array $context ): bool { $current = my_plugin_detect_country(); return in_array( $current, $settings['countries'] ?? array(), true ); } } ``` The full set of public filters: * `renderwhen_register_conditions` — register your conditions here * `renderwhen_evaluate_{condition_id}` — last-mile override of any condition’s result * `renderwhen_render_block_hidden` — fires when a block is hidden, useful for cache busters and SEO tools * `renderwhen_device_type` — swap in your own device detection The plugin is developed openly on GitHub. Issues, PRs, and architecture discussions welcome: https://github.com/abhishekfdd/renderwhen ## Screenshots * [[ * The Visibility panel in the block inspector * [[ * User State condition with role selector * [[ * Date Range condition with start/end pickers * [[ * Device type condition with three checkboxes * [[ * Editor indicator showing dashed border on rule-bearing blocks ## Installation 1. Upload the `renderwhen` folder to `/wp-content/plugins/`, or install through the** Plugins Add New** screen 2. Activate the plugin 3. Edit any post or page, select a block, and find the **Visibility** panel in the block inspector There is no settings page. By design. ## FAQ ### Does this work with the Site Editor? Yes. Conditions apply to blocks anywhere they render — posts, pages, template parts, navigation menus, and patterns. ### Does this work with third-party blocks? Yes. The visibility attribute is registered on every registered block, including blocks from other plugins (ACF Blocks, GenerateBlocks, Stackable, etc.). ### Will hidden blocks affect SEO? Hidden blocks are never rendered into the page HTML. Search engines see what your visitors see — not the hidden content. This is the opposite of CSS-based hiding, where the content is still in the DOM. ### Can I combine multiple conditions on one block? Not in v1.0 — one rule per block. AND/OR condition groups are planned for v1.1. ### What does the dashed border on some blocks mean? The dashed left border indicates a block has a visibility rule attached. It’s editor- only — visitors never see it. The cue helps prevent confusion when blocks disappear from the published version. ### Why do role-restricted blocks appear hidden when I preview as “Any role”? The preview can’t know which roles an arbitrary visitor would have. When you preview as “Any role,” role-restricted blocks appear hidden because the safest assumption is that an unknown visitor doesn’t have the required role. To verify a role-restricted block actually shows for that role, pick the specific role from the preview dropdown. ### How does this compare to Block Visibility or Conditional Blocks? Both are excellent, mature plugins with broader feature sets. RenderWhen is intentionally smaller in surface area, server-side-only in rendering, and built around a public extension API. If you need ACF/WooCommerce/cookie conditions today, use one of those. If you want a small, fast, extensible foundation, this is for you. ### How does device detection work? By default, via `wp_is_mobile()` plus a user-agent check for tablets. The result is filterable via `renderwhen_device_type` so you can plug in a more sophisticated library. ### Is this caching-friendly? Mostly yes — visibility is evaluated at render time, so server-side page caches will cache whatever was rendered for that request. For varying-by-user content ( login state, role), you’ll want a cache layer that varies on cookies. The `renderwhen_render_block_hidden` action is provided so cache plugins and edge integrations can hook in. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “RenderWhen for Blocks” is open source software. The following people have contributed to this plugin. Contributors * [ Abhishek Kumar ](https://profiles.wordpress.org/abhishekfdd/) [Translate “RenderWhen for Blocks” into your language.](https://translate.wordpress.org/projects/wp-plugins/renderwhen) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/renderwhen/), check out the [SVN repository](https://plugins.svn.wordpress.org/renderwhen/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/renderwhen/) by [RSS](https://plugins.trac.wordpress.org/log/renderwhen/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.0 * Initial release. * Three built-in conditions: user state, date range, device type. * Public Conditions API. * Editor indicator and “Preview as…” mode. ## Meta * Version **1.0.0** * Last updated **5 hours ago** * Active installations **Fewer than 10** * WordPress version ** 6.5 or higher ** * Tested up to **6.9.4** * PHP version ** 7.4 or higher ** * Tags * [block-editor](https://wordpress.org/plugins/tags/block-editor/)[blocks](https://wordpress.org/plugins/tags/blocks/) [conditional](https://wordpress.org/plugins/tags/conditional/)[gutenberg](https://wordpress.org/plugins/tags/gutenberg/) [visibility](https://wordpress.org/plugins/tags/visibility/) * [Advanced View](https://wordpress.org/plugins/renderwhen/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/renderwhen/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/renderwhen/reviews/) ## Contributors * [ Abhishek Kumar ](https://profiles.wordpress.org/abhishekfdd/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/renderwhen/)