by Abhishek Kumar 0 (0 reviews)

RenderWhen for Blocks

Name: RenderWhen for Blocks
Author: Abhishek Kumar

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

RenderWhen for Blocks ranks #67,200 among WordPress.org plugins with 0+ active installations, and was last updated Aug 3, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.8 (Current: 7.1.4)

v1.0.0 Current Version v1.0.0

Updated 3 months ago Last Update on 03 Aug, 2026

Refreshed 1 week ago Last Refreshed on

View on WordPress.org

Rank

#67,200

— No change

Active Installs

-100%

KW Avg Position

N/A

— No change

Downloads

300

+2 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 10%

0+ 10+

39,632

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 9 more installs to reach 10+

Rank Changes

Current #67,200

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.0.0
Last Updated: Aug 03, 2026
Requires WP: 6.5+
Tested Up To: 7.0.8
PHP Version: 7.4 or higher
Author: Abhishek Kumar

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

block-editor blocks conditional gutenberg visibility

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,015

Frequently Asked Questions

Common questions about RenderWhen for Blocks

Yes. Conditions apply to blocks anywhere they render — posts, pages, template parts, navigation menus, and patterns.

Yes. The visibility attribute is registered on every registered block, including blocks from other plugins (ACF Blocks, GenerateBlocks, Stackable, etc.).

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.

Not in v1.0 — one rule per block. AND/OR condition groups are planned for v1.1.

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.

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.

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.

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.

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.

RenderWhen for Blocks

Next Milestone 10

Unlock Exact Install Count

Rank Changes

Upgrade to Pro

Active Installs Growth

Downloads Growth

Upgrade to Pro

Reviews & Ratings

Track This Plugin

Plugin Details

Support & Rating

Keywords

Upgrade to Pro

Similar Plugins

Frequently Asked Questions

Sign In / Register