Standard vs Fallback embed mode

When you copy a Flare embed snippet, you can pick between two delivery modes — Standard and Fallback. They both play the same video, but they render very differently.

Standard (recommended)

Standard mode loads the player inline on your page as a custom HTML element (<flare-player>). The player runtime loads once per page, then renders directly into your page's DOM.

Why it's the default:

• Faster first paint — no nested document, no second JavaScript context to initialize
• Lighter on the page — multiple embeds on the same page share a single player runtime
• Better integration — the player sits in your page's DOM, so layout, fonts, and dark/light theming flow through naturally
• Smoother on mobile — fewer document parses means less main-thread work and lower battery use

If you have multiple Flare videos on the same page, Standard is strongly recommended. The runtime is fetched once and reused across every embed. With Fallback (iframe), each video is its own document, and the player runtime gets parsed and initialized once per video.

Fallback (iframe)

Fallback mode wraps the player in an iframe. Each embed is its own isolated document.

When to use it:

• Strict content security policies — some CSPs block inline scripts or custom elements but allow iframes from a known origin
• Sandboxed or unknown host environments — CMSs, email-rendered previews, and widget areas with restricted permissions
• Hostile CSS — when the surrounding page has aggressive styles you can't control, an iframe gives you a clean rendering boundary

The cost:

Each iframe is a full page load: its own JavaScript heap, its own cache, its own decoder context. Two embeds = two parallel document parses. Five embeds = five. The bytes-on-the-wire are similar, but the CPU and memory cost compounds quickly on mobile.

Which should I pick?

Default to Standard. Switch to Fallback only when you've actually hit a compatibility issue, or when the host page mandates iframe-only embeds.