Embed

Embedding is the process of placing a flipbook or document viewer directly inside another web page using an [iframe](/glossary/iframe) or JavaScript snippet. The embedded content renders inline within the host page, retaining full interactivity — page flipping, zoom, search, and navigation controls all work exactly as they do when viewing the publication on its own URL. Because the viewer loads inside the host page's DOM, readers never leave your site or see a third-party domain in their browser bar.

When you embed a publication instead of linking to it, you keep visitors inside your own browsing experience. This matters for three reasons. First, readers who stay on your site are more likely to take a next step — filling out a form, clicking a [CTA button](/features/cta-buttons), or exploring related pages. Second, engagement metrics like time-on-page and [scroll depth](/glossary/scroll-depth) stay attributed to your domain, which benefits SEO. Third, embedded content appears in the natural flow of the page, making it feel like part of your brand rather than an external resource.

FlipLink's [sharing and distribution](/features/sharing-and-distribution) feature generates a ready-to-paste [embed code](/glossary/embed-code) for every publication. The default option is a [responsive embed](/glossary/responsive-embed) iframe that scales to fit any container width, so the flipbook looks correct on desktops, tablets, and phones without manual sizing. All configured features — CTA buttons, [lead capture](/features/lead-capture) forms, [analytics](/features/analytics-and-insights) tracking, and [password protection](/features/password-protection) — work inside the embed. For platforms that block iframes (some email clients and social networks), FlipLink offers a [clickable image embed](/features/clickable-image-embed) as a fallback: a cover thumbnail that opens the full flipbook in a new tab. You can also restrict where your publication can be embedded using [domain whitelisting](/glossary/domain-whitelisting).

An embed link is typically delivered as an HTML `<iframe>` tag pointing to the publication's hosted URL. The iframe runs in a sandboxed browsing context, meaning it cannot access the parent page's cookies or JavaScript scope — this provides a layer of security for both the publisher and the host site. FlipLink's embed code includes `allow="fullscreen"` so readers can expand the viewer, and uses `loading="lazy"` to defer loading until the iframe enters the viewport, which avoids slowing down the host page's initial render. For single-page applications or CMS platforms that strip iframe tags, a JavaScript embed snippet is available that dynamically creates the iframe after the DOM loads.

- **Match container width to content purpose.** A full-width embed works well for catalogs and magazines. For supplementary content within a blog post, a narrower container (600–800px) keeps the embed proportional to the surrounding text. - **Use lazy loading.** If you embed multiple flipbooks on a single page — for example, a resource library — lazy loading prevents all of them from requesting assets simultaneously. - **Set a minimum height.** Without a minimum height, the iframe can collapse to zero on some CSS frameworks. A value of 400–500px prevents layout jumps while the content loads. - **Enable domain whitelisting.** If your publication contains sensitive or gated content, restrict embedding to your own domains so it cannot be iframe-jacked by third parties. - **Test on mobile.** Responsive embeds adapt to width, but always verify touch interactions (pinch-to-zoom, swipe-to-flip) work correctly on actual devices.

**Can I embed a FlipLink flipbook on any website builder?** Yes. Any platform that lets you add custom HTML — WordPress, Wix, Squarespace, Webflow, Shopify, or a hand-coded site — supports FlipLink's iframe embed code. For platforms that use block editors, paste the code inside an HTML or "Custom Code" block. **Does embedding affect my page speed?** FlipLink's embed code uses lazy loading by default, so the flipbook only loads when a visitor scrolls near it. The initial page load is not affected. Once the iframe loads, assets are served from FlipLink's CDN, which keeps delivery fast regardless of the reader's location. **What is the difference between embedding and link sharing?** Embedding displays the flipbook directly on your page so readers interact with it inline. [Link sharing](/glossary/link-sharing) sends readers to a separate URL where the flipbook opens full-screen. Embedding is better for keeping visitors on your site; link sharing is better for channels like email and messaging where inline rendering is not possible.