HTML5 Ad Inspector
MarketingInspect HTML5 ads before they go live. Drop a ZIP, paste an iframe or script tag, or enter a creative URL — checked in your browser, never uploaded.
HTML5 Ad Inspector checks a display creative before it goes live. Drop an HTML5 ZIP or an HTML file, or paste an iframe tag, a third-party script tag or a creative URL, choose where the ad will run, and get a plain report: the size it states, whether its files are all there, HTTPS and mixed content, external domains, click handling, file weight, and the chosen publisher's own limits, each with a link to where the rule comes from. Drop a whole campaign — several ZIPs, or one ZIP with a folder per size — for a table of every creative and what to fix first, downloadable as a spreadsheet. Run the creative in a sandboxed preview to see its script errors, console output, requests and the size it really draws, and save your own publisher specifications in your browser. Files are opened in your browser and never uploaded; a pasted tag is read as text, so the creative itself stays on its own server.
Why use HTML5 Ad Inspector
100% private
Your creative files are processed locally and never uploaded.
Instant
No upload or download wait — it runs at the speed of your device.
Free to start
Use it free every day; go Pro for unlimited runs.
No install
Works in any modern browser. No sign-up to begin.
How to use HTML5 Ad Inspector
- 1Give it the creative
Drop an HTML5 ZIP or HTML file, or paste an iframe tag, a script tag, some HTML or a creative URL. The type is detected for you.
- 2Choose where it will run
Pick the publishing environment — General / IAB, Amedia, Polaris Media, Google Ads, Google Ad Manager — or paste your own specification as JSON.
- 3Read the report
Problems come first, then every check by category, with the source and date behind each publisher rule. Switch publisher and the rules re-run at once.
Frequently asked questions
Is my ad uploaded anywhere?
No. A ZIP or HTML file is opened and read in your browser, and nothing about it is sent to Alvseike — not the files, not their names, not the URLs inside them. A pasted tag or URL is read as text; the creative it points to is not fetched.
Where do the publisher rules come from?
From each publisher's own current public specification, and every rule links to the page it came from with the date it was last checked. What a publisher states as a hard limit fails as an error; what it offers as guidance shows as a warning. If a limit could not be confirmed from the publisher's documentation, it is not in the tool.
Can it look inside a hosted iframe or script tag?
It reads the tag itself — its source, size, parameters, HTTPS and click parameters. Show the preview and it also runs the tag in a sandbox and reports what happened: script errors, console output, the requests the tag's page made and the size it drew. What the creative does inside its own frames, served from another site, stays out of reach — browser security rules see to that — and the report says so rather than guessing.
Can I check against my own specification?
Yes. Copy a built-in publisher as your starting point, or choose Custom and paste a small JSON specification with the limits you work to — ZIP size, allowed sizes, HTTPS, clickTag and so on. Save it in your browser, where it gets a revision number each time its rules change, or download it as a file to share. It is never uploaded.