File Storage for Gaming
Ship Game Assets and Updates With Low-Latency Delivery
Store game assets, updates, and user content with low-latency global delivery.
A game ties together several distinct file workloads: large initial downloads, incremental patches, streamed asset bundles and textures, player-generated content, and a graveyard of old builds you must retain but rarely touch. files.link can sit behind most of that with one API and an integrated global CDN. Patches and asset bundles uploaded through the API are served from edge locations close to the player, so a download in Tokyo and a download in Toronto both pull from nearby rather than from a single distant origin — important when a launch-day update hits every region at once and you do not want one origin saturated.
The delivery is bundled with storage, so you are not separately operating a CDN and paying egress as its own escalating line item the way you would composing a raw object store with a separate edge tier; with files.link the bandwidth is drawn from the same prepaid-credit balance as storage, which keeps a viral spike from turning into a surprise transfer bill.
Player-generated content — custom levels, avatars, screenshots, mod uploads — flows through your game backend using the three-call pattern: request a presigned target with POST /v1/files/{folderId}, have the client or server PUT the bytes, then POST /v1/files/confirm-upload to finalize, after which the asset is a CDN-served URL you can hand to other players.
Access can be public via permanent links for shared community content, or private via signed URLs when a file should only reach specific players. For the long tail, a cold storage tier lets you keep deprecated builds, old event assets, and superseded patch sets for rollback or compliance at a much lower rate, still reachable through the same API when you need to resurrect one.
One honest caveat: a CDN is for distributing files, not for real-time multiplayer state — matchmaking, position updates, and netcode belong on your game servers, not here. For everything that is fundamentally a file being shipped to players, though, the consolidated storage-plus-delivery model removes a lot of the plumbing studios usually hand-build.
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
| Object store + separate CDN | Google Cloud Storage | files.link | |
|---|---|---|---|
| Built-in CDN (no separate setup) | |||
| Simple REST API for client + backend | |||
| No separate egress billing | |||
| Prepaid credits billing | |||
| Permanent links for shared UGC | |||
| Cold storage tier for old builds |
Calculate Your Needs
Storage
Egress
CDN Bandwidth
Start Hosting Game Assets
- Global CDN delivery
- Edge-cached worldwide
- Signed-URL security
- Unlimited files
- Unlimited storage
- Public + Private storage
- No subscription — prepaid credits keep spend predictable