Developer-first Image Storage
Durable Object Storage for Your Original Image Assets
Always-available image storage and CDN delivery — not just on your machine.
Most "image" services are built around on-the-fly transformations, but the asset you actually can't afford to lose is the original — the full-resolution upload before any crop, resize, or recompression. files.link is durable storage for those master image files. Whether you are warehousing 24-megapixel product shots, user avatars, scanned artwork, or camera RAW and HEIC originals straight off a phone, the original byte-for-byte file lives on infrastructure designed to keep it intact, and you decide later what derivatives to generate from it.
The upload flow is three predictable REST calls. First POST /v1/files/{folderId} with your filenames; the response comes back as { success, urls:[{url,id,...}] }. Second, PUT each image's bytes directly to the presigned url you received — no proxying through our API, so a 60MB TIFF or a folder of RAW files goes straight to storage. Third, POST /v1/files/confirm-upload with { ids:[...] } to finalize.
The Authorization header is your raw API key (no Bearer prefix), which makes server-side ingestion from a Node, Python, or Go worker a few lines of code.
Keep originals private when they are pre-moderation user uploads — store them as private files and mint short-lived signed URLs only for the people who should see them. Or mark a folder public and every image gets a permanent link served from the global CDN, so the original doubles as the delivered asset for blogs, catalogs, and docs. Because billing is prepaid credits against storage and bandwidth, a library of large originals that is written once and read rarely stays cheap, and there is no per-transformation meter ticking in the background.
files.link does not resize or re-encode your images — it stores exactly what you send. That is a feature for an archive of masters: the file you download in two years is bit-identical to the one you uploaded. Pair this with the image-cdn page when you also need fast delivery of derivatives, or the image-upload-api page when the priority is the ingestion endpoint itself.
Benefits With No Complexity
Global CDN delivery
Edge-cached worldwide
Signed-URL security
What You Get
Unlimited files
Unlimited storage
Public + Private storage
CDN ready links
Prepaid credits
More coming soon
How files.link Works
1. Upload
2. Copy
3. Use Anywhere
Why Developers Choose files.link
A Better Way to Store & Deliver Files
| Cloudinary | Amazon S3 | Imgix | files.link | |
|---|---|---|---|---|
| Stores byte-identical originals (no forced re-encode) | ||||
| Built-in global CDN on the same URL | ||||
| No per-transformation fees | ||||
| Private originals via expiring signed URLs | ||||
| Prepaid credits (no surprise overage bill) | ||||
| Direct-to-storage presigned upload |
Calculate Your Needs
Storage
Egress
CDN Bandwidth
Start Storing Images Globally
- Global CDN delivery
- Edge-cached worldwide
- Signed-URL security
- Unlimited files
- Unlimited storage
- Public + Private storage
- No subscription — prepaid credits keep spend predictable