> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/concepts-and-reference/audio-and-video-media-specifications.md). # Audio and video media specifications Check supported audio and video masters, prepared renditions, duration, codecs, captions, and destination limits before delivery. Use this reference when you upload, review, or repair a Creative or episode media file. Podigee checks the source and creates prepared renditions for supported delivery paths. A file can be playable in a local player and still fail a delivery profile. ![The current One Podigee Creative page shows a clean security scan, ready format preparation, one rendition, the master asset, and Creative coverage.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-1163f404bbc5126ba88f9402f165480b0f51469d%2Fdoc-monetization-045-media-checks.jpg?alt=media) *Media checks show the source, preparation, rendition, and coverage state.* ## Accepted source types Use a source file that the upload form accepts for the selected media kind. Declare the correct kind before upload: | Media kind | Source must contain | Source must not contain | | ---------- | ----------------------------------------------- | ---------------------------------- | | **Audio** | One readable audio stream. | A video stream. | | **Video** | One readable video stream and one audio stream. | Missing audio or unreadable video. | The source duration must be at least 1 second and no more than 10 minutes for a Creative. Podigee rejects a source when it cannot read the required stream or duration. ## Prepared audio rendition The current progressive audio profile uses: | Property | Prepared value | | ----------- | ------------------------- | | Container | MP3 | | Bitrate | 128 kbps constant bitrate | | Sample rate | 44.1 kHz | | Channels | Stereo | Podigee checks the prepared file against the active profile. A small bitrate tolerance allows normal encoder behavior. ## Prepared video rendition The current video profile uses: | Property | Prepared value | | ----------------- | -------------------- | | Video codec | H.264 | | Audio codec | AAC | | Image size | 1280 by 720 pixels | | Frame rate | 30 frames per second | | Audio bitrate | 128 kbps | | Audio sample rate | 48 kHz | | Audio channels | Stereo | The destination can create more HLS variants. Check the destination article when Apple, HLS, or a connected platform needs an encoding ladder, captions, or I-frame media. ## Duration and timeline rules The prepared duration must match the source use. For an ad Creative, keep the intended duration within the Campaign and break limits. For an episode, check the source duration, chapters, and ad break positions together. An inserted ad changes the heard or viewed timeline. Podigee creates a presentation-specific timeline when the delivery profile requires it. Do not move a chapter by editing a Creative file. ## Loudness and quality checks The current Media checks card confirms security, source, preparation, and profile validation. It does not by itself certify every loudness, silence, clipping, caption, or editorial suitability requirement. Use the Creative preview and the destination requirements to check: * audible clipping, silence, or unwanted noise; * visible black frames, frozen frames, or missing pictures; * loudness and true-peak rules required by the destination; * captions, subtitles, and language tracks; * companion video or image assets; * brand, disclosure, and suitability rules. If the product shows no separate result for a quality item, do not report that item as certified. Complete the required editorial or destination review. ## Captions and companion assets Captions and companion assets belong to the destination profile. Check their language, timing, format, MIME type, and association with the exact media version. For Apple Podcasts video, prepare the required audio-only, video, I-frame, caption, and interstitial resources and run the Apple validator. For Podigee HLS, check the current HLS ladder and caption behavior. For Spotify, check the media requirements in the Spotify connection because Spotify controls final processing. ## Read the delivery format table ![The current One Podigee Creative page shows the ready MP3 delivery format with its preparation state, quality state, duration, and bitrate.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-7daa5c642f8412a3c9d12a22fd78bfd0e923204d%2Fdoc-monetization-046-usage-rights.jpg?alt=media) *The Delivery formats table shows the exact rendition that can be assigned.* Check these columns: | Column | Meaning | | ----------------- | ------------------------------------------------------ | | **Delivery use** | The delivery path for which the rendition is prepared. | | **File format** | The container used by the rendition. | | **Preparation** | The preparation operation completed. | | **Quality check** | The rendition passed the active profile validation. | | **Duration** | The prepared duration. | | **Bitrate** | The prepared audio or video rate. | | **Dimensions** | The video image size, when applicable. | **Ready** means that the current technical profile passed. It does not approve the Creative for editorial use or prove that an external platform accepted it. ## Destination limits | Destination | Extra requirement | | ------------------------ | ---------------------------------------------------------------------------- | | **RSS audio** | Ready progressive audio rendition and valid audio rights. | | **Podigee HLS** | Compatible video and audio media, HLS playlists, and timeline resources. | | **Apple Podcasts video** | Apple HLS ladder, captions, CORS, interstitial, and validator evidence. | | **Spotify** | Accepted submitted media and capability-specific Spotify processing. | | **VAST or OpenRTB** | Provider response media and tracking must pass the connector contract. | | **Owned player** | The player profile must support the selected media and measurement contract. | ## Common rejection reasons | Reason | Repair | | ---------------------------------- | ------------------------------------------------------------------- | | Wrong declared media kind | Upload a new version with the correct declaration and source. | | Missing required stream | Create a valid source with the required audio or video stream. | | Unsupported container or codec | Export the source with a supported profile. | | Duration outside the limit | Trim or replace the source, then create a new version. | | Security scan failed | Do not retry the unsafe file. Follow the security incident process. | | Rendition preparation failed | Read the named media error and upload a corrected source. | | Rights or destination blocked | Correct the right or destination package before assignment. | | Caption or companion asset missing | Add the destination resource and run its validation. | Do not edit a historical master or rendition to change its evidence. Upload a new version. ## Check a new upload 1. Confirm the media kind and source file. 2. Upload the master. 3. Wait for the security scan and preparation state. 4. Open **Media checks** and **Delivery formats**. 5. Preview the exact rendition. 6. Check rights, disclosures, suitability, and coverage. 7. Assign it only to a Flight whose media and destination match. ## Expected result The source is readable, safe, and declared correctly. The prepared rendition matches the current profile, the destination has its extra resources, and the operator knows which checks remain before the Creative or episode can be used in live delivery. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podigee.com/documentation/grow-and-monetize/monetization/concepts-and-reference/audio-and-video-media-specifications.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.