The Podigee Podcast Player
You can configure your web player directly in the podcast settings under the “Web Player” tab. Depending on your selected plan, different customization options are available – for example, adjusting the color(s) or other design elements like white-label branding.
The configuration applies to both the podcast player (for all episodes) and the episode player (for individual episodes).
Embedding on External Websites
You can flexibly embed the web player on external websites – either for the entire podcast (optionally with a playlist of all episodes) or for individual episodes.
Here’s how to find the appropriate embed code:
- For the entire podcast:
You’ll find the embed code in the podcast settings under the “Web Player” tab. - For a single episode:
Open the desired episode and go to “Media File”. The embed code for that specific episode will be shown there.
Privacy and GDPR Compliance
The Podigee player is 100% GDPR-compliant. All integrated social media buttons (e.g., “Share”) operate exclusively via static links.
This means:
- No cookies are set.
- No communication with third-party services occurs unless there is active interaction by the listener.
If you prefer not to use the sharing function, you can completely disable it. Go to the “Web Player” tab and choose:
On the website (Podigee blog) and/or Embedded → Share
You can disable the share button separately for both contexts.
Privacy Notice for External Websites:
If you embed the Podigee player on your own website, you can (and should) include a notice in your privacy policy mentioning the use of the player.
A sample privacy policy text is available here:
👉 To the sample privacy policy
You can find this section on the Podigee blog under: “Blog” → “Datenschutzerklärung”
Known Issues / Compatibility
Our player works reliably on most websites – with a few important exceptions and technical recommendations:
- WordPress.com
→ The cloud version of WordPress blocks external scripts such as our player.
✅ Self-hosted WordPress installations work without any issues. - Wix.com
→ Please use the restricted embed code, as the standard integration may not work correctly.
- Maximum number per page:
We recommend embedding no more than 25 web players on a single HTML page.
Background: For security reasons, browsers limit the number of concurrent requests per second. With more than 25 players, this limit may be exceeded, causing some players not to load properly. - Script blockers and local display issues:
If you’re using a script blocker (e.g., uBlock, NoScript), the player might not display.
➤ Solution: Add the following domains to your blocker’s allowlist:*.podigee.io*.podigee.com
This ensures the player can load properly.
If You Use Your Own Podcast Player
If you use your own web player to deliver a podcast hosted by Podigee, certain technical requirements must be met. These ensure fair usage of our infrastructure and a good listening experience – without unnecessary server load or data protection concerns.
⚠️ Please keep in mind the following points:
- The player should not support autoplay.
→ Playback must only start when users actively click “Play”. - Do not preload audio data automatically.
→ Only load the audio file after the listener clearly indicates they want to listen. - Use the audio URL exactly as provided.
→ Do not add additional parameters to the URL. Modifications could interfere with analytics or delivery. - Do not cache or mirror audio files on your own servers.
→ All requests must go directly to our servers to ensure accurate analytics and update delivery. - If you offer full downloads, the entire file must be fetched in a single request.
→ For progressive streaming (e.g., allowing users to skip ahead), the file must be loaded using byte ranges. - Use the GUID to identify new episodes in the RSS feed.
→ Titles, publish dates, and URLs can change – the GUID is the only permanent and unique identifier for an episode. - Limit automatic downloads, e.g., by stopping after 5 unplayed episodes.
→ This protects server resources and avoids unnecessary storage use on listener devices. - Do not download all episodes by default (e.g., from the full archive).
→ Bulk downloads place unnecessary load on servers and networks. - Use the following pattern for your User Agent string:
→ <app name>/<app version> <device info> <os name>/<os version> <other info>
e.g., AppName/1.2.3 DeviceBrand DeviceModel OSName/1.2.3 LibName/1.2.3 - If you load metadata like the episode title or cover, load only the header information found at the beginning of the file to avoid downloading the entire audio unnecessarily.
These recommendations are important to ensure scalable, fair, and privacy-compliant use of our hosting services.