Back to help center
Technical

How Folio finds and stores source PDFs

A look under the hood at open-access fetching, private storage, and signed URLs.

F

Folio Team

November 8, 2026 3 min read

For the curious, and the security-minded, here's how the reader gets its PDFs.

Open-access first

When you add a source without uploading a PDF yourself, Folio looks for one in the background, in this order: a direct arXiv link, then bioRxiv or medRxiv, then an open-access PDF address already on the source's record, then open-access locations found through the DOI at Unpaywall, OpenAlex and Semantic Scholar, and finally a best-effort look at the source's own landing page for a linked PDF. We only fetch copies that are openly available; we don't bypass paywalls. If a free copy exists but its publisher doesn't allow automated downloads, the paper's page links to it so you can save it and upload it yourself. When you upload your own PDF, Folio skips this search and keeps your file.

Downloaded server-side, stored privately

PDFs are fetched on our servers (never cross-origin in your browser), checked to be genuine PDFs and no larger than 25 MB, and stored in a private bucket. Nothing is public.

Read with its page numbers

Once a PDF is stored, Folio reads its text page by page and keeps the page numbers, along with the printed page labels when the PDF has them. It splits the text into passages and indexes them, which is how the Library's search, Find in this paper, Scholar and the editor's claim checker can point you to the page a passage is on.

For a source with a DOI, Folio checks the retraction record when you add it and again every week. The paper's page in the Library sums all of this up in one line: whether the record matches Crossref, whether a retraction was found and when it was last checked, and how much of the text Folio has (for example, Full text, 12 pages).

Served through short-lived signed URLs

When you open the reader, Folio mints a signed URL for your file, valid for one hour, after confirming you own the source. Links expire, and one user can never reach another's files.

Loaded same-origin

The PDF rendering engine is served from Folio itself rather than a public CDN, so the reader keeps working on restricted networks. Your PDF and the address of what you're reading never go to a third party. The one outside request is for shared font and character-map files the renderer needs for some PDFs, which load from a public CDN (unpkg.com) and carry nothing about your document.

Was this helpful?

Discussion

No comments yet. Be the first to share your thoughts.