WebflowEmbedFlipbookWeb DesignAgencies

Webflow Flipbook Embed

Put a page turning flipbook into a Webflow build with one HTML Embed element. Upload the PDF, copy the snippet, drop it into a wrapper div and size it at each breakpoint like anything else in the project. The document reads on the page instead of downloading, and it keeps your type scale and your colours around it. Made for designers and agencies who own the whole front end. Free to use, with no watermark, no subscription to hand over at launch, and no branding you have to explain to a client.

Webflow Flipbook Embed

How to Embed a Flipbook in Webflow

1

Upload and Style the PDF

Upload the exported PDF to Flipbooks AI. Set the page turn, add the logo, match the control colours to the project palette, and add any links the pages need. The preview shows exactly what a visitor will read.

2

Copy the Embed Snippet

Open the share options and copy the snippet. It is a short block of HTML, well inside the character limit a Webflow Embed element accepts, and there is nothing in it you need to edit by hand.

3

Place It and Size the Wrapper

Add an HTML Embed inside a div block, paste the snippet, and give the wrapper a class with a max width and a height. Check it in Preview, adjust the height at tablet and mobile, then publish.

How to Create a Webflow Flipbook Embed Code

How to Create a Webflow Flipbook Embed Code

Start with the PDF the design already produced. Upload it to Flipbooks AI and an interactive preview appears immediately, so you can read the document the way a visitor will before it goes near the project. Choose the page turn style, add a logo, set the control colours from your palette, and add links inside the pages. Decide whether the flipbook is public or password protected. Then open the share options and copy the embed snippet. It is a short block of HTML, well under the fifty thousand character limit an Embed element accepts, and you never have to edit it by hand.

What Is a Webflow Flipbook Embed?

A Webflow flipbook embed is a hosted page turning reader placed inside your own layout through an HTML Embed element. You upload a PDF to Flipbooks AI, it hosts the reader, and it hands you a short snippet. You paste that snippet into an Embed element, wrap it in a div you can style, and from then on the document lives inside your sections with your nav above it and your footer below. Readers move through spreads without leaving the page, and the file never touches your Webflow assets, so a hundred page catalogue does not sit in the project weighing down every publish.

What Is a Webflow Flipbook Embed?
What Is a Webflow Flipbook Embed?
What Is a Webflow Flipbook Embed?
What Is a Webflow Flipbook Embed?

Where the HTML Embed Element Goes

In the Designer, add an HTML Embed from the Add panel and place it inside a div block rather than dropping it straight into a section. Paste the snippet into the code editor and save it. Give the wrapper a class so the size lives in your style sheet instead of on the element, and put the wrapper inside a normal content container so it inherits the padding the rest of the page uses. That one habit is the difference between an embed that survives a redesign and one that has to be repositioned every time the section around it changes.

Where the HTML Embed Element Goes

Trusted by Fortune 500 Companies

Wrapping the Embed for Clean Layout

Wrapping the Embed for Clean Layout

Give the wrapper a class such as embed wrapper, set width to one hundred percent, add a max width that matches your content column, and centre it with auto margins. Height is the only value the reader cannot decide for you, so set one that suits the page shape: a landscape catalogue wants a wide, shorter frame and a portrait booklet a taller one. Keep the values on the class rather than the element, and any second flipbook on the site inherits the same sizing. Add a little vertical padding around the wrapper so the book is not fighting the section above it.

Why an Embed Beats a Linked PDF Asset
Why an Embed Beats a Linked PDF Asset
Why an Embed Beats a Linked PDF Asset
Why an Embed Beats a Linked PDF Asset

Why an Embed Beats a Linked PDF Asset

Uploading the PDF to Webflow assets and linking it is quick, and it is also where the document stops being part of the site. The browser hands the file to a viewer with its own chrome, the type is not yours, the nav is gone, and on iOS a good share of readers never come back. An embedded reader keeps the visitor inside the layout you built, keeps the links inside the pages working, and reports back on how far people got. When a client asks what the case study page achieved, a linked asset gives you nothing to say. The embed gives you page by page reading data.

Setting Height Across the Breakpoints

Height is where most embeds go wrong, and Webflow makes it easy to fix because inherited values cascade down. Set the base height first, then move to tablet and reduce it, then to mobile landscape and mobile portrait. Viewport units work well here: a height in vh keeps the reader proportional to the screen rather than to a number you picked on a large monitor. Check every breakpoint in Preview rather than trusting the canvas, and pay attention to the smallest one, since that is where a two page spread becomes unreadable and single page mode earns its place.

Setting Height Across the Breakpoints

Webflow Flipbook Embed Alternatives

Issuu

Issuu

  • Free & Unlimited
  • No Watermarks
  • One Line Embed
  • Responsive Reader
  • Mobile Ready
  • Clickable Links
  • Fast Loading
  • Password Protection
  • Instant Updates
  • Reader Analytics
Flipbooks AI

Flipbooks AI

  • Free & Unlimited
  • No Watermarks
  • One Line Embed
  • Responsive Reader
  • Mobile Ready
  • Clickable Links
  • Fast Loading
  • Password Protection
  • Instant Updates
  • Reader Analytics
Heyzine

Heyzine

  • Free & Unlimited
  • No Watermarks
  • One Line Embed
  • Responsive Reader
  • Mobile Ready
  • Clickable Links
  • Fast Loading
  • Password Protection
  • Instant Updates
  • Reader Analytics
Publuu

Publuu

  • Free & Unlimited
  • No Watermarks
  • One Line Embed
  • Responsive Reader
  • Mobile Ready
  • Clickable Links
  • Fast Loading
  • Password Protection
  • Instant Updates
  • Reader Analytics
Why the Designer Canvas Shows a Placeholder

Why the Designer Canvas Shows a Placeholder

Webflow does not run custom code on the canvas, so an Embed element shows a placeholder rather than the flipbook while you are designing. That is expected and not a fault in the snippet. Use Preview to see it render, and publish to staging when you want to test it on a real phone. This is the one habit that differs most from embedding on Squarespace or Wix, where the block previews in place inside the editor. In Webflow you design the wrapper blind and confirm it in Preview, which is why setting the size on a class rather than the element saves so much back and forth.

Features That Suit a Webflow Build

The reader is responsive inside whatever container you give it, so a wrapper with a max width and a sensible aspect ratio is usually all the CSS it needs. You can set the page turn style, add a logo, and match the control colours to the swatches already in the project. Inside the pages you can place clickable links to a CMS driven product page, a booking form or a mailto, embed a short film, and add a table of contents for a long document. Nothing is watermarked and nothing is capped, so a fifteen page brand guide and a two hundred page catalogue behave the same way.

Features That Suit a Webflow Build
Features That Suit a Webflow Build
Features That Suit a Webflow Build
Features That Suit a Webflow Build

Custom Code Needs a Paid Site Plan

This is worth knowing before you promise a date. Webflow only publishes custom code, including whatever sits inside an HTML Embed element, on sites with a paid Site plan. On the free staging domain the embed will not appear at all, which looks exactly like a broken snippet if you do not know the rule. Nothing about the flipbook changes: the same snippet works the moment the Site plan is live. If a client is still deciding, link to the hosted flipbook from a button in the meantime and swap the button for the embed once the plan is active.

Custom Code Needs a Paid Site Plan
Driving Flipbooks From the Webflow CMS

Driving Flipbooks From the Webflow CMS

For a site with many documents, put the flipbook link in a plain text field on the collection instead of hard coding a snippet per page. Inside an Embed element on a collection page or in a collection list, you can insert that field into the code, so every item renders its own reader with no extra design work. A magazine gets one issue template that covers every back issue. A property site gets one unit template that covers every brochure. Adding a document becomes a CMS entry, which is the point at which a client can genuinely run the section themselves.

Good for Studios, Agencies and Freelancers
Good for Studios, Agencies and Freelancers
Good for Studios, Agencies and Freelancers
Good for Studios, Agencies and Freelancers

Good for Studios, Agencies and Freelancers

This is aimed at the people who build Webflow sites for a living. A brand studio embeds the guidelines document instead of shipping a download link. An agency embeds a capability deck on the services page and reports on who read it. A property developer site embeds a specification brochure per unit. A magazine embeds each issue on a CMS templated page. A recruitment site embeds the benefits handbook. The work is the same in every case: one snippet, one wrapper, one class, and a document that behaves like part of the design system instead of an attachment bolted onto the end of it.

Matching the Reader to Your Style Guide

An embed that ignores the design system is the thing a designer notices first. Set the background behind the pages to a colour from your palette, match the control colours to your buttons, add the client logo, and choose a navigation style that suits the rest of the interface. Keep it quiet on a typographic site and let the colour carry on a bolder one. Multiple languages are supported, so a brand running two markets can embed a localised version on each locale page and keep the surrounding layout identical.

Matching the Reader to Your Style Guide

Who Embeds Flipbooks in Webflow

2456+

Web Designers

6

Design Agencies

13

Freelancers

24

Brand Studios

65

Marketing Teams

9

Publishers

Interactive Elements Inside the Pages

Interactive Elements Inside the Pages

Once the reader is on the page, the document can do things the printed version never could. Link a product shot to its CMS item, drop a booking link on a services spread, put an email on the back cover, or embed a short film inside a page. A table of contents lets someone jump to the section they came for, and search helps in a long catalogue. These are the details that decide whether a visitor reaches the last page or leaves at the third, and they cost nothing to add once the file is uploaded.

Responsive Across Every Webflow Breakpoint

Webflow gives you a base breakpoint plus tablet, mobile landscape and mobile portrait, and any wide breakpoints you have added above it. The reader is fluid inside its container, so the work is in the wrapper rather than the embed. Set a max width and a height on the base breakpoint, then check tablet and both mobile widths and adjust the height where a spread starts to feel cramped. On narrow screens, switching the flipbook to single page mode is usually better than shrinking a two page spread. Pinch to zoom works, swiping works, and nothing asks the visitor to install anything.

Responsive Across Every Webflow Breakpoint
Responsive Across Every Webflow Breakpoint
Responsive Across Every Webflow Breakpoint
Responsive Across Every Webflow Breakpoint

Page Speed and the Embedded Reader

Webflow projects are usually already carrying webfonts, interactions and a lot of imagery, so anything heavy gets blamed for the whole page. The reader is hosted separately and loads in its own frame, so it does not add megabytes to your Webflow assets or slow the rest of the page down. Pages are compressed carefully, the first spread appears quickly and the remainder streams in behind it. On a phone on weak signal that is the difference between a document being read and a visitor going back to the search results.

Page Speed and the Embedded Reader
SEO Around an Embedded Document

SEO Around an Embedded Document

Be realistic about what an embed does for search: the reader is a frame, so treat the page around it as the thing being indexed. Give the page a proper heading, a short introduction, a summary of what the document covers, and a paragraph or two of real text using the words people actually search for. Fill in the page title and meta description in page settings rather than leaving the defaults. Done that way, an embedded brochure gives a thin page genuine content and a reason for a visitor to stay, which is the part search engines can actually see.

A Free Embed You Can Hand to a Client
A Free Embed You Can Hand to a Client
A Free Embed You Can Hand to a Client
A Free Embed You Can Hand to a Client

A Free Embed You Can Hand to a Client

Flipbooks AI is completely free, and the things you would normally have to justify in a proposal are included: no watermark across the spreads, no page cap, no limit on how many readers you embed across a site, and no charge for password protection or analytics. That matters most at handover. A client who has just signed up for a Webflow Site plan does not want a second subscription attached to one page of their site, and you do not want to be the person who chose the tool that starts nagging them in month seven. Build it, hand it over, and nothing expires.

Fits the Tools in Your Design Stack

Nothing new enters the workflow. Export the PDF from Figma, Adobe InDesign, Affinity Publisher, Canva or Google Slides and upload it as it is. Link from inside the pages to a Webflow CMS page, a Calendly booking, a Typeform, a Shopify product or a newsletter signup. Drop the same snippet into a second Webflow project, a client site on another platform, or a landing page built elsewhere. The flipbook is a hosted page with a link and a snippet, so it slots into whatever pipeline the studio already runs.

Fits the Tools in Your Design Stack

What Designers Say About the Webflow Embed

We build Webflow sites for consumer brands and the lookbook was always a linked asset that nobody could measure. One Embed element inside a wrapper class solved it. The reader inherits the container, the client changes the PDF themselves, and for once the monthly report has a number in the documents section.

Marketing team
Marketing team

Product catalogs

The CMS trick is what sold me. I put the flipbook link in a text field on the issues collection and inserted it into the Embed on the template. Twelve back issues render from one page now, and the editor adds a new one without ever opening the Designer or asking me for a favour.

Studio owner
Studio owner

Client lookbooks

I lost an afternoon once wondering why the embed was blank on the staging domain before I understood that Webflow does not publish custom code without a Site plan. Once the plan was live it appeared instantly. Worth knowing before you demo a build, and nothing to do with the snippet itself.

School office
School office

Newsletters and programmes

As a freelancer, handing over anything with a monthly fee attached is a conversation I would rather not have. This has no plan and no watermark, so the brand guide sits on the studio page looking like part of the design system, and there is nothing for the client to renew in six months.

Independent designer
Independent designer

Portfolio flipbooks

Private Flipbooks for Client Review

Private Flipbooks for Client Review

Not every document should be public while it is still being argued over. Publish it with password protection and only the people you send the password to can open it, which is a tidy way to share an unreleased collection, a pitch document or a price list meant for the trade. You can also turn off downloading so the pages stay in the reader rather than travelling as a file. When it is signed off, remove the password and the same link becomes the public one, with no re upload and no new snippet.

Share the Same Flipbook Outside the Site

The embed is one surface, not the only one. Every flipbook also has a plain hosted link, so the same document can go in a newsletter, a proposal, a direct message or an Instagram bio without exporting anything again. Print a QR code for an event stand or a printed leaflet and it opens the same book. Put the reader on a second page, on a campaign landing page, or on a site you built somewhere else entirely. Because there is one file behind all of it, correcting a page corrects every route to it at once, which is the part that saves time on a live campaign.

Share the Same Flipbook Outside the Site
Share the Same Flipbook Outside the Site
Share the Same Flipbook Outside the Site
Share the Same Flipbook Outside the Site

Building a Library of Past Issues

Every flipbook you publish stays live, so a site can carry a real archive rather than a folder of downloads. Keep every issue of the magazine, every quarterly report, every seasonal catalogue, each with its own link, and list them from a CMS collection so the archive page builds itself. Visitors browse back through the work, and the studio has a record of what shipped and when. Relaunching a popular edition means duplicating a flipbook and changing a few pages instead of rebuilding it from the original file.

Building a Library of Past Issues

Compare Ways to Publish a Flipbook

ApplicationRatingUnlimited CreditsUsage RatingDescription
10/10Yes1

Flipbooks AI hands you a snippet that drops into an HTML Embed element, a reader that is fluid inside your wrapper, clickable links to your CMS pages, password protection and per page reading data, all free and unlimited. It is built to be handed to a client without a subscription attached to it.

FlipHTML5

5.2/10No2

FlipHTML5 has been converting PDFs into flipbooks for a long time and its effects library is deep, which suits people who want to tune the reader itself. The free tier brands your pages and holds back the statistics, so a client build usually ends up on a paid plan.

Issuu

7.1/10No3

Issuu is a publishing platform with a reader most people already recognise and an audience of its own, which is a real advantage for a magazine. The free tier wraps your document in Issuu branding and caps uploads, so a clean embed inside a designed site normally means paying.

Heyzine

8.3/10No4

Heyzine is fast and pleasant to use, and it produces a good looking book from a PDF with almost no configuration. The free plan limits how many books you keep and adds its own mark, and the styling control a design system needs sits in the paid tiers.

Publuu

6.4/10No5

Publuu is well built, with clean hotspot linking and useful tracking. The pieces that matter on a client project, particularly detailed statistics and longer documents, are part of a paid plan, so it is hard to specify on a build where nobody wants a recurring cost.

Flipsnack

7.8/10No6

Flipsnack is a capable editor as much as a converter, and designing pages inside it can suit a team without an InDesign licence. Free use is limited, and removing the branding and opening the analytics means a monthly fee that has to be justified to whoever pays it.

Webflow Lightbox

6.9/10No7

The native lightbox is reliable, weightless and already in the project, which counts for a lot. It shows images or video in an overlay rather than a document, so there is no spread, no page turn, no clickable page and nothing reported back about what was read.

Self Hosted PDF.js

8.1/10No8

Rolling your own viewer with PDF.js gives you total control and no third party in the stack, which some teams require. It also means hosting the file, writing the viewer chrome, maintaining it, and building any analytics yourself, which is a project rather than an afternoon.

Google Drive Preview

6.5/10No9

A Drive preview is free, instant and needs no account work from your side. The frame carries Google interface around your pages, the typography is not yours, and dropping a visitor into an unrelated product undoes the care the rest of the page was built with.

Direct PDF Asset Link

7.6/10No10

Linking the asset straight from Webflow is the fastest option and costs nothing. It also hands the visitor to a browser viewer, adds the file weight to your project, renders differently on every device, and reports nothing about whether anyone read past the cover.

Client Updates Without a Designer

Client Updates Without a Designer

The best outcome for both sides is a client who can correct their own document. Once the Embed element is in place, the snippet never changes again. They upload a revised PDF, publish the flipbook, and the page shows the new version without anyone opening the Designer. A corrected price, a discontinued item, a new address on the back page: none of it becomes a ticket. For a studio on a retainer that removes a class of small jobs that were never worth invoicing and always worth doing quickly.

Reading Data You Can Put in a Report
Reading Data You Can Put in a Report
Reading Data You Can Put in a Report
Reading Data You Can Put in a Report

Reading Data You Can Put in a Report

A hosted PDF tells you a file was requested and nothing more. Flipbooks AI shows opens, time spent per page, and the page where readers stop turning. That turns a design decision into an argument you can make: the case studies belong before the team page, the price list is losing people on page three, the last spread is where the enquiry link should sit. For an agency writing a monthly report, it is a section that used to be guesswork. For a freelancer, it is evidence the page you charged for is doing something.

An Embed That Survives a Site Rebuild

Documents outlive layouts. When the site is redesigned in two years, the flipbook link and the snippet are still valid, so the reader moves to the new template with a copy and paste rather than a migration. The reader itself is built on current web standards and maintained as browsers change, so nothing decays into the grey box that old viewers left behind on so many sites. Everything is hosted, so there is no dependency to update inside the project and nothing in the Webflow build that can quietly stop working.

An Embed That Survives a Site Rebuild

Frequently Asked
Webflow Flipbook Embed

What is a Webflow flipbook embed?

It is a hosted page turning reader placed inside your Webflow layout with an HTML Embed element. Flipbooks AI hosts the document for free, so visitors read a catalogue or brochure inside your own page instead of downloading a file from your assets.

Why does the flipbook not show in the Designer?

Webflow does not run custom code on the canvas, so an Embed element shows a placeholder while you design. Use Preview to see it render, and publish to staging to test it on a real device. The snippet is fine, the canvas simply does not execute it.

Do I need a paid Webflow Site plan to publish it?

Yes, for the embed. Webflow only publishes custom code on sites with a paid Site plan, so on a free staging domain the reader will not appear. Until the plan is live, link to the hosted flipbook from a button and swap it later.

Is Flipbooks AI really free for client work?

Yes. It is completely free with no watermarks, no page limits, and no cap on how many readers you embed. Customization, password protection, sharing and analytics are all included, so nothing new appears on the client invoice at handover.

Can I drive flipbooks from the Webflow CMS?

Yes. Store the flipbook link in a plain text field on the collection and insert that field into the Embed element on the collection page. Every item then renders its own reader, so adding a new issue or brochure is a CMS entry rather than a design job.

How should I set the height across breakpoints?

Put the size on the wrapper class, not the element. Set a base height, then reduce it on tablet and both mobile breakpoints. Viewport units keep the reader proportional to the screen, and single page mode reads better than a shrunken spread on a phone.

Can the client update the PDF without a designer?

Yes. The snippet never changes. They upload a revised PDF, publish the flipbook, and the embedded reader shows the new version straight away without anyone opening the Designer or republishing the Webflow site.

What reading data comes back from the embed?

You get opens, time spent on each page, and the page where readers stop turning. It is enough to say which spread is losing people and where a call to action belongs, which is more than a linked PDF asset has ever reported.

Have more questions?

If you still have questions or want to explore more details about our features, limitations, and usage, we invite you to visit our full FAQ page.