WordPress dropped its classic editor years ago, and most site owners now build everything block by block. If you run a radio station, a podcast network, or a community broadcast channel, that shift changes how you should pick a player too.
A lot of radio plugins were built for shortcodes first and Gutenberg second. You paste in a shortcode, hope the styling doesn’t break, and cross your fingers when you switch themes. That’s not how block-based sites work anymore.
So we looked at this from a different angle. Instead of ranking plugins by feature count, we tested how well each one fits into the block editor itself. We checked how the block behaves in the inserter, whether you get a live preview while editing, and how much you can style without touching CSS.
Below, we’ll walk through five solid radio player plugins for WordPress and show you how each one behaves inside Gutenberg.
Let’s get in.
Why the Block Editor Changes the Way You Build a Radio Site
Before we get to the plugins, it helps to understand why this matters.
A shortcode is just text. WordPress has no idea what it renders until the page loads on the front end. That means no live preview, no drag-and-drop repositioning, and no easy way to nest your player inside a row or a section built with other blocks.
A native Gutenberg block works differently. It sits in the editor as its own component. You can drag it above your show schedule, drop it inside a two-column layout next to your logo, or place it in a sidebar pattern you reuse across every episode page. What you see while editing stays close to what visitors get on the live site.
This matters even more once you start combining your player with other content. A radio station page usually needs more than audio. It needs a schedule, host photos, a way to show upcoming events, and probably a donate or subscribe button. If your player plugin fights with your layout blocks, you end up wrestling with padding and alignment instead of publishing.
What to Look For in a Ready Radio Player WordPress Plugin
Here’s what actually matters if you’re building your station page inside the block editor instead of relying on shortcodes and custom HTML.
A real block, not a shortcode in disguise. Some plugins label themselves “Gutenberg blocks” but only insert a shortcode field. You still can’t preview the player while editing. Look for plugins that render the actual player inside the editor canvas.
Support for stream formats you actually use. Shoutcast and Icecast cover most live radio setups. If your station uses HLS or a specific CDN, confirm the plugin supports it before you commit.
Style controls inside the block panel. You want to adjust colors, layout, and skin from the block settings sidebar, not by digging into a separate plugin settings page every time you tweak something.
Compatibility with layout blocks. Test whether the player behaves normally inside columns, groups, or third-party layout blocks. Some players break out of their container or ignore width settings.
A sticky or persistent playback option. If listeners browse other pages while your stream plays, sticky playback keeps them tuned in instead of cutting them off the moment they click away.
We used this checklist to test each plugin below.
4 Radio Player Plugins Built for the WordPress Block Editor
1. StreamCast
StreamCast ships with a dedicated Gutenberg block. Search for it directly in the block inserter and drop it anywhere on a page or post. Once it’s placed, you get a live preview right in the editor instead of a placeholder box.
It connects to Shoutcast, Icecast, Radionomy, Radiojar, and RadioCo, covering most independent and community stations. Inside the block settings panel, you can switch between Minimal, Standard, Advanced, and Ultimate layouts, and pick from more than 80 built-in skins without leaving the editor.
The Ultimate layout mode stands out for block-based builds. You can change colors, apply a custom background image, and adjust positioning (left, right, or center) right from the sidebar controls. That means your player can actually match your site’s block-based design instead of looking bolted on.
It also supports keyboard navigation and screen reader access, so accessibility isn’t an afterthought if you’re building a fully block-based, standards-compliant site.
Good fit if: you want the player to visually match a custom block-built theme without writing CSS overrides.
2. Radio Station
Radio Station leans into content structure more than any other plugin on this list, and that makes it a strong match for block-based site building. It adds a custom post type for shows, so each program gets its own page with scheduling details, host info, and metadata, all manageable from blocks and widgets.
You can display your weekly schedule as a table, tabs, or a list, and the plugin automatically converts show times to each listener’s local timezone. It also supports Genre and Language taxonomies, so you can organize shows the same way you’d organize blog categories.
The built-in stream player supports MP3, AAC, OGG, WebM, and OPUS, with a few skins to choose from, including Howler and jPlayer. You can place everything from the show archive to the stream player with Gutenberg blocks or classic widgets, so it fits naturally into a page built from block patterns.
Good fit if: your station runs multiple shows and you want a dedicated, structured page for each one.
3. MP3 Audio Player by Sonaar
MP3 Audio Player by Sonaar started as a music and podcast player, and that history shows in how well it handles mixed content. If your site plays both live radio and on-demand tracks, this plugin handles both from the same block without switching tools.
It supports Icecast streaming with metadata like song titles and cover art, and the Gutenberg block gives you a real editor preview instead of a static placeholder. Layout options include waveform visualizations, coverflow, and compact views, so you can match the player’s look to the rest of your block-built page.
The Pro version adds a sticky player and call-to-action buttons you can attach directly to the player. That’s useful for donation prompts or promo links without needing a separate button block stacked underneath.
Good fit if: you mix live streaming with on-demand playlists and want one player block to handle both.
4. AudioIgniter
AudioIgniter wasn’t built specifically for radio, but it handles live streaming from Shoutcast, Icecast, and Radiojar well enough to make this list. It works across Gutenberg, Elementor, and Visual Composer, so it’s a safe pick if your site mixes editors during a transition period.
Inside the block, you can toggle cover art, track listings, and artist names on or off. That keeps the layout simple if you just want a clean stream player without extra clutter. It also supports WooCommerce, so stations that sell merchandise or digital downloads alongside their stream have a built-in path to do that.
Good fit if: you want a lightweight player block and might add WooCommerce or a page builder mix later.
Building a Complete Radio Station Page with Blocks
This is where a block-based approach beats a shortcode-heavy build. Once your player block is in place, you can build out the rest of the station page in the same editor, with no separate plugin settings screens and no custom code.
Here’s a practical layout using bBlocks alongside your radio player block:
Hero section with the live player. Place your radio player block inside a Row Columns block, next to a Section Heading that states your station name and tagline. Keep this above the fold so visitors can hit play immediately.
Host and DJ profiles. Use the Team Member block to introduce your hosts with photos, bios, and social links. This humanizes the station and gives return listeners a reason to check the page beyond just tuning in.
Show schedule as tabs. Instead of a plain table, drop your weekly lineup into the Advanced Tabs block, one tab per day. It keeps the page shorter and easier to scan on mobile, where most listeners are probably browsing anyway.
Listener testimonials. If your station has loyal fans, the Testimonial block turns their comments into a scrolling, styled carousel. Pair it with the Star Rating block if you collect any kind of listener feedback score.
Upcoming events or pledge drives. The Countdown block works well here. If you run seasonal fundraisers or special broadcasts, a visible countdown creates urgency without a line of code.
Show archive. Use the Posts block to pull in recent episode write-ups or news posts automatically, filtered by category, so the page stays current without manual updates.
FAQ section. Close the page with the Accordion block for common listener questions, like how to tune in on mobile or how to submit song requests. It keeps the page from feeling cluttered while still covering the details.
Call to action. Finish with a Button block linking to your donation page, newsletter signup, or app download. Keep the label direct. “Support the Station” works better than something vague.
None of this requires a separate page builder plugin running alongside WordPress. It’s all native blocks working together, and that keeps your site lighter and easier to maintain long term.
Design and Performance Tips for a Faster Radio Page
A radio player streams continuously, and that puts more load on your page than a typical blog post. A few adjustments help keep things smooth.
Lazy-load everything below the player. Your hero section and player should load first. Images in your host profiles, show archive, and testimonials can load as visitors scroll.
Avoid stacking too many animated blocks near the player. Countdown timers, animated counters, and sliders all run JavaScript. Spread them across the page instead of grouping them near your stream, so the audio doesn’t stutter while other elements animate.
Test your sticky player on mobile first. Sticky playback works great on desktop, but on smaller screens, it can cover navigation or content if it’s not sized correctly. Check it on an actual phone, not just a resized browser window.
Keep your color palette consistent across blocks. When your player skin, buttons, and section backgrounds pull from the same two or three brand colors, the page feels intentional instead of assembled from mismatched parts.
Explore the 5 WordPress Post Grid Plugins Compared for Better Gutenberg Design Workflows.
Common Mistakes to Avoid When Adding a Live Stream in Gutenberg
We see a few patterns repeat across radio station sites, so it’s worth calling them out directly.
Using an HTTP stream URL on an HTTPS site. Browsers block mixed content by default, so your player silently fails to load. Confirm your stream source supports HTTPS, or use a proxy add-on if your plugin offers one.
Placing the player block inside a container with a fixed height. Some layout blocks apply a max height that clips the player’s controls. Always preview on the front end after placing a player inside a custom container.
Skipping a check after a theme switch. Even native Gutenberg blocks can shift slightly when your theme changes its default spacing or font sizes. A quick front-end check after any theme update saves you from an awkward-looking player going unnoticed for weeks.
Adding too many players on one page. Multiple simultaneous streams confuse visitors about which one is actually live. Stick to one primary player per page unless you’re specifically building a multi-channel directory.
Check also 6 Best WordPress Audio Player Plugins, Compared for Every Type of Site.
FAQs About Radio Player Plugins for WordPress
Do these radio player plugins work without a page builder like Elementor?
Yes. All five plugins we covered offer native Gutenberg blocks, so you don’t need Elementor or any other page builder to add a working stream player.
Can I combine a radio player block with other block plugins on the same page?
In most cases, yes. StreamCast, Radio Player, and MP3 Audio Player by Sonaar all render properly inside layout blocks like columns and groups, so they combine easily with a block library like bBlocks.
Which plugin is best for a station with multiple shows and hosts?
Radio Station is the strongest option here, since it adds a dedicated post type for shows with scheduling, host roles, and taxonomy support built in.
Will a sticky player slow down my site?
A well-coded sticky player adds minimal overhead. The bigger factor is usually how many other animated or media-heavy blocks you stack on the same page, not the sticky player itself.
Can I show a schedule and a live player on the same page without it feeling cluttered?
Yes, if you organize content with tabs or accordions instead of listing everything in one long scroll. Splitting your schedule into tabs by day, as we outlined above, keeps the page clean.
Do I need coding skills to style the player to match my brand?
No. All five plugins offer style options inside their block settings panel, including colors, layouts, and in some cases custom backgrounds, so you can match your brand without touching CSS.
Final Thoughts
Picking a WordPress radio player plugin isn’t just about which one streams audio reliably. If you’re building your site with the block editor, how well that plugin fits into your existing blocks matters just as much.
StreamCast and Radio Player both offer strong native Gutenberg support with real editor previews, making them easy first picks. Radio Station is worth the extra setup time if you’re running a full schedule of shows with individual hosts. And once your player is in place, building out the rest of the page (host profiles, testimonials, an FAQ, a schedule) becomes a matter of stacking the right blocks together.
That’s the real advantage of a block-first approach. You’re not managing five different tools to build one page. You’re using the same editor, the same blocks, and the same design system for everything, from the live stream down to the donate button at the bottom of the page.
Leave a Reply