Luna Web Radio Player Plugin Media is a JavaScript-based audio player that embeds a live internet radio stream into a web page and displays the current track information alongside the controls. It is sold on CodeCanyon by the developer sodah for $29, and it targets website owners who run or promote a radio station and want a self-hosted player rather than an iframe supplied by a streaming host. With 2,413 sales and a 4.56 out of 5 rating across 144 reviews, it is one of the more established options in this narrow category.
The product is a front-end player, not a streaming server. It does not host audio, transcode formats or manage playlists. It connects to an existing stream and renders the listening experience in the browser, which is the part most radio sites struggle to get right.
What the Player Actually Does
The core function is straightforward: point the script at a stream URL and it plays. What separates it from a bare HTML5 audio tag is the range of formats and stream types it handles. The player supports MPEG audio and AAC audio streams, which covers the two codecs nearly every broadcaster uses. That matters because AAC streams are common on mobile-oriented setups, and a player that only handles MP3 will fail silently for a portion of the audience.
Metadata is the second pillar. The player pulls the StreamTitle field from Shoutcast 2, Icecast 2, Radionomy, Radiojar and Radio.co servers and displays the current song or show name on the player itself. For a radio site, this is the difference between a static “Listen Live” button and something that looks maintained. A listener who sees the actual track name is more likely to stay.
Presentation options are more generous than the price suggests. There are two interface layouts, one sized for narrow placements such as a sidebar widget and one for a full-width header or hero area. Both are responsive, so the same embed works on desktop, Android and iOS without a separate mobile build. The volume control uses a draggable slider, there is a mute toggle, and the player can display a cover image behind or beside the controls.
Seven audio visualizer effects are included. These are animated graphics that react to the audio signal, and while they are cosmetic, they serve a practical purpose: they give the player visual motion that confirms the stream is live even when the user has the volume low. The vendor also supports multiple instances on a single page, which is useful for directory-style sites listing several stations.
Browser coverage is broad by the standards of the category. The vendor lists Internet Explorer 11, Firefox, Safari, Opera, Chrome and Edge as compatible. Internet Explorer 11 support is unusual in new software and suggests the codebase targets maximum reach rather than modern-only APIs. The script depends on jQuery, which is worth noting because it means the library must be loaded on any page where the player appears.
Where This Fits and Where It Does Not
The clearest fit is a radio station’s own website. A broadcaster running an Icecast or Shoutcast server can drop this player into a WordPress page, a static site or a custom PHP build and get a working listen-live element with track metadata in an afternoon. The same applies to a musician or podcast producer who streams live shows on a schedule and wants a persistent player on their site.
It also suits aggregator and directory projects. Because multiple instances can coexist on one page, a site listing twenty stations can give each one its own player without conflicts. Community sites, church and campus radio pages, and niche genre portals are all natural homes for this kind of embed.
Freelancers and agencies have a specific reason to consider it. When a client asks for a radio player, the alternative is building one from scratch, which means handling stream buffering quirks, codec differences and metadata parsing per server type. Buying a $29 component that already solves those problems is usually the cheaper path, even after accounting for the time spent integrating it.
There is also a clear case against it. The vendor states that apps are not supported, so anyone building a native iOS or Android application should look elsewhere. The player is also the wrong choice for on-demand audio. It is built for live streams, and a site that mainly hosts archived episodes or a podcast feed would be better served by a standard podcast player. Finally, the JavaScript file ships obfuscated to prevent copying. That is a reasonable anti-piracy measure, but it means a developer cannot read or modify the player’s internal logic. Teams that need to customise behaviour at the code level, rather than through configuration, will find that constraint frustrating.
Strengths and Limitations
Strengths
- Handles both MPEG and AAC audio streams, so it works across the codec choices broadcasters actually make.
- Reads now-playing metadata from five major streaming platforms, including Shoutcast 2, Icecast 2 and Radio.co.
- Two responsive layouts cover both compact sidebar placements and full-width headers.
- Seven visualizer effects add motion and reinforce that a stream is live.
- Multiple players can run on one page, which suits station directories.
- Broad browser support, including Internet Explorer 11, extends reach to older hardware.
- Source files in JavaScript, HTML and PHP are included, so integration into an existing site is direct.
- Established track record: 2,413 sales and a 4.56 rating from 144 buyers.
Limitations
- The JavaScript is obfuscated. Customising the player’s internal behaviour is not possible without the vendor’s involvement.
- It requires jQuery, adding a dependency that some modern, lightweight builds deliberately avoid.
- Native mobile apps are explicitly unsupported. This is a web-only component.
- The server hosting the page must be permitted to reach the streaming server, either through a CORS policy or a PHP proxy. That is a server configuration task, not a checkbox, and it is the most common place integrations stall.
- The vendor does not publish a changelog in the listing, so the pace of ongoing maintenance is not visible from the product page alone.
- No on-demand or playlist playback. It is a live-stream tool and nothing more.
How It Compares to the Wider Category
Radio players for the web fall into three rough groups. The first is the free iframe or JavaScript snippet provided by the streaming host. These cost nothing and require no setup, but they are visually generic, rarely responsive, and usually carry the host’s branding. They also give the site owner almost no control over layout or metadata display.
The second group is full radio station platforms, which bundle a player with scheduling, statistics, DJ management and sometimes hosting. These are far more expensive and far heavier. A site that only needs a listen-live element ends up paying for and maintaining features it will never use.
The third group is standalone player components like this one. The trade-off is narrow scope in exchange for low cost and direct control. Compared with a host-provided embed, Luna Web Radio Player Plugin Media offers better layout control, metadata display across multiple server types, and visualizer effects. Compared with a full platform, it does far less but costs a fraction as much and does not lock the site into a hosting relationship.
The jQuery dependency and the obfuscated source are the two points where this product sits behind a hypothetical custom build. A developer writing their own player would control every line. Whether that matters depends entirely on how much customisation the project needs. For most station sites, configuration is enough.
Frequently Asked Questions
Does Luna Web Radio Player Plugin work with Shoutcast and Icecast?
Yes. The player reads now-playing metadata from Shoutcast 2, Icecast 2, Radionomy, Radiojar and Radio.co servers, and it plays both MPEG and AAC audio streams from them. That covers the large majority of self-hosted and commercial radio streaming setups in use today.
Can it be used inside a native mobile app?
No. The vendor states plainly that apps are not supported. This is a browser-based player intended for websites. Projects building native iOS or Android applications need a different solution, typically a platform-specific audio library rather than a web component.
Why does the player need CORS or a PHP proxy?
Browsers block a page from reading data on a different domain unless that domain explicitly allows it. Metadata sits on the streaming server, so the page either needs the stream server to send a permissive CORS header or needs a small PHP script on the same domain to fetch the data on its behalf.
Can several players run on the same page?
Yes, multiple instances are supported. This makes the plugin viable for station directories and genre portals where each listing needs its own player. Each instance is configured with its own stream URL and layout choice, so a page can mix compact sidebar players with wider header placements.
Verdict
Buy this if a site needs a self-hosted live radio player that displays track metadata, works across desktop and mobile browsers, and can be integrated without building the audio layer from scratch. It is a sensible purchase for radio stations, station directories, and agencies delivering a radio client project on a modest budget. Skip it if the project is a native mobile app, an on-demand podcast archive, or anything requiring deep modification of the player’s internal code, since the obfuscated JavaScript rules that out. The requirement to configure CORS or a PHP proxy on the server should also be factored in before purchase, because it is the step most likely to cause delay. At $29 with a 4.56 rating from 144 buyers, the risk is low for the right kind of project.
