Abhishek Kumar

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:
<blockquote>
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.
</blockquote>
RenderWhen is built around two ideas that set it apart from other visibility plugins:
<ul>
<li>Server-side rendering only. When a block is hidden by a condition, it is not rendered into the page output at all. No CSS <code>display: none</code>, no DOM bloat, no leaked content in view-source. Search engines, screen readers, and your page weight all benefit.</li>
<li>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.</li>
</ul>
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.
<h4>Built-in conditions (v1.0)</h4>
<ul>
<li>User state — show to logged-in users, logged-out users, or specific roles</li>
<li>Date range — show between two datetimes, timezone-aware</li>
<li>Device type — show on desktop, tablet, or mobile</li>
</ul>
<h4>Designed for</h4>
<ul>
<li>Agencies and freelancers building client sites who want a clean, predictable visibility tool</li>
<li>Developers who need an extension point, not another walled garden</li>
<li>Anyone who cares about page weight and SEO hygiene</li>
</ul>
<h4>What this plugin deliberately does NOT do</h4>
It does one thing well rather than ten things adequately. Out of scope in v1.0:
<ul>
<li>Multi-condition AND/OR groups (planned for v1.1)</li>
<li>URL / cookie / referrer / geolocation conditions</li>
<li>WooCommerce, ACF, or membership integrations</li>
<li>A settings dashboard</li>
</ul>
If you need those today, <a href="https://wordpress.org/plugins/conditional-blocks/" rel="ugc">Conditional Blocks</a> and <a href="https://wordpress.org/plugins/block-visibility/" rel="ugc">Block Visibility</a> are excellent and well-established choices.
<h4>For developers</h4>
Register a custom condition in three steps. Implement the interface, add it to the registry, ship.
<pre><code>add_action( 'renderwhen_register_conditions', function ( $registry ) {
 $registry->register( new My_Plugin\\Conditions\\Country_Condition() );
} );
</code></pre>
Your condition class implements <code>RenderWhen\Conditions\Interface_Condition</code>:
<pre><code>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 );
 }
}
</code></pre>
The full set of public filters:
<ul>
<li><code>renderwhen_register_conditions</code> — register your conditions here</li>
<li><code>renderwhen_evaluate_{condition_id}</code> — last-mile override of any condition’s result</li>
<li><code>renderwhen_render_block_hidden</code> — fires when a block is hidden, useful for cache busters and SEO tools</li>
<li><code>renderwhen_device_type</code> — swap in your own device detection</li>
</ul>
The plugin is developed openly on GitHub. Issues, PRs, and architecture discussions welcome: https://github.com/abhishekfdd/renderwhen

RenderWhen for Blocks

Show or hide any block when conditions match. Developer-first API and true server-side rendering — hidden blocks never reach the browser.

Dynamic.ooo

Build smarter websites with Dynamic Visibility for Elementor
Create personalized experiences by showing the right content to the right users at the right time. Perfect for membership sites, WooCommerce stores, landing pages, and content personalization.
<h4>Key Features</h4>
User-Based Visibility 
* User roles & capabilities 
* Logged-in or logged-out users 
* User metadata 
* IP address restrictions
Time & Date Conditions 
* Schedule content (from-to dates) 
* Day of the week 
* Time of day (hour range) 
* Perfect for limited-time offers and events
Content & Context 
* Custom field values 
* Specific pages or post types 
* Referral source (where users come from) 
* Browser & device detection
WooCommerce Integration 
* Product visibility based on cart content 
* Product types
Flexible Display Options 
* Hide via CSS or remove from DOM completely 
* Fallback content (e.g., “Coming soon”, login form) 
* AND/OR logic for multiple conditions 
* Works with Events trigger for interactive reveals
<h4>Perfect For</h4>
<ul>
<li>Membership Sites: Show content only to subscribers</li>
<li>WooCommerce: Display special offers to specific customers</li>
<li>Landing Pages: A/B testing and personalization</li>
<li>Maintenance Mode: Hide sections under development</li>
<li>GDPR Compliance: Show cookie notices based on location</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Edit any page with Elementor</li>
<li>Select your widget, section, container or column</li>
<li>Open the Visibility tab in Advanced settings</li>
<li>Enable Dynamic Visibility and configure your conditions</li>
<li>Save and preview!</li>
</ol>
<a href="https://www.dynamic.ooo/dynamic-visibility-for-elementor/" rel="nofollow ugc">More info</a> 
<a href="https://www.dynamic.ooo/dynamic-visibility-for-elementor/try" rel="nofollow ugc">Try now on a sandbox</a>
<h4>Upgrade to Dynamic Content for Elementor</h4>
Get 150+ advanced features including:
<ul>
<li>Custom PHP Conditions: Write unlimited custom logic</li>
<li>Advanced Dynamic Tags: Post data, user data, ACF fields, and more</li>
<li>Template System: Create reusable content templates</li>
<li>Dynamic Posts Widget: Advanced query builder</li>
<li>Integrations: ACF, JetEngine, Meta Box, Toolset, WooCommerce, WPML, Search and Filter Pro</li>
<li>Premium Support: Priority email support</li>
</ul>
<h4>Documentation & Support</h4>
<ul>
<li><a href="https://dnmc.ooo/visibilitydoc" rel="nofollow ugc">Documentation</a></li>
<li><a href="https://facebook.com/groups/dynamic.ooo" rel="nofollow ugc">Facebook Community</a></li>
<li>Free support via WordPress.org forums</li>
</ul>

Dynamic Visibility for Elementor


It works like a charm and beautifully integrated.


Just great! Thank you!


Please ignore the few angry 1-star reviews here. If you have a clean set up of you website, -meaning not loads of potentially conflicting plugins-than this is an amazing tool. Always test on a clean site before jumping to conclusions. 



Their support is top notch, I can say by my own experience. Highly recommended!!


Works great on a well built website!

Show or hide Elementor widgets, containers, columns, and pages based on user role, date, device, and many other powerful conditions.

RenderWhen for Blocks vs Dynamic Visibility for Elementor