> 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/product-limits.md).

# Product limits

Check the current volume, file, request, retention, report, sharing, and integration limits before you plan or operate a large workload.

Limits protect playback, data quality, provider relationships, and predictable cost. A limit can apply to a workspace, object, user, request, provider, or delivery surface. The application shows the effective value for the current scope when a limit can vary by plan, policy, or provider.

Do not assume that a limit for one surface applies to another surface. Do not work around a limit by creating duplicate Campaigns, Creatives, reports, or integrations.

## Limit ownership

| Limit owner       | What it controls                                          | Where to check                                          |
| ----------------- | --------------------------------------------------------- | ------------------------------------------------------- |
| Product contract  | Safe file, request, response, and media boundaries        | The field help, validation result, or API contract.     |
| Workspace policy  | Break, privacy, retention, sharing, and cost boundaries   | Monetization settings and the policy version.           |
| Commercial object | Campaign, Flight, Inventory, Creative, and report limits  | The object form, readiness view, or receipt.            |
| Provider          | Rate, concurrency, response, quota, and platform limits   | The integration capability and provider evidence.       |
| Delivery surface  | Media, player, HLS, RSS, Apple, Spotify, and event limits | The surface capability and compatibility matrix.        |
| User or role      | Access, share, and action limits                          | People and access, secure share, or the action receipt. |

## File and media limits

| Limit              | Current rule                                                                                      | Scope                                          |
| ------------------ | ------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
| Audio master size  | Up to 2 GB for MP3 or WAV                                                                         | One uploaded Creative master.                  |
| Video master size  | Up to 2 GB for MP4 or QuickTime                                                                   | One uploaded Creative master.                  |
| Prepared rendition | The exact codec, bitrate, sample rate, dimensions, duration, and captions required by the surface | One Creative version and destination.          |
| Break duration     | The maximum duration saved on the Break version                                                   | One episode break.                             |
| Ads in a break     | The slot count saved on the Break and publisher policy                                            | One break and its policy scope.                |
| Asset retention    | The current rights, replay, and evidence horizon                                                  | One Creative, representation, or presentation. |

![The One Podigee Upload creative master window shows the brand, rights grantor, language, markets, source file, and usage rights fields.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-3b2547b9e8314a4479e3a31bae96545c96a6a733%2Fdoc-monetization-043-upload-master.jpg?alt=media)

*The upload form applies the master-file boundary before media preparation starts.*

The current prepared audio and video profiles are in [Audio and video media specifications](/documentation/grow-and-monetize/monetization/concepts-and-reference/audio-and-video-media-specifications.md). A file can meet the master-file limit and still fail a codec, rights, caption, duration, or destination check.

## Campaign, Flight, and Inventory limits

Campaign and Inventory limits protect the object model and the delivery contract.

| Limit area               | What the system limits                                           | What to do                                                 |
| ------------------------ | ---------------------------------------------------------------- | ---------------------------------------------------------- |
| Targeting values         | Controlled market, language, category, media, and surface values | Select values from the governed list.                      |
| Flight window            | Start, end, time zone, and rights boundary                       | Keep the Flight inside the authorized period.              |
| Capacity reservation     | Available eligible supply and the reservation window             | Forecast before you reserve.                               |
| Pod capacity             | Slots, duration, partial fill, and fallback                      | Set the Break policy before you publish.                   |
| Frequency and separation | Exposure, adjacency, and identity-tier pressure                  | Use the configured identity and policy boundary.           |
| Creative coverage        | Compatible Creative versions and markets                         | Prepare the missing rendition or coverage.                 |
| Inventory package        | Shows, episodes, breaks, formats, and markets                    | Add approved supply instead of creating free-text filters. |

The application prevents a value outside the declared limit. The readiness and forecast views show the reason when a limit reduces eligible supply.

## Request and provider limits

Request-time limits protect the listener or viewer from delay and protect providers from uncontrolled traffic.

| Limit                     | Applies to                                 | Failure behavior                                              |
| ------------------------- | ------------------------------------------ | ------------------------------------------------------------- |
| Request body size         | API or provider request                    | Reject the request with a stable validation reason.           |
| Rate limit                | API client, workspace, or provider         | Return a rate result and follow the retry boundary.           |
| Concurrent requests       | Integration, provider, or delivery surface | Queue or reject according to the capability profile.          |
| Response timeout          | Demand provider or platform request        | Continue to the next source or safe fallback.                 |
| Wrapper or redirect depth | VAST or provider response                  | Reject the response when the configured depth is exceeded.    |
| Response size             | Provider response or asset list            | Reject or quarantine an oversized response.                   |
| Retry count               | Provider, webhook, or report delivery      | Stop at the profile limit and create a visible failure.       |
| Circuit threshold         | Provider, cost, or integration health      | Pause the named dependency and keep clean playback available. |

Provider limits can change without a Podigee product release. Read the active capability and provider evidence before increasing request volume or concurrency.

## Report, export, and share limits

Reports can be large and can contain commercial or personal data. The system limits their scope, format, retention, and sharing behavior.

| Limit                  | Current behavior                                                                | Scope                         |
| ---------------------- | ------------------------------------------------------------------------------- | ----------------------------- |
| Report scope           | A report must use an allowed workspace, Campaign, Flight, surface, and period   | One report definition.        |
| Report output          | The format and column set must be supported by the destination                  | One report run.               |
| Report retention       | The report profile or workspace policy defines how long a run remains available | One report run.               |
| Secure share downloads | Choose 1, 3, or 10 downloads                                                    | One secure share.             |
| Secure share expiry    | Choose the shortest time that supports the purpose                              | One secure share.             |
| Export access          | A share or export is limited to the recipient and permission scope              | One recipient and report run. |

![The current One Podigee Evidence and Money view shows this month's qualified delivery, fill rate, qualified revenue, no-fill decisions, a daily chart, and the media and money breakdown.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-ab157f76d1c3f5f7be3a2d369de4c2995b42dd3b%2Fdoc-monetization-072-reports-overview.png?alt=media)

*Report access and sharing limits protect the evidence as well as the numbers.*

When a share reaches its download count or expiry, create a new share with a new purpose and recipient. Do not extend an old share only to avoid recording the new access decision.

## Retention and deletion limits

Retention is a policy value, not a single product-wide number. The effective retention can be different for request-time identity, delivery events, report output, commercial records, audit receipts, security cases, and financial documents.

The retention rule follows this order:

1. Legal hold.
2. Statutory retention.
3. Active dispute or reconciliation.
4. Certified replay horizon.
5. Contractual retention.
6. Customer deletion request.
7. Ordinary lifecycle.

A lower-priority deletion request cannot remove evidence required by a higher-priority rule. The system can redact direct identifiers while preserving non-identifying digests, lineage, and required financial or audit facts.

## Integration limits

| Integration    | Limit or boundary                                                           | What it means                                                                |
| -------------- | --------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| Apple Podcasts | HLS, association, asset, replay, and platform contract limits               | Host-side checks do not replace Apple certification.                         |
| Spotify        | API version, asynchronous processing, capability grant, and provider quotas | Podigee submits the approved intent; Spotify controls destination execution. |
| VAST           | Wrapper, redirect, response, media, and tracking limits                     | A valid XML response can still fail media or policy checks.                  |
| OpenRTB        | Request, bid, price, currency, timeout, and privacy limits                  | A bid is not a fill or a qualified impression.                               |
| CATS           | Profile, signed message, operation, endpoint, and timeout limits            | A transport result must pass the certified message contract.                 |
| Owned player   | Request, media, interstitial, event, and fallback contract                  | A health check does not prove real playback.                                 |
| Webhook        | Signature, body, clock, retry, and event retention profile                  | At-least-once delivery requires idempotent consumers.                        |

If a provider or platform contract does not define a required limit, keep the capability blocked or limited. Do not invent a production limit from a local test.

## Check a limit before a large operation

1. Open the exact workspace, Campaign, Flight, Creative, report, or integration.
2. Read the field help, readiness state, and policy version.
3. Check the effective limit for the selected scope and destination.
4. Check the current provider or platform capability when an external system is involved.
5. Forecast the volume, media, request, cost, and retention effect.
6. Use the smallest workload that proves the intended change.
7. Record the operation and receipt.

If the form blocks a value, read the displayed reason. Do not paste a new value into another field or create a duplicate object as a workaround.

## What to do when a limit is reached

| Situation                     | Safe response                                                      |
| ----------------------------- | ------------------------------------------------------------------ |
| File limit reached            | Prepare a valid source or use the approved upload path.            |
| Capacity limit reached        | Change the scope, timing, or reservation with an approved version. |
| Request limit reached         | Reduce load, follow the provider profile, or use a safe fallback.  |
| Report or share limit reached | Narrow the report or create a new purpose-bound share.             |
| Retention limit reached       | Follow the retention and legal-hold workflow.                      |
| Integration limit reached     | Read the provider result and wait or repair the capability.        |
| Unknown limit                 | Keep the operation blocked and request an authority update.        |

## Expected result

You know which limit applies, who owns it, what scope it covers, and what safe behavior occurs at the boundary. Large workloads remain predictable, playback remains available, and a limit never creates hidden data loss, false billing, or an unsafe provider request.


---

# 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/product-limits.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.