Google Ads HTML5 Eligibility: Get Your Account Ready

There is no single switch for HTML5 ads in Google Ads. Eligibility depends on the campaign type, the account's standing and the asset itself. This guide shows how to check each one and what to do when the option is missing.

By the PlayableRun team··7 min read

Key takeaways - There is usually no "HTML5 on/off" switch. Google Ads HTML5 eligibility is the combined result of campaign type, account standing and the asset itself. - Check the campaign type first. If that campaign type does not accept HTML5, nothing else you do will make the option appear. - Account-level problems, such as unresolved policy notices or incomplete billing setup, can block or slow ad delivery even when the upload option exists. - A passing upload is not the same as an approved ad. Technical validation and policy review are separate steps. - Test with one small, clean asset before you build a full set of creatives.

What "eligibility" actually means

When people say "my account isn't enabled for HTML5," they usually mean one of three different things. Separating them saves a lot of guessing.

  1. The campaign type does not offer HTML5. The interface offers different asset options depending on the campaign. The place you upload HTML5 in a Display campaign is not the place you add it in an App campaign.
  2. The account has a restriction. Policy notices, billing problems or a suspended payment profile can limit what you can run, regardless of format.
  3. The asset is rejected. The option is there, but the file fails validation or review.

Each has a different fix. Most "missing option" tickets turn out to be the first, and most "it won't work" cases turn out to be the third.

Step 1: Confirm the campaign type supports HTML5

Start in the campaign, not in the account settings.

  • Display campaigns let you upload display ads, and HTML5 is one of the accepted formats. You add it at the ad level, in an ad group, as an uploaded creative.
  • App campaigns treat HTML5 as an asset that the system can use among your other assets. You add it in the assets section of the campaign, not as a standalone ad. Our article on how the HTML5 asset is used in App campaigns covers what to expect after it is added.
  • Other campaign types may or may not accept HTML5, and this changes over time as Google updates its products.

Availability can vary by account and over time. Treat the live interface and the Google Ads Help Center as the source of truth, not any blog post, including this one.

A practical check: open a new draft campaign of the type you want, go to the point where you add creatives, and see whether an HTML5 or "upload" option is offered. If you cannot find it in the draft, you will not find it in the live campaign either.

Step 2: Check account standing

An account can be technically allowed to use a format and still be unable to deliver ads. Before you blame HTML5, look at the basics.

  • Billing and payment profile. Make sure setup is complete and no payment issue is flagged.
  • Policy notices. Open the policy manager and look for account-level or ad-level notices. An unresolved issue on the account can make every new ad harder to get through.
  • Advertiser verification and notices. Some accounts are asked to complete verification steps. If you see a banner asking for action, handle it first.
  • Access level. If you work in a shared or manager account, confirm you have permission to create and edit ads in the account where you are working. A read-only role looks a lot like "the option is missing."

None of this is specific to HTML5, which is exactly why it gets overlooked. If your text ads and image ads also behave oddly, the cause is almost certainly here.

Step 3: Prepare an asset that can pass

If the option is visible and your account is healthy, the asset is the next thing to check. Most rejected first uploads fail for ordinary reasons, not exotic ones.

What a Google-ready HTML5 package generally needs:

  • A correct ZIP structure. The entry HTML file and its assets must be where the validator expects them. Details are in our guide to HTML5 ZIP structure, assets and size.
  • A supported click path. Google needs to know where a click goes. That means the right click handling for the ad type, either a clickTag-style variable or the Exit API, depending on the context. See Exit API vs clickTag for how to choose.
  • No external dependencies. Fonts, scripts and images should ship inside the package. Requests to outside hosts are a frequent cause of rejection. Our article on self-contained HTML5 ads explains why.
  • Declared dimensions and sizes that match the slot. Google publishes the current size and file-weight limits. We do not quote numbers here because they change. Check the current spec in the help center before you build, then build to it.

Why does this matter for eligibility? Because a failed first upload is easy to misread as "my account can't do this." Fix the package before you decide the account is the problem.

Step 4: Run a minimal test upload

Before investing in a full playable, test the pipeline with the smallest possible asset.

  1. Build or export a very simple HTML5 ad with one screen and one click action.
  2. Upload it to the correct place in a draft or paused campaign.
  3. Read any validator message carefully. Fix exactly what it says and no more.
  4. Once it uploads, preview it, test the click, and only then expand to the real creative.

This isolates variables. If the simple file uploads, your account and campaign type are fine, and any later failure is about what you added. If even the simple file is rejected, the error text usually tells you which layer to look at. Our guide to uploading an HTML5 ZIP without failing policy walks through the flow in more detail, and the validator errors article helps decode messages.

If you are producing playables rather than simple banners, PlayableRun exports a Google Ads-ready ZIP from a store listing, which can be a quick way to get a test file. You still need to run it through Google's own validation and review, as you would with any other source.

When the option is still missing

Work down this list in order. Stop when something changes.

  • Wrong campaign type or wrong level. Confirm you are in the campaign and ad group where uploads are offered.
  • Wrong account. In a manager hierarchy, make sure you are in the child account that runs the campaign.
  • Insufficient permissions. Ask an admin to check your role.
  • Outstanding account notices. Resolve billing, verification or policy items.
  • Browser or session quirks. Try a clean session or another browser. It sounds trivial, but it does occasionally resolve interface glitches.
  • Feature not available to the account yet. Some features roll out gradually. If everything else checks out, contact Google Ads support with the campaign type, the account ID and a screenshot of where you expected the option.

When you contact support, be specific. "HTML5 is not enabled" is hard to act on. "In a Display campaign draft, under Ads, I see only responsive display ad and no upload option" is something a support agent can check.

Upload is not approval

Even when everything is set up correctly, you are not done. After upload, ads go through review. An ad can be technically valid and still be disapproved for behavior, content or destination issues.

Common review problems with playables include misleading interactions, unclear or broken click-through, and content that does not match the advertised app. Plan for a review step in your launch schedule, and keep a QA pass in your workflow. Our playable policy checklist is a good starting point, and the disapproval causes and fixes article covers what to do if an ad is rejected.

A simple readiness checklist

Use this before you spend time on creative production:

  • Campaign type confirmed to accept HTML5 in the live interface.
  • Account free of unresolved billing or policy notices.
  • Your role allows creating ads.
  • Test asset uploaded successfully to a draft or paused campaign.
  • Click path tested in preview.
  • Current size, dimension and file requirements checked against the network's documentation.

If you can tick all of these, you are eligible in every practical sense. Any remaining problem is specific to the asset, and the error message will usually point at it.

Next step

If you want a playable to run through this process, you can browse working examples at /demos or create a free account and export a ZIP to use as your first test upload. It will not replace Google's checks, but it gives you a realistic file to validate against.

Frequently asked questions

›Is there a setting to enable HTML5 ads in Google Ads?

For most accounts there is no single setting to turn on. Whether you can use HTML5 depends on the campaign type, whether that campaign type accepts HTML5 assets, the account's standing, and whether the file passes Google's checks. If the option is missing, work through those in order before contacting support.

›Why can't I see an HTML5 upload option in my campaign?

The most common reason is the campaign type. Not every campaign type or ad format accepts uploaded HTML5, and the interface differs between Display and App campaigns. Check that you are in the right campaign type and ad group, then check the help center, since availability can change over time.

›Does a new account have to wait before running HTML5 ads?

Google does not publish a universal waiting rule that we can point to. A new account with no billing set up or with open policy issues is more likely to hit limits. Finish setup, resolve any account-level notices, and test with a simple compliant asset.

›Will a file that uploads successfully always be approved?

No. Upload validation checks the technical package. Policy review is a separate step and can still disapprove an ad for content, behavior or landing destination reasons. Treat a successful upload as the first gate, not the last.

›What should I do if the validator rejects my ZIP?

Read the exact error message, fix that one issue and re-upload. Common causes are file structure, missing click handling, or external requests. Our validator errors article walks through the usual ones.

Turn your store listing into a playable

Paste an App Store or Google Play link and get an HTML5 playable you can test in minutes. The first one is free.

Keep reading