PDF Hosting

PDFs are the documents you most need to hand someone reliably — invoices, whitepapers, contracts, spec sheets, ebooks — and the common ways of sharing them all introduce friction. Email providers cap attachments (often around 25MB), so a design-heavy brochure bounces. Google Drive links frequently prompt the viewer to sign in or request access, which kills conversion on a lead-magnet PDF.

Committing a PDF to your web server means serving it from a single origin with no edge caching. files.link gives any PDF a permanent CDN URL that opens inline in the browser's native viewer on the first click, from the nearest edge location. The behavior that matters is the content-type: files.link serves PDFs as application/pdf, so browsers render them in-tab instead of forcing a download or showing a broken blob — exactly what you want for a whitepaper or a viewable invoice.

Uploading is a drag into the dashboard, or for systems that generate PDFs (an invoicing service, a report builder, a contract generator) the three REST calls: POST /v1/files/{folderId} returns {success, urls:[{url,id,...}]}; PUT the PDF bytes to the presigned URL; POST /v1/files/confirm-upload with {ids:[...]}. Persist the returned URL on the order or document record and email or display that link.

The public/private split is the useful part for documents. Marketing PDFs — datasheets, guides, lead magnets — live on permanent public URLs you can put behind a form or paste anywhere. Sensitive documents — a customer's invoice, a signed contract, an HR letter — should be private files served via short-lived signed URLs (10-minute expiry), so the link in an email can't be forwarded and replayed indefinitely, and the document isn't reachable from a guessable path.

Be honest about what files.link does not do: it won't add a password to the PDF itself or apply DRM. If you need a password-protected document, encrypt it locally first (qpdf or your PDF library) before upload, or rely on signed-URL expiry as your access control. Size is generous — up to 1TB per file via multipart — so a 600-page archival manual or a high-resolution print-ready PDF is no problem; the practical ceiling is just how big a download your viewers will tolerate.

Prepaid credits debit by storage and delivery, so a popular ebook costs predictable bandwidth, not a metered per-view charge.