Product capability
Embed the reader, not a platform
The versioned embed script loads an isolated iframe lazily and keeps its height in sync without taking visitors away from your site.
Publish a PDFReader on your website.
The versioned v1 loader creates a lazy, isolated iframe and accepts only validated height messages from its own reader.
- One container element and one script tag. Only
data-embedfoxis required; the rest of the page keeps its own styles, scripts and loading speed. - The iframe is created lazily as it approaches the viewport, so a long page does not pay for a reader nobody scrolled to.
- The reader reports its height only to its matching embed, and the loader accepts only validated messages from its own reader.
-
data-embedfox-pageopens the embed on a chosen page, so a catalogue can start at its spread instead of the cover. - Several embeds can live on one page; each mounts its own isolated reader and resizes independently.
What it does not do yet.
Naming the edge is more useful than implying there is none. These are on the product roadmap, not in the product.
- Restricting which domains may embed a document, and signed embed sessions for a private page.
- Serving the reader from your own subdomain instead of the EmbedFox public content origin.
Live demo
This is what your readers get.
FOXFIELD is a fictional field journal we publish through the same pipeline as any customer document. The reader below is a real embed — page through it, search it for “fox”, zoom in.
For publishing over time
Control where readers appear.
Domain locks, custom domains, private links and publisher-controlled appearance let you decide where readers appear.
Delivery status for this capability lives on the product roadmap; delivered changes appear in the changelog.
Keep reading.
The pages that answer the next question about this capability.