You can put your VosCast station on a WordPress page using the block editor's Custom HTML block. On a self-hosted WordPress site that permits this HTML, you do not need a radio player plugin. Visitors start listening with the browser's Play button.
Get your listener URL
Find the direct listener stream URL in your VosCast account. Open it in a separate browser tab, press Play if prompted, and confirm that you hear your station. A station homepage, server status page or account page is not the audio stream address.
Use a working HTTPS listener URL for an HTTPS website. Copy the actual HTTPS address and port provided for listening; changing http to https on another port does not enable secure streaming. Ask support if you need help finding the correct address.
The example below is for an MP3 broadcast. Your stream must actually be MP3: adding audio/mpeg to the HTML does not convert another audio format. Our HTML5 radio player guide explains the player and stream requirements in more detail.
Add a Custom HTML block
- Open the page or post in the WordPress block editor using an account that can edit it.
- Select + to add a block, search for Custom HTML, and select it. You can also type
/htmlin an empty paragraph. - In WordPress 7.0, select Edit HTML to open the editing dialog. Paste the example into the HTML panel, then select Update to apply it. Older editors show the HTML editing area directly inside the block; paste it there and use Preview if offered.
- Replace both example URLs with your real HTTPS listener URL.
<audio controls preload="none" aria-label="Live radio stream">
<source src="https://stream.example.invalid:8443/stream" type="audio/mpeg">
</audio>
<p><a href="https://stream.example.invalid:8443/stream">Listen to the live stream</a></p>
The .invalid address is a placeholder and will not play. Use only the public listening address; do not put your Broadcast password, admin password or VosCast account credentials in the block.
The separate link gives listeners another way to open the stream. Keep it below the player. There is no autoplay setting in this example: visitors press Play. preload="none" asks the browser to wait before loading audio, although browsers treat this as a hint.
Save and test the page
- Preview your changes, then Publish or Update the page if your WordPress role allows it. If your role requires editorial approval, submit it through your site's normal process.
- Open the saved page as an ordinary visitor, signed out of WordPress, and press Play. Confirm the correct station is audible.
- Check Pause and the separate listening link. Test the published page on a computer and on the phones your audience uses; see listening on a mobile device.
- Reopen the editor and confirm that the audio HTML survived saving. An editor preview alone does not confirm what visitors receive.
WordPress.com and restricted sites
WordPress.com has its own custom HTML rules. Available code depends on the plan and activated hosting features. Self-hosted sites can also filter saved HTML according to user permissions or site configuration. Do not assume that having a Custom HTML block means every HTML element will be retained.
If the player code disappears after saving, ask the site's administrator to check the permitted HTML and your editing permissions. On WordPress.com, check the current plan and code rules with its support team before changing plans. A separate player plugin is not required for the basic self-hosted method above.
Using an Audio block instead
The built-in Audio block offers Insert from URL. You can try your direct HTTPS stream URL there, with Autoplay and Loop off and Preload set to None if those controls are available. Add a separate listening link in a paragraph below it.
WordPress documents this block primarily for audio files. Confirm that your saved page plays the ongoing live stream; uploading a recording or selecting one from the Media Library plays that file, not your live station.
If the player is silent
Check the direct listener link first. If it works but the page player does not, compare the saved URL with the original and check that the stream format is supported by the listener's browser. Use a valid HTTPS listener certificate. Your site's security policy or an HTML filter may also block the embed; ask the site administrator to investigate.