Simple & Reliable File Storage

Not every storage need fits a niche. Sometimes you just need a dependable place to put arbitrary files and get them back fast — mixed media, archives, exports, binaries, whatever your app produces. files.link is that general-purpose layer: no format restrictions, no assumptions about what's inside the file, just durable storage with a global CDN and a REST API that's the same whether you're storing a 4KB JSON blob or a 200GB archive.

The contract is three calls. POST /v1/files/{folderId} with your filenames returns { success, urls:[{url,id,...}] }. PUT each file's bytes to its presigned url — direct to storage, so big files don't bottleneck through our API. POST /v1/files/confirm-upload with { ids:[...] } to commit. Authentication is your raw API key in the Authorization header, no Bearer prefix, which keeps server-side integrations short.

Files you mark public get a permanent CDN link; files you keep private are reachable only through expiring signed URLs you mint on demand.

What makes this a comfortable default rather than a compromise: organization and billing. Projects and folders give you real structure instead of a flat namespace of prefixed keys, and each project carries its own API key for isolation. Billing is prepaid credits against storage and bandwidth with no per-request, per-upload, or egress surcharge — so a month where traffic spikes costs you bandwidth, not a bill you can't predict. There are no monthly minimums and no tier you grow out of.

Think of this as the hub. When a use case sharpens, there's a focused page: image-storage and video-storage for media masters, document-storage for office files, file-storage-with-cdn for the delivery angle, serverless-file-storage for Lambda-style backends, and how-to-store-user-uploads for ingesting from your users. Comparing the economics against a hyperscaler? s3-alternative and no-egress-fees-storage lay out the trade-offs. cloud-file-storage-api covers the API surface in depth.