Creative Guidelines
Modified on Wed, 4 Nov at 6:15 AM
GROW YOUR APP WITH EASE
bidease
Creative Guidelines
Explore the creative formats available with Bidease and discover how your brand can appear across different ad experiences.
Video
Video creatives served across Fullscreen and MREC* placements, followed by a static or interactive end card with a CTA.

ASSETS WE NEED
Fullscreen 9:16
1080×1920
Fullscreen 16:9
1920×1080
MREC
600×600
Duration
15s+
Max file size
1.5 GB
BEST PRACTICES
•
Capture attention in the first 5 seconds
•
Ensure the message is clear with the sound off and the CTA is legible on the end card
•
Keep styling cohesive between the video and the end card
•
Create AI-generated video creatives with our support
* MREC (Medium Rectangle) is a display ad format typically measuring 300 × 250 / 300 × 300 pixels. On high-density displays (Retina/HiDPI), higher-resolution assets may be required to maintain visual sharpness.
Playable Ads
Interactive creatives built around a simple game mechanic, followed by a CTA end card.

ASSETS WE NEED
Creative format
HTML5
Standard
MRAID 2.0*
Layout
Responsive for
Fullscreen 9:16 / 16:9
Fullscreen 9:16 / 16:9
Recommended file size
<1 MB
BEST PRACTICES
•
Send us your existing playable ad, and we’ll adapt it to run on the Bidease platform while keeping all visual elements unchanged
•
If you need assistance with playable ad creation, share your creative assets, brand guidelines in PDF format, and vector logo in SVG or AI format. We’ll create a playable ad at no additional cost
* MRAID (Mobile Rich Media Ad Interface Definitions) is a standard API that enables rich media ads to interact with mobile apps.
Static
Image-based creatives for Banner, MREC, and Fullscreen placements, widely supported but typically less engaging than video or interactive creatives.

ASSETS WE NEED
Static Portrait 9:16
1080×1920
Static Landscape 16:9
1920×1080
Banner
640×100
MREC
600×600
Max file size
10 MB
File formats
JPG / PNG / GIF
Minimums: Banner 320×50
BEST PRACTICES
•
Keep the key message short, visible from the start, and within safe margins
•
Ensure creatives stay clear and readable at smaller sizes
Native
Native creatives assembled from image and copy to match the surrounding app experience.

ASSETS WE NEED
Title
up to 25 characters
Description
up to 120 characters
CTA
up to 15 characters
Localized copy
by target market
BEST PRACTICES
•
Match visual elements to the surrounding organic content
•
Use copy that feels personalized and avoids clickbait
•
Keep the message clear and concise with a strong CTA
CTV
Full-screen, cinematic video creatives designed for the TV experience, running before content (pre-roll) or during natural content breaks (mid-roll).

ASSETS WE NEED
Format
Standard VAST*, no end cards
Placement
Linear pre-roll / mid-roll
Resolution
Min 1920×1080; 4K preferred
Aspect ratio
Strictly 16:9
Max file size
2 GB
Duration
15s+
BEST PRACTICES
•
Use high-resolution assets for large-screen viewing
•
Make it feel cinematic, not simply adapted from mobile
•
Keep branding clear and easy to recognize
* VAST (Video Ad Serving Template) is an XML-based standard used to deliver video ads and related metadata to video players.
Dynamic Product Ads
Personalized creatives dynamically assembled from a product feed based on user behavior.

ASSETS WE NEED
Product feed
CSV, JSON, or XML
Product ID
required
Image URL
required
Deeplink
required
BEST PRACTICES
•
Direct deeplinks to the relevant product page
•
Update stock status to exclude unavailable products
•
Match Product IDs between the feed and tracking
Leave creative
production to Bidease
production to Bidease
From concept to ready-to-launch assets, we can support the full production process:
Contact Our Creative Team →•
Make new creatives from scratch
•
Adapt existing assets for campaign requirements
•
Produce launch-ready creatives within one week
✓At no additional production cost
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article