> 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/understand-media-checks-and-prepared-renditions.md).

# Understand media checks and prepared renditions

Understand the security, source, format, and delivery checks that prepare an audio or video Creative for supported destinations.

The Podigee Audio Video Ad Server checks each uploaded master before it can become a delivery format. These checks protect the listener, the publisher, and the buyer from unsafe or incorrect media.

A **prepared rendition** is a checked file that Podigee creates from the master for a specific delivery use. The master and the rendition are different files with connected evidence.

## How preparation works

Podigee uses this sequence:

1. Store the uploaded master.
2. Confirm that the recorded usage rights cover the media.
3. Scan the master for malware.
4. Inspect the media streams and file metadata.
5. Confirm that the actual media type matches the declared type.
6. Create the required delivery format.
7. Inspect the created format.
8. Store the rendition and its preparation result.

Podigee stops the sequence when a required check fails. A failed version does not become ready for delivery.

## Read the Media checks card

Open **Monetization**, select **Creatives**, and open a Creative. The **Media checks** card shows the current security and format state.

![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)

*Use Media checks to confirm that the master is clean and at least one rendition is ready.*

The card contains these items:

| Item                      | Meaning                                                               |
| ------------------------- | --------------------------------------------------------------------- |
| **Security scan**         | The malware scanner returned a clean result for the exact source.     |
| **Format preparation**    | Podigee completed the media preparation sequence.                     |
| **Security scan receipt** | A short reference connects the visible result to its stored evidence. |
| **Renditions**            | The number of prepared delivery formats for this Creative version.    |

The short receipt reference is useful for support or audit work. You do not need to read its full technical value during normal ad operations.

## Source checks

Podigee checks that the source can be read and contains the expected streams.

For an audio master, the source must contain audio and must not contain a video stream. For a video master, the source must contain both video and audio.

The source duration must be from 1 second through 10 minutes. Podigee rejects media when required stream metadata or duration is missing.

## Prepared audio format

The current progressive audio rendition uses these main properties:

| Property    | Prepared value             |
| ----------- | -------------------------- |
| File format | MP3                        |
| Bitrate     | 128 kbps, constant bitrate |
| Sample rate | 44.1 kHz                   |
| Channels    | Stereo                     |

Podigee checks the prepared file against this profile. A small bitrate tolerance allows normal encoder behavior.

## Prepared video format

The current video preparation profile uses these main properties:

| 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               |

This rendition is a checked input for supported video delivery. The destination flow can create additional HLS variants and apply more platform checks.

## Read the Delivery formats table

The **Delivery formats** table shows each rendition that belongs to the exact Creative version.

![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)

*Confirm the delivery use and quality result before you assign the Creative.*

Read these columns:

| Column            | What to check                                                                    |
| ----------------- | -------------------------------------------------------------------------------- |
| **Delivery use**  | The rendition can serve the required media path.                                 |
| **File format**   | The prepared container matches the expected use.                                 |
| **Preparation**   | Processing completed successfully.                                               |
| **Quality check** | The rendition passed its profile validation.                                     |
| **Duration**      | The prepared file has the expected length.                                       |
| **Bitrate**       | The audio or video rate matches the prepared profile.                            |
| **Dimensions**    | The video size matches the required profile. This value does not apply to audio. |

**Ready** in both result columns means that the rendition passed the current technical profile. It does not approve the Creative for editorial use.

## Understand destination readiness

One ready rendition does not mean that every destination is ready. Check the selected destination and the Creative coverage.

| Destination                  | Media readiness rule                                                                                                         |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| RSS podcast audio            | Requires a ready progressive audio rendition and valid audio rights.                                                         |
| Podigee HLS video            | Requires ready video media and a valid HLS delivery package.                                                                 |
| Apple Podcasts video         | Requires valid HLS media plus the Apple-specific package and publication checks.                                             |
| Spotify delivery             | Requires accepted media and configuration through the Spotify connection. Spotify controls final streaming and ad execution. |
| Other connected destinations | Requires the formats and checks declared by that connection.                                                                 |

Do not treat a green Creative state as proof that an external platform accepted the media. Open the destination or publication state when the platform controls final acceptance.

## Checks that need a separate review

The current Media checks card does not show separate results for loudness, silence, clipping, or captions. Do not assume that **Ready** is a pass for each of these items.

Use the Creative preview to check audible or visible defects. Check captions and destination rules when they apply. Complete the editorial review before assignment when your policy requires it.

## Understand preparation states

| State          | Meaning                                                                   | Operator action                                                     |
| -------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| **Queued**     | The upload waits for preparation.                                         | Wait, then refresh the Creative.                                    |
| **Scanning**   | Podigee scans the source.                                                 | Keep the version out of delivery.                                   |
| **Processing** | Podigee creates and checks the rendition.                                 | Keep the version out of delivery.                                   |
| **Ready**      | The required rendition passed the current checks.                         | Preview it and complete the required review.                        |
| **Failed**     | A named security, source, rights, processing, or validation check failed. | Resolve the named problem, then retry when the action is available. |

Malware detection is a hard stop. Do not retry the same unsafe file.

## Solve common problems

| Problem                                              | Cause                                                                         | Safe action                                                              |
| ---------------------------------------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Security scan stays unavailable                      | The approved scanner cannot complete the check.                               | Keep the Creative out of delivery and retry when the scanner is healthy. |
| Source is invalid                                    | The media cannot be read or its streams do not match the declared type.       | Check the source file and upload the correct master as a new version.    |
| Rights are invalid                                   | The version has no usable grant for its media and surfaces.                   | Correct the rights record before preparation.                            |
| Processing fails                                     | Podigee cannot create the required rendition.                                 | Open the named failure and use a supported source file.                  |
| Validation fails                                     | The output does not match its delivery profile.                               | Retry preparation after the source or processor problem is corrected.    |
| The Creative is ready but the destination is blocked | The destination needs another format, package, right, or platform acceptance. | Open Creative coverage and the destination state. Resolve the named gap. |
| Duration or media type is wrong                      | The wrong source file was uploaded.                                           | Upload the authorized file as a new version.                             |

Do not change the meaning of an earlier version after it has delivery evidence. Use a new Creative version for a corrected source.

## Result

You can explain which master was checked, which rendition is ready, and which delivery use it supports. You also know which checks remain in the editorial or destination flow.

Next, confirm Creative rights, disclosures, and suitability.


---

# 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/understand-media-checks-and-prepared-renditions.md?ask=<question>&goal=<endgoal>
```

`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.