A buyer asks for “one HTML5 banner concept in four sizes.” Then two languages, two products, a promotion, Google Ads, Display & Video 360, backups, and revision rounds enter the brief. It is still one campaign—but no longer one unit of work.
A useful HTML5 banner production cost estimate therefore starts with a deliverable map, not a price per file. Count concepts, layout masters, approved appearances, platform packages, backups, and QA passes separately. That reveals what can be reused and what reopens design, engineering, packaging, or review.
Our fictional example turns 32 theoretical combinations into 20 approved appearances, then 26 HTML5 ZIPs and 20 JPGs. An 18-line effort worksheet shows why an unchanged file count can still hide substantial production work.
Start With the Units You Are Actually Buying
“Banner” is too ambiguous to be a reliable line item. A quote should distinguish at least six units:
- Concept: the central message, visual idea, and animation direction.
- Layout master: an approved composition for an aspect-ratio family, such as rectangle, tower, or leaderboard.
- Appearance: one approved combination of concept, language, product or offer, size, and behavior.
- Platform package: the ZIP or other artifact prepared for a specific delivery environment.
- Backup asset: the static fallback supplied separately or alongside the HTML5 package.
- QA pass: a defined check of a package or appearance in a named browser, size, locale, preview, account, or acceptance stage.
These units overlap but are not interchangeable. A provider may charge per appearance, size, master plus adaptation, hour, or campaign suite. One responsive ZIP may represent several sizes; one appearance may need multiple environment packages. Revision capacity and defect correction may also follow different commercial rules.
Production can cover briefing, concept or storyboard, asset preparation, masters, animation, interaction, adaptation, packaging, trafficking support, QA, revisions, and handoff—but public offers start at different points. YYDevelopment describes collecting the brief, approving one banner, then adapting the remaining sizes. GetDevDone starts from a client-supplied design and excludes banner design. Their headline prices do not buy the same work.
Ask every supplier to label shared work, repeated work, and exclusions. “Five banners” might mean five concepts, one concept in five sizes, five localized appearances, or one responsive package with five serving dimensions.
Public Prices Show Different Buying Models, Not a Market Average
Public asking prices reveal how providers define the unit. They are not comparable quotes for one brief, and this small international set cannot establish a US market average.
| Public offer checked September 8, 2026 | Stated price basis | Visible inclusions and limits | What must be confirmed |
|---|---|---|---|
| RevenueJack | €45 / $54 per interactive HTML5 banner | Custom animated design, unlimited revisions, retina-ready creative, fallback image; source files and rush delivery are add-ons | Dollar currency code, exact network set, whether every size is a separately billed banner; VAT applies to EU customers under the stated conditions |
| YYDevelopment | $800 for 1 size; $1,100 for 3; $1,350 for 5; $1,600 for 10 | One design adapted into different sizes; FLA and ZIP files; first banner approved before the rest are produced | Dollar currency code, tax, revision limit, browser or account QA, and whether the listed “recommended” sizes match the media plan |
| MorphMake | $99–149 per standard size; $199–349 per complex size; $49–79 per additional size | Two revision rounds, backup images, click-tag checks, cross-browser testing, platform packaging, and a stated 90-day bug-fix warranty | Dollar currency code, tax, exact definition of standard versus complex, and which platform package is included |
| GetDevDone | Card lists $24 static, $36 animated, $48 interactive; DV360/Adform is +20% | Development from supplied design, up to 15 seconds for animated work, one or two revisions, ZIP, PNG fallback, preview link | The same untouched page also shows a $49 package summary, so the applicable price must be confirmed before treating either number as a quote |
| DigiLakshya | $64 HTML5 master; $32 per additional size; $32/hour pay-as-you-go | Master and resize separated; “unlimited revisions within the original brief” for fixed-price assets | Dollar currency code, tax, master complexity, environment packages, and how the original brief is frozen |
| Email Mavlers | “HTML” banner: $79 unique, $49 adaptation | Separates unique work from adaptation | The page does not define the exact HTML5 animation, ZIP, network, QA, tax, or dollar-code scope |
| Maddison Creative | From £199 for one animated HTML5/GIF; from £599 for five; interactive HTML5 is POA | A set discount is visible | HTML5 and GIF share a line, while sizes, concepts, revisions, delivery files, and acceptance scope are not stated |
Compare denominators, not just totals. RevenueJack prices a banner; YYDevelopment discounts one design across sizes; DigiLakshya separates master and resize; GetDevDone starts from supplied design and adds percentages for some environments. Each model can produce a different total without being inconsistent.
Conflicts should be quarantined, not reconciled by guesswork. Plus Also’s terms, updated March 3, 2026, describe an HTML5 display rollout suite at USD 5,500 excluding GST, while its current product page lists other output formats and says HTML5 is “coming soon”. Separate 2026 announcements used still other product and price bases. None is treated here as a current comparable HTML5 quote.
Worked Example: 32 Possible Combinations Become 20 Approved Appearances
The following fictional teaching brief is not an observed campaign or supplier quote. “Trailmark” is an imaginary outdoor-footwear retailer; P1 is its Summit trail shoe and P2 its City runner.
The campaign has one seasonal concept, two locales (en-US, es-US), two products, two offer states (Base, Promo), and four candidate sizes: 300×250, 300×600, 728×90, and 320×50.
The raw multiplication is:
1 concept × 2 locales × 2 products × 2 offers × 4 sizes = 32 theoretical combinations
But the media and content rules say:
P2 / Promowill not run in either language: remove 8 combinations.es-US / P1 / Promoruns only in 300×250 and 300×600: remove 2 horizontal combinations.es-US / P2 / Basealso runs only in 300×250 and 300×600: remove 2 horizontal combinations.
The excluded groups do not overlap, so:
32 − 8 − 2 − 2 = 20 approved appearances
| Content group | Approved sizes | Appearances |
|---|---|---|
| en-US / P1 / Base | 300×250, 300×600, 728×90, 320×50 | 4 |
| en-US / P1 / Promo | All four sizes | 4 |
| en-US / P2 / Base | All four sizes | 4 |
| es-US / P1 / Base | All four sizes | 4 |
| es-US / P1 / Promo | 300×250, 300×600 | 2 |
| es-US / P2 / Base | 300×250, 300×600 | 2 |
| Total | Selected combinations only | 20 |
The Cartesian product is not automatically the order. Approval, inventory, legal copy, product availability, and layout feasibility decide which combinations exist. Count before applying those rules and both the file estimate and QA plan inflate.
A zero “extra variations” value should still leave the baseline creative; an empty approved set is different. Output count and work already performed must remain separate records.
Why 20 Appearances Become 26 ZIPs and 20 JPGs
Now apply two delivery profiles to the same 20 appearances.
For this example, Google Ads uses one fixed-size ZIP per appearance. Display & Video 360 uses one responsive ZIP per content group, with that group’s approved serving sizes inside the package. Each appearance also receives one JPG final-frame backup shared across the two profiles.
| Content group | Google Ads fixed ZIPs | DV360 responsive ZIPs | Backup JPGs |
|---|---|---|---|
| en-US / P1 / Base | 4 | 1 | 4 |
| en-US / P1 / Promo | 4 | 1 | 4 |
| en-US / P2 / Base | 4 | 1 | 4 |
| es-US / P1 / Base | 4 | 1 | 4 |
| es-US / P1 / Promo | 2 | 1 | 2 |
| es-US / P2 / Base | 2 | 1 | 2 |
| Total | 20 | 6 | 20 |
The active delivery is therefore:
- 20 Google Ads ZIPs
- 6 DV360 responsive ZIPs
- 20 backup JPGs
- 46 active assets in total
The six DV360 ZIPs do not erase their 20 appearances; they change the package topology. There are still 40 appearance–profile states to consider across Google Ads and DV360.
A fully fixed-size plan for both environments would produce 40 ZIPs plus 20 JPGs. The responsive plan has 14 fewer ZIPs, but not necessarily the cost of 14 fewer banners: responsive engineering, serving-size registration, and size-by-size review remain. File reduction is observable; labor savings would require a comparable production measurement.
Reuse Ends Where Layout, Language, Assets, or Behavior Change
Reuse is real, but it has boundaries. The fictional brief uses three layout masters: 300×250 for rectangles, 300×600 for towers, and 728×90 for wide placements. The 320×50 version inherits the wide concept but requires a structural adaptation.
The geometry explains why. Scaling 728×90 proportionally to 320 pixels wide produces a height of only 39.56 pixels. Scaling it to 50 pixels high produces a width of 404.44 pixels—84.44 pixels wider than the available canvas. A simple export cannot satisfy both dimensions. The producer must reconsider hierarchy, crop, logo, copy, CTA position, motion path, and final frame.
Language can trigger the same kind of work. In the example, “Shop now” contains 8 characters including the space, while “Comprar ahora” contains 13. Character counts are not reliable width measurements, and a shorter translation can also create awkward empty space. The W3C’s internationalization guidance recommends flexible layouts and warns that translated strings, glyph widths, compound words, and line heights can change the space required. A locale therefore should not be scoped as a blind text swap unless the exact copy has already been fitted and approved.
Product and offer changes also differ. A pre-cropped image with the same silhouette may be a simple swap; a new focal point, embedded language, or font can reopen crop, localization, asset preparation, and rights review. Copy-only offers may reuse the timeline, while a second exit, hover state, countdown, or new legal disclosure changes behavior.
Classify each request as a simple content adaptation, localized reflow, structural layout adaptation, or behavior/profile change. Follow the dependency, not the buyer’s label.
Platform Packaging and QA Are Separate Scope Layers
“HTML5 ZIP” names a technology family, not a universal delivery contract. Current first-party requirements show why environment work belongs in the estimate.
| Environment | Packaging or behavior that affects scope | Verification consequence |
|---|---|---|
| Google Ads uploaded HTML5 | ZIP up to 600 KB, no more than 40 files, local/relative assets with limited hosted exceptions, Google Ads environment in Google Web Designer, no expandable ads, and no timer or multiple exits for environment target actions | Check compressed package weight, file inventory, entry metadata, asset references, click behavior, and account eligibility. Do not borrow the 150 KB image/GIF limit for HTML5. |
| Display & Video 360 | Animation up to 30 seconds, browser download up to 5 MB, up to 100 files in the ZIP, click tags, and publisher limits that may be smaller | Test the served download assumptions as well as the upload package. A ZIP can have no platform upload-size limit while still failing a publisher or browser-download rule. |
| DV360 responsive creative | One creative can restyle across selected serving sizes; backup images are uploaded separately, one per size if used; serving sizes cannot be edited after publication | Review every approved size, confirm the registered dimensions, and treat a post-publication size change as a replacement or registration event rather than a silent export. |
| Adform | A root-level manifest.json and main HTML file are required, clickTAG names are case-sensitive, the DHTML library must be included, and banner weight is measured after unzipping |
A Google-ready package is not automatically an Adform-ready package. Manifest, click variables, library integration, upload parsing, and weight accounting need their own checks. |
Shared art, motion logic, layouts, and content can remain common across environments. The profile-specific layer owns click handling, metadata, packaging, limits, and the official preview or account path. Google Web Designer warns that converting environments can discard incompatible events or bindings and recommends saving a new copy.
Itemize QA instead of hiding it inside “production included.” Separate four layers:
- Automated package checks: weight, file count, syntax, manifest, asset paths, and validator messages.
- Human visual and behavioral review: each approved size, locale, product, offer, animation state, and backup frame.
- Account or official-preview checks: upload result, detected dimensions, click configuration, and the preview context the platform actually supports.
- Production acceptance: consolidated stakeholder feedback against the approved storyboard, layouts, copy, destinations, and exclusions.
Passing a validator is not approval: Google Web Designer calls its Ad Validator informational. Nor does a non-clicking creation preview prove failure; Google Ads documents a supported full-size preview path after saving.
Our selected QA plan creates 20 appearances × 2 profiles × 4 configurations = 160 planned review cells. This is a coverage plan, not 160 measured tests or a platform mandate. It makes “QA included” comparable.
A Completed 18-Line Effort Budget
The following worksheet is deliberately synthetic. No supplier quoted this fictional brief. The quantities and time coefficients are teaching assumptions, and the uniform USD 80/hour rate is illustrative—not a market benchmark. Public provider prices above are not inputs to this calculation.
| # | Work item | Basis | Hours | Illustrative labor |
|---|---|---|---|---|
| 1 | Brief, concept, storyboard | Shared project work | 6.00 | $480.00 |
| 2 | Asset preflight and preparation | Shared project work | 4.00 | $320.00 |
| 3 | Three layout masters | 3 × 3 hours | 9.00 | $720.00 |
| 4 | 320×50 structural adaptation | 1 × 2 hours | 2.00 | $160.00 |
| 5 | Shared HTML5 animation core | One 15-second, single-loop implementation | 8.00 | $640.00 |
| 6 | Google Ads environment profile | Packaging and click integration | 2.00 | $160.00 |
| 7 | DV360 responsive profile | Responsive/package integration | 4.00 | $320.00 |
| 8 | Simple content adaptations | 8 × 15 minutes | 2.00 | $160.00 |
| 9 | Localized layout adaptations | 8 × 45 minutes | 6.00 | $480.00 |
| 10 | ZIP export batch | 26 active ZIPs, batched allowance | 2.00 | $160.00 |
| 11 | JPG backup batch | 20 backups, batched allowance | 2.00 | $160.00 |
| 12 | Automated-report review | 26 × 3 minutes | 1.30 | $104.00 |
| 13 | Canonical visual reviews | 40 appearance–profile states × 6 minutes | 4.00 | $320.00 |
| 14 | Other configuration smoke reviews | 120 × 2 minutes | 4.00 | $320.00 |
| 15 | Upload-result reviews | 26 packages × 3 minutes | 1.30 | $104.00 |
| 16 | URL and click checks | 40 states × 2 minutes | 1.33 | $106.67 |
| 17 | In-scope revision capacity | 2 consolidated rounds × 2 hours | 4.00 | $320.00 |
| 18 | PM, acceptance manifest, and handoff | Shared allowance | 3.00 | $240.00 |
| Total | 3,956 resource-minutes | 65.93 | $5,274.67 |
The exact total is 65 hours 56 minutes of resource time, not calendar lead time. It excludes translation, media, licenses, tax, new concepts, complex interaction, campaign management, and out-of-policy revisions. The actual project quote remains unknown.
If primary reviews take 10 rather than 6 minutes and other configurations 3 rather than 2, the same files add 280 minutes and the illustrative subtotal becomes $5,648. If eight localized adaptations take 75 rather than 45 minutes, four hours are added while the 20/26/20 counts remain unchanged.
The Same Six Changed Appearances Can Reopen 12 ZIPs or 8
Change requests expose why active file count is a poor proxy for effort.
Suppose a late layout change affects the 300×250 master. Six appearances use that master: three English groups and three Spanish groups. Each has a Google ZIP, and each sits inside a different DV360 responsive package. The change therefore creates 12 replacement ZIP versions—6 Google plus 6 DV360—and 6 replacement JPGs.
Now suppose the P2 product image changes. It also affects six appearances, but those appearances are grouped into only two DV360 packages. This creates 8 replacement ZIP versions—6 Google plus 2 DV360—and 6 replacement JPGs.
| Change | Changed appearances | Replacement ZIP versions | Replacement JPG versions | Planned QA coverage under the selected regression policy | Final active output count |
|---|---|---|---|---|---|
| 300×250 master layout change | 6 | 12 | 6 | 104 cells | 26 ZIP + 20 JPG |
| P2 image replacement | 6 | 8 | 6 | 48 cells | 26 ZIP + 20 JPG |
Under the chosen regression policy, every approved size in a rebuilt responsive package is reviewed again. The master change touches six responsive packages representing 20 DV360 appearances; the product change touches two packages representing six. The 104 and 48 cells are illustrative coverage decisions, not platform mandates.
After old versions retire, both scenarios still end at 46 active assets. Rework and version history grow; the final manifest does not.
Redesigning that master, rebuilding 12 ZIPs and 6 JPGs, running the selected regression checks, reviewing uploads, and retesting clicks totals 568 minutes—9 hours 28 minutes. At the illustrative rate, it adds $757.33 and raises the synthetic labor total to $6,032.
Who pays remains a contract question. The same repair may be new client direction, an included revision, or a supplier defect. GetDevDone defines consolidated feedback and distinguishes out-of-scope and post-acceptance work; MorphMake advertises revision rounds and a bug-fix warranty. Classify the commercial event before applying a fee.
How to Request Quotes That Can Actually Be Compared
Send every bidder the same approved combination map and ask for the response in the same structure:
- Inputs: approved copy, translations, brand files, product images, landing URLs, legal lines, font and stock rights, and who prepares missing assets.
- Creative scope: number of concepts, storyboard responsibility, animation length and loops, interactions, exits, and what counts as a new direction.
- Master scope: named aspect-ratio families and which sizes require structural adaptations rather than simple resizes.
- Variation scope: approved language, product, offer, and size combinations—not just the raw possible combinations.
- Environment scope: exact account or network profile, package type, click handling, backup policy, validation, and trafficking responsibility.
- QA scope: automated checks, browsers, sizes, locales, account uploads, click tests, backup review, and acceptance owner.
- Revision scope: number of consolidated rounds, feedback deadlines, defect warranty, late updates, and out-of-scope rate.
- Commercial scope: currency code, tax, minimums, rush fees, source files, licenses, external costs, payment schedule, and ownership.
Ask for separate totals for shared creative and engineering, adaptations, platform packaging, QA, revision capacity, and optional work. They need not match this article’s coefficients; they must reveal the supplier’s denominator.
Twenty outputs do not require twenty times the concept work, but automated export does not remove adaptation, packaging, or review. Count valid appearances first, map platform artifacts second, then price the work drivers. That makes both the quote and later change requests explainable without treating every ZIP as a new idea—or every reuse as free.
Try the scope calculator to change approved appearances and delivery profiles. The filled workbook keeps the article baseline, editable effort quantities, supplier comparison, and quote checklist together. Its saved delivery map and change examples are fixed examples; changing top-level counts does not generate new map rows or automatically revise effort quantities.
Sources
- Uploaded display ads specifications — Google Ads Help; checked September 8, 2026.
- Fix error messages with Uploaded ads — Google Ads Help; checked September 8, 2026.
- Guidelines for HTML5 display creatives — Display & Video 360 Help; checked September 8, 2026.
- HTML5 creatives — Display & Video 360 Help; checked September 8, 2026.
- Responsive HTML5 creatives — Display & Video 360 Help; checked September 8, 2026.
- The Ad Validator and The ad environment — Google Web Designer Help; checked September 8, 2026.
- Requirements for HTML5 Banner Files — Adform; updated March 31, 2025; checked September 8, 2026.
- Text size in translation — W3C Internationalization; checked September 8, 2026.
- RevenueJack pricing, YYDevelopment HTML5 Banners Design, MorphMake HTML5 Banner Ads, GetDevDone digital assets, DigiLakshya pricing, Email Mavlers pricing, and Maddison Creative pricing — provider-published offers; checked September 8, 2026.
- GetDevDone Terms and Conditions — last updated May 20, 2026; checked September 8, 2026.
- Plus Also Studios Terms of Service — last updated March 3, 2026; current product page; checked September 8, 2026.
- Plus Also Studios launches new $5k rollout service — Campaign Brief, March 10, 2026; and Plus Also Studios releases Unicorn for all — Campaign Brief, July 23, 2026.
