Game Asset Hosting

Web and downloadable games live or die on asset delivery: the first scene shouldn't stall while a sprite atlas trickles in, and a patch shouldn't force players to re-download the whole bundle. files.link is the CDN origin your build pipeline targets — not a game portal, but a plain REST endpoint you call from a post-build step. The flow fits CI naturally: after your Unity, Godot, or Phaser build emits its assets, a script runs the three-call upload (POST /v1/files/{folderId} returns {success, urls:[{url,id,...}]}; PUT each asset to its presigned URL; POST /v1/files/confirm-upload with {ids:[...]}), captures the returned CDN URLs, and writes them into your asset manifest or remote-config JSON.

At runtime the game pulls from the nearest edge instead of your origin. Concrete pipelines map cleanly. Unity Addressables: build your content catalog and bundles, upload the .bundle files and catalog_*.json, then set the Addressables RemoteLoadPath to the files.link CDN URLs so the engine streams content from the edge. Phaser/PixiJS: upload your texture atlases (the packed PNG plus the JSON frame data), audio sprites, and tilemaps, and point your preload() loader at the CDN URLs.

Godot: upload exported .pck/.zip packs or individual resources and load them with ProjectSettings/load_resource_pack against the hosted URL. Because files.link serves the exact bytes you upload with correct content-types, binary formats — WebGL .wasm and .data, compressed .br/.gz bundles, .ogg/.mp3 audio, .glb models — all download cleanly via curl on the first try, which matters when you're debugging a loader in CI.

Versioning is up to you and works either way: ship immutable filenames per build (atlas-7f3a.png) so CDN caches never serve stale content and old clients keep working, or overwrite in place and let cache TTLs expire. Public assets get permanent URLs; premium DLC or unreleased content can sit in private files behind signed URLs so a leaked manifest path doesn't hand out paid content.

Billing is prepaid credits debited by storage and delivery — crucially there are no per-play or per-download fees, so a game that suddenly gets a hundred thousand sessions costs bandwidth, not a punitive per-user surcharge, and you can cap storage in the dashboard. You can also host the playable build itself: upload the WebGL/HTML5 output (individually or as a ZIP) and reference it from your index.html, or hand the link to a portal that accepts external hosting.