Publishing use case

Catalogs that stay next to the products.

Add a PDF catalog to a reader on the website where customers browse products.

PUBLIC READER · WEBSITE EMBED · 25 MB TOTAL · 7 DAYS

Publish a PDF

No account required. Uploaded documents are public and expire after seven days.

A clear path from document to reader.

Start with a public document, share a direct link and embed the reader in the page where it is useful.

01 / UPLOAD

Choose the document

Upload a PDF up to 25 MB total.

02 / SHARE

Use a reader URL

Readers can open the document directly and share a specific page.

03 / EMBED

Keep the context

Embed the reader on the website visitors already trust.

Live demo

See a live example on this page.

The reader below opens our FOXFIELD sample magazine at the spread closest to this use case — a real embed, not a screenshot. Page through it or search it.

A real embed through the public /embed/v1.js snippet — the same one you get after upload.

For a public catalog.

Use the public reader where the document supports a page, not as a replacement for the information around it.

Use the public flow for public material.

Anonymous uploads are public and expire after seven days. Do not use this upload route for student records, client files, property documents under embargo, unpublished material or any other private content.

When your team publishes regularly. The publishing plan scope covers persistent libraries, private delivery, domain controls, publisher identities and reader analytics beyond this public upload flow.

See plan scope

Questions this page answers.

What publishers ask before they publish this kind of document.

Can a campaign link into the middle of the catalogue?
Yes. Every page has its own address, and an embed can open on a chosen page.
What happens when the catalogue changes?
On a paid plan you can replace the file under the same link, so pages and embeds that already point at it stay correct.

Keep reading.

Where publishers usually go next from here.