Meta information

Meta title: Creative Automation Tools for Display Advertising: HTML5 Ad Production & Programmatic Platform Comparison
Meta description: Compare creative automation tools for display advertising and HTML5 ad production across DV360, Amazon DSP, The Trade Desk, Microsoft/Xandr, and Adform. See specs, workflows, and how Viewst streamlines banner production.

As of: August 2026. Specs and policies change frequently. Always confirm details in live platform documentation before launching campaigns.

Programmatic display platforms may look similar from a media-buying perspective, but they feel very different in production.

This guide compares programmatic display platforms for creative automation tools, HTML5 ad production, and DCO integration so creative leaders can design processes that actually match channel reality.

We’ll focus on what Heads of Creative, Design Directors, and Creative Ops leads care about:

• Concrete HTML5 specs and file-size limits

• Programmatic display ad formats and rich media constraints

• How each DSP/ad server affects workflows, QA, and automation

• Where specialized tools like Viewst sit in the stack to remove production pain

For a deeper architectural view, see the pillar guide: “Display Ad Platform Support: How Creative Teams Align with Programmatic Advertising.”

At a glance: creative automation platforms for display advertising tools features comparison

This table compares the major programmatic advertising companies and display ad platforms from a creative production standpoint (not media buying).

| Platform | Primary role | Key HTML5 / display specs* | Workflow / automation fit | Best for |

| --- | --- | --- | --- | --- |

| Google DV360 + CM360 | DSP + ad server | DV360: up to 5 MB total download, 100 HTTP calls, 25 cookies, 30s animation, ZIP upload only.[^dv360-spec] CM360: up to 100 files, 9.5 MB ZIP/ADZ, polite image under 40 KB.[^cm360-spec] | Split workflow: rich media via Studio → CM360 → DV360. Strong need for modular HTML5 and asset re‑use. | Complex, multi-market campaigns with strong Google stack alignment. | | Amazon DSP | DSP | Standard display image ads: 50–200 KB max file size depending on unit.[^amazon-image] Standard display workflow: up to 10 image assets, 500 KB total for all sizes.[^amazon-std] HTML5 banners must use Amazon SDK click-through; no external link directly in ZIP.[^amazon-std] | Strict, opinionated specs; favors lightweight, standardized units. Benefits most from smart resize and robust QA. | Retail media, e‑com, and brands heavily invested in Amazon Advertising. | | The Trade Desk | DSP | Supports image, HTML5, native, video, audio creatives via REST/GraphQL.[^ttd-types] Specs vary by supply partner; hosted HTML5 vs third‑party tags. | API‑first: Creative and Creative Connector APIs enable bulk upload, approvals, and trafficking automation.[^ttd-connector] | API-driven organizations and agencies wanting end‑to‑end creative ops automation. | | Microsoft Invest / Monetize (Xandr) | DSP + SSP | Approved formats include JPEG, PNG, GIF, DHTML, HTML5, JS third‑party tags.[^xandr-formats] Hosted HTML5 must be single ZIP, index.html at root, clickTag referenced correctly.[^xandr-html5] | Template system supports up to 100 custom templates; template changes can cascade to all creatives.[^xandr-templates] High need for controlled master templates. | Enterprises using Microsoft Advertising / Xandr with strong templated production. | | Adform + Adform Studio | DSP + ad server + studio | Rich media templates specify 40 KB initial download, 100–150 KB polite download, 24 fps for some units.[^adform-pushdown] Many formats require manifest.json + HTML file at ZIP root.[^adform-mraid] | Most creative‑studio‑native: built‑in HTML5 authoring, preview, and testing.[^adform-studio] Still benefits from external automation around versioning. | European/global advertisers needing advanced rich media and integrated studio. |

*Specs summarized from vendor docs as of Aug 2026; always verify current requirements.

Why platform specs matter more than you think

For most creative teams, the bottleneck isn’t ideas; it’s production friction.

• Designers burn hours resizing banners, compressing assets, and fixing rejected HTML5 ZIPs.

• Different DSPs impose conflicting constraints on file size, animation length, and clickTag behavior.

• Creative must be produced in many sizes and variants to feed AI‑driven campaigns and DCO.

Adobe’s 2024 State of Creativity report found that 83% of decision makers saw a change in workload over the last 12 months, and 3 in 4 plan to invest in tools to handle escalating workloads and improve productivity.[^adobe-creativity]

That’s the context for creative automation platforms like Viewst: systems that treat HTML5 banner production as infrastructure between design tools (Figma, Adobe) and media platforms (DV360, Amazon DSP, The Trade Desk).

Google Display & Video 360 creative specs HTML5 (with CM360 + Studio in the loop)

For Google’s stack you’re effectively designing for three products:

• DV360 — media buying and hosted display/rich media creatives

• Campaign Manager 360 (CM360) — ad server and advanced HTML5 hosting

• Studio — authoring for complex rich media formats

DV360 HTML5 display constraints

DV360’s HTML5 display creative specs directly shape your production standards:

• Format: HTML5 display creatives must be uploaded as a ZIP.[^dv360-spec]

• File weight: Max 5 MB total browser download.[^dv360-spec]

• HTTP calls: Max 100 HTTP calls.[^dv360-spec]

• Cookies: Max 25 cookies.[^dv360-spec]

• Animation: Max 30 seconds.[^dv360-spec]

• Core sizes: Common units include 300×250, 728×90, 160×600, 300×600, 970×250, 320×50, 320×100, 320×480, and more.[^dv360-spec]

Google recommends modular, asset-based creative systems, especially for AI-driven campaigns, and highlights that “creative asset variety is key” with new asset generation and asset-level reporting in Display and App campaigns.[^google-genai]

CM360 HTML5 upload behavior

Creative ops must also support CM360’s slightly different HTML5 rules:

• ZIP/ADZ structure: Up to 100 files per ZIP; max 9.5 MB.[^cm360-spec]

• Root file: A root‑level HTML file with the required click tag implementation.[^cm360-spec]

• Polite-load: Polite-load image is recommended to be under 40 KB.[^cm360-spec]

Workflow implications for creative leaders

Operationally, that means:

• You need consistent HTML5 templates that can compile into DV360‑ and CM360‑valid ZIPs.

• The same master creative must comfortably meet DV360’s 5 MB total download and CM360’s 9.5 MB upload limits.

• For advanced rich media (expandables, interstitials), teams still rely on Studio → CM360 → DV360 workflows.[^dv360-rich]

A production studio like Viewst can sit upstream:

• Import master creative from Figma/Adobe.

• Use AI Smart Resize to generate all DV360 core sizes from one master.

• Export production‑ready HTML5 ZIPs tuned for DV360/CM360 constraints.

Amazon DSP: stricter caps and opinionated HTML5 behavior

Among major platforms, Amazon DSP is one of the strictest in terms of display production.

Image and HTML5 limits

From Amazon’s public specs:

• Image display: Many standard JPG/PNG/GIF display units cap at 50 KB, with some larger formats up to 200 KB.[^amazon-image]

• Standard workflow: Supports up to 10 image assets with a combined 500 KB max across all sizes in the upload flow.[^amazon-std]

• HTML5 requirement: HTML5 banners must use Amazon’s click-through SDK; you cannot include an external link directly in the HTML5 ZIP.[^amazon-std]

Amazon also lists 60+ sizes across desktop and mobile and offers AI to auto‑generate additional sizes from uploaded assets.[^amazon-std]

What this means for creative production

• Design teams must aim for radically lean assets and aggressive compression.

• HTML5 templates must embed Amazon’s SDK click-through function, not hard-coded external links.

• High-volume campaigns need smart resize and variant control to stay within the 10‑asset / 500 KB flow.

Viewst can help by:

• Keeping a single master creative as the source of truth, then generating Amazon‑compliant static versions in bulk.

• Using AI Smart Resize and AI Image Deflatening to adapt designs while preserving brand standards.

• Exporting Amazon‑ready files with the correct click-through integration presets.

The Trade Desk creative specs and supported formats

The Trade Desk (TTD) is more flexible on formats and more advanced on workflow automation.

Creative types and upload methods

TTD’s public docs define creatives as:[^ttd-types]

• Image

• HTML5

• Native

• Video

• Audio

Creatives can be uploaded via:

• REST API

• GraphQL API

• UI uploads

TTD’s Creative API supports different attribute subsections per creative type, including hosted HTML5, image, native, and third‑party‑hosted video/audio.[^ttd-api]

Creative Connector and approvals

The Creative Connector is designed to push creatives into TTD at scale:

• It accepts creative data or third‑party ad tags and passes them to supply vendors.

• Creatives are auto-submitted for approval where applicable.[^ttd-connector]

• No ad group can spend until the creative is approved.[^ttd-connector]

Production + automation implications

Compared to Amazon or Google, TTD is API-first, which is ideal if you want:

• Automated bulk upload of HTML5 ZIPs and tags.

• Integration between your production studio (e.g., Viewst) and TTD for synchronized versioning.

• Automatic status checks and alerts when creatives are rejected or require changes.

Here, Viewst functions as the creative infrastructure:

• It standardizes the structure, weight, and animation behavior of HTML5 sets.

• TTD’s APIs then handle trafficking, approvals, and distribution.

Microsoft Invest / Monetize (Xandr): template-driven HTML5

Microsoft’s Invest/Monetize (formerly Xandr) supports a wide array of creative formats, but has precise HTML5 structure rules.

Approved formats and HTML5 structure

Per Microsoft docs:[^xandr-formats]

• Approved formats include JPEG, PNG, GIF, DHTML, HTML5, JavaScript third‑party ad tags.

• Hosted HTML5 must be provided as a single ZIP.[^xandr-html5]

For hosted HTML5 creatives:[^xandr-html5]

• index.html must be at the root of the ZIP.

• The clickTag must be referenced correctly in the creative URL / code.

• Any assets referenced in HTML must be contained within the ZIP.

Creative template system

Xandr supports a Creative Template Service:[^xandr-templates]

• Up to 100 custom templates can be defined.

• Updating a template can immediately affect all creatives using that template.

• If an update breaks rendering, those creatives can be rejected.

Implications for creative ops

• You need rigidly governed HTML5 templates; ad-hoc edits can trigger mass rejection.

• A master creative system (like Viewst’s brandbooks and locked templates) reduces risk when templates change.

• Any automation should respect template IDs and versioning to avoid accidental global changes.

Adform Studio: creative-studio-native HTML5 and rich media

Adform is the most “creative-studio-native” platform in this set, with Adform Studio sitting alongside its ad server and DSP.

Adform Studio capabilities

Adform Studio allows creative teams to:[^adform-studio]

• Create, upload, preview, edit, and test HTML5 banners.

• Use pre-defined templates for common formats and rich media units.

Rich media and IAB-like constraints

Adform’s format docs reveal production constraints similar to IAB Rising Star and rich media specs:

• Many templates specify 40 KB max initial download.[^adform-pushdown]

• 100–150 KB polite download depending on device.[^adform-pushdown]

• Animation at 24 fps on some units.[^adform-pushdown]

Several templates require specific ZIP structure:[^adform-mraid]

• manifest.json at root.

• HTML file at root.

• Assets organized per manifest references.

How external creative automation fits

Even with Adform Studio, high-volume teams still wrestle with:

• Versioning across markets and languages.

• Consistent brandbooks across dozens of formats.

• Integrating feedback and approvals inside production.

A dedicated creative infrastructure like Viewst can:

• Manage master creatives and brand systems outside any single ad server.

• Output Adform‑compliant HTML5 ZIPs and rich media variants.

• Keep review and approvals close to production via collaborative preview and commenting.

DCO integration with ad servers and DSPs

Dynamic Creative Optimization (DCO) compounds the production challenge.

Regardless of vendor, DCO requires:

• Structured creative templates with clearly defined dynamic fields.

• Reliable mapping between template fields and feed columns (product, price, copy, imagery).

• Ability to generate and maintain large variant sets without manual layout work.

How major platforms approach DCO (at a high level):

• Google (DV360 + Studio) – DCO typically uses Studio or template-based systems with CM360 hosting. Variants are driven by feeds and rules; creatives must conform to DV360/CM360 specs.

• The Trade Desk – DCO behavior can vary by supply partner and ad server. Hosted HTML5 templates plus dynamic tags are common; its APIs help synchronize large variant catalogs.

• Amazon DSP – Dynamic strategies are constrained by strict file-size caps and limited asset slots. Often, product/offer rotation relies on Amazon’s own retail signals and templated display units.

• Adform – Offers template-based dynamic formats where manifest.json and HTML define placeholders that are populated at runtime.

Viewst’s role in DCO:

• Use a single master creative to define layout, brand styling, and dynamic zones.

• Generate HTML5 templates for each platform with locked brandbooks and mapped dynamic fields.

• Let ad servers/DSPs handle the runtime logic, while Viewst handles the heavy lifting of format scaling and brand consistency.

IAB Rising Star & rich media format support (Rising Star specs)

While classic IAB Rising Star formats (e.g., pushdown, filmstrip) are no longer the only standard, their constraints still shape rich media HTML5.

Common patterns across platforms (modeled on IAB-style specs):

• Initial load weight: Often 40 KB or lower for initial assets (e.g., Adform pushdown unit).[^adform-pushdown]

• Polite load weight: Additional 100–150 KB once user is engaged or page is stable.[^adform-pushdown][^cm360-spec]

• Frame rate: Around 24 fps for smoother motion without excessive CPU usage.[^adform-pushdown]

• Structure: manifest.json + HTML at root for some mobile rich media formats.[^adform-mraid]

For creative leaders, this means:

• Treat rich media as code‑adjacent production: QA must cover not only aesthetics but loading behavior and performance.

• Use tools that can auto‑generate polite-load versions, manage manifest files, and enforce payload budgets.

Viewst’s AI Instant Animator plus HTML5‑native output allows teams to add motion efficiently while still respecting initial/polite load limits.

Ethical AI in advertising creative tools

As AI becomes central to creative automation, governance and ethics matter.

Key principles for ethical AI in display ad design:

• Respect for expertise: AI should remove mechanical work (resizes, exports, basic animation), not replace creative judgment.

• Brand safety and compliance: Automation must respect brandbooks, legal copy, and regulatory constraints, especially in regulated industries.

• Transparency: Creative teams should understand how AI tools manipulate layouts and assets, with the ability to override.

• Data privacy: DCO setups must handle audience data responsibly and comply with privacy regulations.

Viewst is explicitly positioned as AI for production, not just generation. Its features — Smart Resize, Image Deflatening, Instant Animator — operate around a master creative and locked brandbooks so designers stay fully in control of the creative outcome.

1-page creative QA checklist for programmatic HTML5 ads

Use this HTML5 QA checklist before you upload to any DSP or ad server.

Structure & files

• [ ] Single ZIP per creative; no nested ZIPs (required by DV360, Xandr, Adform).[^^dv360-spec][^xandr-html5][^adform-mraid]

• [ ] index.html at the root of the ZIP (required by Xandr; common best practice).[^xandr-html5]

• [ ] For platforms like Adform, manifest.json at root if template demands it.[^adform-mraid]

• [ ] File naming uses ASCII characters and no spaces/special characters where prohibited.

• [ ] Max 100 files per ZIP if you plan to upload via CM360.[^cm360-spec]

Click-through & tracking

• [ ] Implement the correct clickTag / click-through function for each platform:

  • Google: click tag per Studio/CM360 guidelines.[^cm360-spec]

  • Amazon: Amazon SDK click-through; no external link in HTML5 ZIP.[^amazon-std]

  • Xandr: clickTag referenced in creative URL as required.[^xandr-html5]

• [ ] All click areas work across sizes; test in multiple browsers.

• [ ] No hard‑coded external URLs where the platform demands macros/SDKs.

Weight, calls, and performance

• [ ] Total ZIP upload size within platform limits (e.g., 9.5 MB for CM360).[^cm360-spec]

• [ ] Total download weight within live serving caps (e.g., 5 MB and 100 HTTP calls for DV360 HTML5).[^^dv360-spec]

• [ ] Initial load under 40 KB where required; remainder loads politely (CM360, Adform rich media).[^^cm360-spec][^adform-pushdown]

• [ ] Animation duration ≤30 seconds for DV360 and aligned to 24–30 fps where specified.[^dv360-spec][^adform-pushdown]

• [ ] Images optimized (compressed JPEG/PNG/WebP) without visible artifacts.

Layout & brand consistency

• [ ] All required sizes (300×250, 728×90, 160×600, 300×600, 320×50, etc.) are present and legible.[^dv360-spec]

• [ ] Fonts, colors, and logo usage match your brandbook.

• [ ] No text is cut off or overlapping at smaller sizes.

• [ ] Localizations (language variations) use correct copy and legal disclaimers.

Platform-specific validation

• [ ] Test each HTML5 ZIP in the platform preview (DV360/CM360/Adform/TTD/Xandr).

• [ ] Confirm click-through, animation, and tracking work as expected.

• [ ] Check for and resolve any creative rejection reasons before rollout.

Creative automation platforms like Viewst can embed much of this QA into the production pipeline — enforcing file-size limits, clickTag patterns, and brand standards at export.

When creative automation becomes infrastructure (and where Viewst fits)

Across all these platforms, the pattern is clear:

• Specs are non-interchangeable. A banner that passes DV360 may fail Amazon DSP or Adform.

• Workflows are fragmented across design tools, media platforms, and email/Slack.

• Creative leaders are asked to ship more formats and variants without growing headcount.

That’s why treating banner production as infrastructure, not ad-hoc design, is critical.

Viewst’s role in that infrastructure:

• Master creative as single source of truth – all sizes and variants sync from one master, aligning with Google’s modular creative guidance.

• AI for production, not replacement – Smart Resize, Image Deflatening, AI Designer, and Instant Animator remove repetitive work while designers stay in control.

• HTML5-native output – exports DV360-, CM360-, Amazon-, TTD-, Xandr-, and Adform-ready HTML5/GIF/MP4 from the same system.

• Brandbooks and governance – enforce fonts, colors, and logo usage across markets and teams.

• Integrated review and approval – comments and sign‑offs live with the creative set, not in scattered screenshots.

If your team is juggling DV360, Amazon DSP, The Trade Desk, Microsoft/Xandr, and Adform at once, a platform like Viewst becomes the single production studio that abstracts those differences away.

FAQ: creative-leader questions about programmatic display production

1. Which platform has the strictest file-size caps for display ads?

Among the major platforms covered here, Amazon DSP is notably stricter for standard display:

• Many units cap static image files at 50–200 KB.[^amazon-image]

• The standard display workflow allows up to 10 image assets with 500 KB total across all sizes.[^amazon-std]

By contrast, DV360 allows HTML5 creatives with 5 MB total download and 100 HTTP calls,[^dv360-spec] and CM360 allows HTML5 ZIP uploads up to 9.5 MB.[^cm360-spec]

2. How should we handle clickTag and click-through differences across platforms?

Treat click-through behavior as platform-specific code, not a generic snippet:

• Build HTML5 templates that can switch clickTag implementations per export profile.

• For Amazon, ensure HTML5 banners use the Amazon SDK click-through function and exclude direct external URLs in the ZIP.[^amazon-std]

• For Xandr and Google, follow each platform’s clickTag naming and macro requirements.[^xandr-html5][^cm360-spec]

Using a tool like Viewst, you can define export presets for each platform so designers never manually edit clickTag code.

3. When should we use DSP-hosted creatives vs third-party ad tags?

Use DSP- or ad-server-hosted HTML5 when:

• You want faster approvals and fewer vendor dependencies.

• File-size and spec requirements are easy to meet with optimized HTML5 ZIPs.

• You want clean asset-level reporting (e.g., Google’s asset reporting for Display/App campaigns).[^^google-genai]

Use third-party tags when:

• You rely on complex DCO or proprietary rich media not supported natively.

• Measurement or verification vendors require their own containers.

• You need to update creatives centrally without re-uploading to every DSP.

4. How can we validate HTML5 ZIPs for each platform before upload?

Best practices:

• Build a central QA checklist (like the one above) into your workflow.

• Maintain platform-specific export profiles that bake in file-size caps, HTTP call limits, and ZIP structure requirements.

• Use each platform’s preview tools plus a staging environment in your creative automation platform (e.g., Viewst preview links) to test click-through, animation, and layout.

• Where possible, use API-based creative validation (e.g., The Trade Desk’s creative APIs) to catch issues programmatically before launch.

For a deeper dive into how these production realities tie into trafficking, DCO, and media strategy, read the related guide: “Display Ad Platform Support: How Creative Teams Align with Programmatic Advertising.”

And if your team is feeling the weight of multi-platform spec juggling, explore how Viewst can function as your HTML5 ad production infrastructure — so designers stay focused on creative decisions, not file wrangling.

[^dv360-spec]: Google Display & Video 360 HTML5 creative specs – support.google.com/displayvideo/answer/10261241
[^dv360-rich]: Google DV360 rich media guidance – support.google.com/displayvideo/answer/7128959
[^cm360-spec]: Google Campaign Manager 360 HTML5 creative guidelines – support.google.com/campaignmanager/answer/4558694
[^amazon-image]: Amazon Advertising standard display image specs – advertising.amazon.com/help/G4HEYGY4JYWDKEA8
[^amazon-std]: Amazon DSP standard display workflow and file-size limits – advertising.amazon.com/help/GK2JPNKV399ZAWG8
[^ttd-types]: The Trade Desk creative types and formats – partner.thetradedesk.com/v3/portal/api/doc/Creative
[^ttd-api]: The Trade Desk creative API reference – partner.thetradedesk.com/v3/portal/api/ref/post-creative
[^ttd-connector]: The Trade Desk Creative Connector docs – partner.thetradedesk.com/v3/portal/api/doc/CreativeConnector
[^xandr-formats]: Microsoft/Xandr creative guidelines and formats – learn.microsoft.com/en-us/xandr/invest/creative-guidelines-and-specifications
[^xandr-html5]: Microsoft/Xandr HTML5 creative guidelines – learn.microsoft.com/en-us/xandr/invest/html5-creative-guidelines-and-specifications
[^xandr-templates]: Microsoft/Xandr Creative Template Service – learn.microsoft.com/en-us/xandr/digital-platform-api/creative-template-service
[^adform-studio]: Adform Studio capabilities – studio.adform.com
[^adform-pushdown]: Example Adform rich media template (IAB pushdown) – creative.adform.com/media/62176/Adform-IAB-Pushdown-980x300_980x600-.pdf
[^adform-mraid]: Example Adform MRAID mobile template – creative.adform.com/media/307489/adform-mraid-mobile-pull-468x400.pdf
[^adobe-creativity]: Adobe State of Creativity 2024 – adobe.com/content/dam/cct/creativecloud/business/teams/whitepapers/dotcom-116728/Adobe_StateofCreativity_Report_2024_FV_UE.pdf
[^google-genai]: Google Ads blog on creative reporting and gen AI tools – blog.google/products/ads-commerce/creative-reporting-and-genai-tools/