Firebase Storage Alternatives

Firebase Storage couples three things you cannot really separate: a Firebase/Google Cloud project, the Firebase SDK (or its Google-flavored REST surface), and Storage Security Rules — a bespoke DSL you must author and test before a single upload is safe. That works beautifully inside a Firebase app and becomes friction the moment you are outside one: a Go backend, a cron worker, a non-Google mobile stack, or simply a team that doesn't want a rules file as a load-bearing security boundary. files.link replaces all three with a plain REST API, app-level access control via a public/private flag plus signed URLs, and CDN delivery built in rather than configured through separate Firebase Hosting.

The upload contrast is the clearest. Firebase wants the initialized SDK: const ref = storageRef(storage, path); await uploadBytes(ref, file); const url = await getDownloadURL(ref); — and that getDownloadURL only behaves as you expect if your Security Rules match. files.link is three SDK-free HTTP calls with your raw API key in the Authorization header: POST /v1/files/{folderId} returns { success, urls:[{ url, id }] }; PUT the file bytes to that presigned url; POST /v1/files/confirm-upload with { ids:[id] } returns the permanent CDN URL.

The identical three calls run from a browser fetch, a Node backend, a Python worker, or curl — no environment-specific SDK. You also stop writing Security Rules entirely. Instead of a match /b/{bucket}/o block you keep in sync with your auth model, you decide at upload time whether a file is public (a permanent CDN link anyone with it can fetch) or private (no public URL; your backend mints a short-lived signed URL per access).

Authorization lives in your own application code plus the API key and the URL's expiry. Migrating existing objects is a loop: bucket.getFiles() with the Firebase Admin SDK, download each blob, push it through the three-call upload, and store the new permanent URL alongside the old path; flip reads when every record is migrated. On cost, Firebase meters storage, download bandwidth, and operations per 10k separately, with egress the unpredictable one; files.link bundles storage, CDN, and requests into prepaid credits so you watch one balance.

Among Firebase Storage alternatives, the appeal here is portability — the identical upload flow runs in any runtime instead of being bound to a Google Cloud project and a rules file. React and Next.js teams have dedicated guides linked below.