
Uploading a standalone HTML file to Frame.io V4 does not preserve it as an interactive advertisement. Frame.io says that route produces a static image or PDF. For an authorized HTML film ad, use its supported interactive ZIP conversion or an eligible live web asset, then verify the page's actual media and click behavior.
Key Takeaways
- A picture of an ad cannot verify its playback or links.
- An HTML ZIP must satisfy package requirements and become an Interactive asset.
- The recipient must test the intended page state and viewing size.
Choose a reviewable representation
The official Frame.io HTML Review guide covers HTML animations, interactive banners and ads with streaming media. It distinguishes ordinary stored ZIP files from converted interactive assets. Uploading an archive successfully is therefore not the same as enabling interactive review.
Use only files and pages you are authorized to share. Keep production credentials, private customer data and unrelated sources out of the package. This is preparation for a supported review workflow, not a reason to execute unfamiliar downloaded code.
A movie export remains useful for picture review, as the review-copy versus master guide explains. It cannot demonstrate whether the surrounding HTML buttons or responsive layout work.
Check the complete HTML package
The captured guide requires an unpackable ZIP, fewer than 100 files and fewer than 100 directories, a size below 500 MB, and no executable installers or nested archives. It limits directory nesting to five and each HTML file to less than 10 MB. It also requires a root HTML or HTM entry, with a documented special case for a single enclosing directory.
Review the intended entry page. Where multiple HTML files exist, Frame.io chooses its starting page using an order beginning with index, then default, then main. A correct advertisement can still appear missing if an unintended entry loads first.
Keep media paths and required resources associated with the chosen page. A missing remote film may be a resource-access issue rather than a ZIP-conversion failure.
Verify conversion and separate live-page limitations
When an eligible package is detected, Frame.io offers conversion to an interactive asset. If kept as an ordinary ZIP, it does not have that review-and-approval experience. Confirm processing has finished and the resulting asset is marked Interactive before asking a reviewer to click through it.
For live web assets, the source requires sites that permit iframe embedding. It lists YouTube and Figma URLs as unsupported and warns that some private authentication flows may fail. Do not remove security restrictions merely to force a sensitive page into the viewer. Enhanced annotations have additional browser-extension requirements; they are not a reason to claim all private sites work.
Accept interaction, picture and sound separately
For a proposed film launch ad, have the recipient open the intended page, resize to the agreed layout, start the film, inspect captions and follow its call to action. Record the page and viewing resolution with feedback. A desktop screenshot does not verify the mobile interaction.
The autoplay guide separates browser playback permission from missing media. The web-caption loading guide addresses an absent text track. Accept when the actual interactive representation supports the agreed review tasks, with unsupported actions recorded rather than replaced by a reassuring static preview.
Related tasks
- Should I Send a Review Copy or the Final Master of an AI Video to a Client?
- Why Does My Website Video Play Only After a Click?
- Why Does My SRT Work in a Video Player but Show No Captions on My Website?
Sources and scope
- Frame.io V4: HTML Review: A standalone HTML file is delivered as a static image or PDF. An eligible HTML ZIP can be converted into an interactive asset; a root HTML file and documented archive limits apply. Supported live URLs must allow iframe embedding, and some authentication flows and sites are unsupported.
Based on the complete official HTML Review source captured October 29, 2026. No HTML, archive, extension or live URL was opened or uploaded. Packaging and acceptance procedures are proposed. HTML review is explicitly distinguished from an ordinary unsupported project ZIP, and no blanket support for private pages or arbitrary websites is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.