Player Embed Codes | Style

Our Web Player can be embedded in three ways – depending on your level of flexibility, security, and design needs:


1. Standard (Script Embed Code)

This is the recommended method to embed the player.

<script class="podigee-podcast-player" src="https://..." data-configuration="https://....podigee.io/embed?context=external"></script>

❗️ The script embed must be placed inside the <body> of your website. Placing it in the <head> is not supported.

Advantages:

  • Easy setup with just one line of code.
  • Full functionality with automatic updates.
  • Supports interactive features like playlists, search, and login.

💡 Alternative if the standard embed doesn’t work: In rare cases (e.g. when using certain CMS or page builders), you can use this simplified fallback version ⬇️


2. Restricted Embed Code (iFrame)

This version uses an iFrame – suitable for environments where scripts are not allowed.

<iframe src="https://....podigee.io/embed?context=external..."></iframe>

Advantages:

  • Works in limited systems (e.g. CMS, shop platforms).
  • Only the default theme can be used.
  • Extensions with collapsible panels (e.g. extra info sections) won’t work.
  • Secure and isolated from your site’s code.

Limitations:

  • Reduced interactivity.
  • No user login or dynamic customization.

3. External Theme (Custom Design)

This feature is available starting from the Business Pro plan. It allows full customization of the player using self-hosted HTML and CSS files. You will receive a GitHub link to our SDK Player repository. Please contact our support to request access.

Requirements:

  • Own server or hosting space.
  • Knowledge of HTML and CSS.

Steps:

  1. Create a custom HTML layout and matching CSS file.
  2. Upload both to your server.
  3. Enter the file URLs in the interface under “External Theme”.

Advantages:

  • Full customization (colors, layout, fonts).
  • Perfect for branded solutions and developer setups.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.