by wowDevs
4.5 (2 reviews)
Responsive Visibility — Show or Hide Blocks by Device, Custom Breakpoints & Conditions
Show or hide any Gutenberg block by device, custom breakpoint, or condition — login, user role, post type & more. No CSS, no code.
Compatible with WP 7.0.2
v1.2.1
Current Version v1.2.1
Updated 1 week ago
Last Update on 08 Jul, 2026
Refreshed 7 hours ago
Last Refreshed on
Rank
#15,626
—
No change
Active Installs
100+
-23.1%
KW Avg Position
59.3
—
No change
Downloads
2.1K
+1 today
Support Resolved
0%
—
No change
Rating
90%
Review 4.5 out of 5
4.5
(2 reviews)
Next Milestone 200
100+
200+
2,860
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
Need 68 more installs to reach 200+
Rank Changes
Current
#15,626
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
4.5
2 reviews
Overall
90%
5
1
(50%)
4
1
(50%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 4 of 4| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| visibility | 23 | — | Tag | 1 day ago |
| block visibility | 42 | — | Tag | 1 day ago |
| conditional blocks | 77 | — | Tag | 1 day ago |
| responsive | 95 | — | Tag | 1 day ago |
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.2.1
- Last Updated
- Jul 08, 2026
- Requires WP
- 6.2+
- Tested Up To
- 7.0.2
- PHP Version
- 7.2 or higher
- Author
- wowDevs
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 4.5
- Reviews
- 2
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Responsive Visibility — Show or Hide Blocks by Device, Custom Breakpoints & Conditions
Yes. Responsive Visibility adds its controls to every standard Gutenberg block and works with most third-party and dynamic blocks too. It's a block extension, so the visibility options appear automatically wherever you edit.
Go to Settings → Responsive Visibility. Add a new breakpoint, give it a name (for example "Widescreen"), and set its max-width in pixels. The plugin generates the matching CSS media query automatically, and the new breakpoint appears in every block's visibility controls. You can add as many as you like.
It hides blocks with CSS classes and media queries — the block stays in the page HTML but is set to display:none on the device sizes you selected. This keeps the same markup for every visitor.
Yes. Because visibility is CSS-based, every visitor receives identical HTML, so it is fully compatible with full-page caching and CDNs. Visibility also updates live as the browser is resized.
No. The plugin outputs a single small inline <style> block in the page head and adds no extra HTTP requests or JavaScript on the front end. It stays lightweight by design.
Yes. Responsive Visibility works with block themes, classic themes, and Full Site Editing contexts.
Yes. Backward compatibility is a core promise. Blocks hidden with older versions continue to work unchanged — legacy device settings are always honored, and your saved breakpoints are never regenerated or lost.
No. Responsive Visibility is built specifically for the WordPress block editor (Gutenberg) and does not control content rendered by Elementor or other page builders.
Yes, the plugin works on standard WordPress multisite installations.
Conditions let you show or hide a block based on the visitor, the page, or the current request URL: Login Status, User Role, Specific User, Specific Post/Page, Post Type, Page Type, URL Query Param, or Shortcode. Enable conditions in the block's "Visibility Conditions" panel, choose Show or Hide, add one or more conditions, and pick whether All or Any of them must match. Unlike device hiding (which uses CSS), conditions are evaluated on the server, so gated content is never placed in the page source.