HTML · Webflow · Framer
One embed. A page that stays in control.
Prepare the visual once, then install it inside a responsive stage. Use the same asset ID when the approved video changes.
Review current processing, download and publishing allowances on Pricing before you buy.
See the source and transparent result
Generated moving demonstration footage. The interactive page composes the prepared visual over a sample webpage; it does not predict the result or conversion rate of your own video.
Start with an approved hosted asset
An embed needs a published asset, not a temporary upload URL or a private review link. Finish the cutout or existing-alpha preparation, check the result, then authorize the current Hosting offer. The asset ID in Workspace identifies the approved public version. Keep source and working URLs out of client-facing code.
The example below is a prepared demonstration. It shows how a transparent subject can sit over page content; it is not proof that a custom layout, domain or browser has already been tested. Your own public URL is the final verification target.
Use the recipe for your destination
For HTML, copy the complete responsive wrapper from Workspace and load the script once per page. For Webflow, use the documented Code Embed workflow. For Framer, use its supported embed surface. The standard recipe keeps the stage geometry and visual together so you do not accidentally paste a media-only fragment.
Site-builder plans and editor behavior can change. Check the linked official instructions for your current setup, then publish a test page. A builder’s canvas may restrict scripts or render an embed differently from the public site.
Check size, crop and interaction
The parent must have a visible width and height or aspect ratio. If the subject is missing, inspect the container before assuming background removal failed. Check overflow and stacking order if hair, hands or the product are cropped. Avoid placing the transparent layer over links that visitors need to use.
Muted inline animation can still be blocked by browser policy. Keep the poster meaningful, respect reduced-motion preferences, and verify that the rest of the page still works with animation unavailable. Test at the real desktop and mobile dimensions used by your site.
Replace the video without replacing the code
Prepare a replacement from ordinary footage or an existing supported alpha file, review the candidate, and approve it before the public pointer changes. Do not overwrite a cached media URL yourself. The stable asset ID is the integration, while approved media versions can change underneath it.
If the integration looks wrong, use Workspace diagnostics to separate missing resources from a layout issue. Keep the asset reference, browser and public page URL for support. Standard recipes provide a starting point; bespoke theme styling and third-party script conflicts still require work in the destination site.
Frequently asked questions
Can I paste a private result URL into my public page?
Use a published asset’s generated embed. Private result and source URLs have different access and retention rules.
Why is the subject invisible in the builder canvas?
Check the public page, container dimensions, current asset status and builder script support. The canvas alone is not a playback verdict.
Does replacing the video renew Hosting?
No. Replacement preserves the existing asset and current term. Review renewal separately in Workspace.
Sources and review notes
AlphaPublish product limits and workflow statements follow the available product interface; check the displayed limits before uploading or buying. A guide is not evidence that your file has played on every device. Browser, builder, and performance guidance links to primary documentation.