Developer-first Document Storage

Business documents are not media assets — they are records. A signed contract PDF, an exported XLSX financial model, a DOCX proposal, a PPTX board deck: these need to be retrievable years later, access-controlled, and organized so a human can actually find the right version. files.link gives your application durable storage for office documents with per-file privacy and a clean folder hierarchy, rather than dumping everything into one undifferentiated pile.

Most documents should not be public. Store them as private files and serve them only through signed URLs that expire after a short, configurable window (10 minutes by default). Your backend mints a fresh URL each time an authorized user opens the file, so a leaked link is useless minutes later — far safer than emailing the document itself. For documents that are genuinely public (a published whitepaper, a price list PDF), mark the folder public and you get a permanent CDN-backed link instead.

The API is three REST calls: POST /v1/files/{folderId} returns { success, urls:[{url,id,...}] }, you PUT each document's bytes to its presigned url, then POST /v1/files/confirm-upload with { ids:[...] }. Auth is your raw API key. A document-management feature in your app — invoices, reports, client uploads — becomes a thin wrapper over these endpoints, with projects giving you isolated API keys per tenant or per team so one customer's documents can never be addressed by another's key.

Organization is first-class: projects at the top, folders beneath, so you can mirror a structure like client → year → matter without inventing your own prefix conventions. Every file is encrypted at rest and moves over TLS in transit. For document-heavy verticals, see invoice-storage, legal-document-storage, and file-storage-for-legal; for the raw file formats those documents often wrap, see csv-file-storage and xml-file-storage.

Billing is prepaid credits, so a slowly-growing document vault stays predictable with no per-request office-suite surcharges.