Embedding keeps readers on your domain’s story: same header, same analytics, same trust signals—while the flipbook does the heavy lifting for page turns and zoom.
Most teams embed with an iframe pointed at the hosted viewer URL. Your CMS wraps the iframe in a content block; the flipbook loads inside it. Alternatively, a prominent button can open the full viewer in the same tab—useful when you want the publication to feel like its own destination.
The PDF Flip viewer scales to the space you allocate. If the iframe is only a few hundred pixels tall, readers see a postage-stamp book and wonder why the controls feel cramped. Allocate enough vertical space for the spread plus the toolbar—test on a laptop and a phone so the layout still makes sense inside your page grid.
One catalog per iframe works until you have a resource center with a dozen PDFs. A bookshelf library shows covers on a shelf so people browse instead of scrolling past twelve separate embeds.
For how the viewer itself behaves on small screens—not your CMS CSS—read responsive flipbook design.