A reader that behaves like one
Page navigation, in-document search, zoom, fullscreen, text selection, a table of contents from the PDF outline and a light, dark or automatic theme. Every page has its own shareable link.
How the reader worksBuilding in public
Three honest answers on one page: today you can upload a public PDF and get a reader and embed without an account. We are building the publisher layer — libraries, analytics, API, teams and custom domains — in public. Paid plans open when the whole purchase path works, and the founding Lifetime Team offer is reserved for the first publishers.
Upload one PDF up to 25 MB, share its reader URL or add it to your site with one snippet. The anonymous upload is public and expires after seven days.
Page navigation, in-document search, zoom, fullscreen, text selection, a table of contents from the PDF outline and a light, dark or automatic theme. Every page has its own shareable link.
How the reader worksThe stable v1 snippet creates a lazy, isolated reader iframe and adapts its height safely, so your page keeps its own speed and styles.
About the embedReviewed reader controls in all 24 official EU languages plus major world languages. The document stays yours; the controls meet the audience.
Reader languagesAnonymous uploads are validated before publication and expire after seven days. Use this flow only for material you can publish openly.
Publishing boundarySigning in keeps a document past its seven days. A publishing plan adds the parts a returning publisher needs. These are live, not planned.
Claim a document into a free account and it stops expiring. The public link, page links and existing embeds continue to work.
See what a plan addsShared workspaces with owner, editor and viewer roles, so colleagues work on the same documents without sharing one login.
On a paid plan, upload a corrected version of a document. Readers get the new file at the address they already have.
A paid plan sets the publisher name, brand colour and theme per document. White-label removes the EmbedFox attribution.
Short notes on changes that affect a publisher or reader. The full history remains in the changelog.
These are the publisher outcomes we are working toward, in the order that serves teams who publish repeatedly. Each layer opens when it is safe and supportable — not as an early promise.
Decide where a document may appear: allowed embed domains, a preview limited to the first pages, and an email gate for the rest — with export to your own tools.
Protection directionSee how a document is opened and read — per page and over time — without cookie banners and without building a profile of any reader.
Upload from the systems that already prepare your documents, and let your website or CRM react to publishing events with signed webhooks.
API directionSave a publisher name, logo and brand colours once as an identity, then assign it to any document instead of setting the appearance again each time.
Serve readers from a subdomain you control, so documents live fully inside your web presence.
Publisher, Team and White-label limits are published so you can assess the product before sales start. Purchases open when subscription, access and billing support work together — the roadmap above is what those plans buy.
We publish delivered changes and product status openly, so you can judge pace and direction before you rely on us.