Unity Ads Playable End Card: Size Limits & Best Practices

Unity Ads supports playable ads and interactive end cards as single HTML files. Hitting their size and format rules is key for approval and performance. Here’s what you need for Unity Ads playable end cards.

Unity Ads Playable End Card Specs

Unity Ads supports playable end cards up to 5 MB per HTML file (all ad networks support a 5 MB cap). Use a single, self-contained HTML file with all assets (images, CSS, JS) embedded—no external requests. Unity’s SDK is added by the network; you only provide the creative.

Best Practices for Unity Playable End Cards

• Smaller files load faster; use image compression when needed (all networks support up to 5 MB).
• Use one clear CTA button with correct iOS/Android app store URLs.
• Test on real devices; avoid heavy animations that hurt load time.
• Use a playable end card maker that exports Unity-ready HTML with tracking.

Lighter creatives load faster, which can improve viewability and completion rates. Use WebP or well-compressed JPG/PNG for images, and avoid unnecessary large assets. Use the tool's compression feature or reduce image resolution if you want faster loads; all networks support up to 5 MB.

CTA and App Store Links

Your end card should include a single primary CTA (e.g. Install, Play Now). The creative must detect the user's device and open the correct store—iOS App Store or Google Play. A no-code playable end card maker typically handles this when you provide both URLs at export time.

How to Build Unity Playable End Cards Without Code

Use a tool that supports Unity Ads export. Design your end card (background, text, CTA button), set iOS and Android URLs, and export the Unity option. You will get one HTML file to upload in the Unity Ads dashboard. No coding or manual HTML editing required.

Unity Ads Dashboard and Submission

After exporting your creative, log in to the Unity Ads dashboard and navigate to your app or campaign. Create or edit a playable or interactive end card placement and upload the HTML file. Unity may run automated checks; if the file is within size and format rules, it should be accepted. If you get a rejection, check the error message and fix the issue (often file size or invalid links) before resubmitting.

Unity supports A/B testing of creatives, so you can run multiple end card variants to see which performs best. Use clear naming in the dashboard so you can tell creatives apart when analyzing results. Over time, you can refine your end cards based on install rate and engagement data.

Troubleshooting Unity Playable End Card Issues

If your creative fails to load or the CTA does not work, verify that all assets are embedded (no broken image or script references) and that the HTML runs correctly in a mobile browser. Test on both iOS and Android. For faster loading, use your tool compression or reduce the number and resolution of images; all ad networks support up to 5 MB per file.