Mintegral playable asset rules: package, upload path and what stays in the test tool

Mintegral’s AppGrowth help centre documents a playable as an HTML package with a hard size ceiling, companion image assets, and a mandatory pass through its Playable Test Guide before delivery. Announcement and per-rule enforcement effective dates are not stated on the cited pages and remain unknown.

What the documentation currently requires

Creative Asset Specifications (last modified 10 September 2026) lists Playable as:

• HTML (single file) with no fixed pixel size, required to render in portrait or landscape.
• Maximum size 5 MB.
• Used for Playable Interstitial and Rewarded Video.
• Notes: upload a main image and app icon alongside the playable file, and see the Playable Test Guide before submitting.

The same table requires 512×512 app icon and 1200×627 or 1200×628 main image (each max 5 MB) for formats that include playable.

Creative Step-by-Step Guide (last modified 12 September 2025) states playable upload format supports URL and ZIP, and playable form supports playable and dynamic endcard. Part 7 instructs operators to load the playable in the test tool, play through the entire experience until the end so methods are exercised, and obtain Test Success before treating the asset as ready.

Playable Test Guide (last modified 14 August 2025) points producers to the external Mindworks/Playturbo testing document and validator rather than restating low-level CTA or embedding APIs on the Mintegral page itself.

What is recommendation or unresolved here

This record does not invent a shared cross-network playable spec. Exact store-open JavaScript call signatures, base64-embedding rules and method checklist labels live in the linked Mindworks testing surface; they are not restated as hard gates on the Mintegral asset-specs page. Account-level approval timing (FAQ text elsewhere mentions longer review for interactive creatives) is not treated as a package rule in this edition.

Who should act, and how

Studio playable producers and UA buyers submitting to Mintegral AppGrowth should:

1. Keep the playable HTML (or ZIP that yields a locally openable HTML) under 5 MB.
2. Ship the required icon and main image with the playable.
3. Confirm the build is intended for playable interstitial / rewarded paths, or as a dynamic endcard, as configured in the creative set.
4. Run the Playable Test Guide end-to-end and retain a Test Success result before relying on upload alone.

Our editorial inference—not a Mintegral claim—is that packages built for MRAID networks with external asset fetches are high-risk reuse candidates until they pass Mintegral’s own validator.

Applicability table

Download the applicability table.

Limits of this record

This edition body-reads Mintegral Help Center articles. It does not inspect a live advertiser account, certify a specific ZIP, or reproduce the full Mindworks method matrix. Announcement and effective dates stay unknown until Mintegral publishes them.

Research checked 19 September 2026. Local draft; human editorial review and byline assignment pending.