Developer-first QR Code Storage

There are two different things people call a 'QR code storage' problem, and files.link solves one of them precisely. It does not generate codes and it is not a redirect/short-link service that lives inside the encoded URL — for that, the encoded payload should point at your own destination.

What files.link does is host the QR image itself: the PNG or SVG you generated, on a permanent CDN URL, so the artwork shows up instantly wherever it's embedded — an email, a web checkout, a digital menu, a kiosk screen.

The generate-then-host flow is clean: produce the code with any library (qrcode in Node, segno or qrcode in Python, the browser's canvas) encoding whatever URL you want scanned, then upload the rendered image in three calls — POST /v1/files/{folderId} to get a presigned URL and id, PUT the image bytes, then POST /v1/files/confirm-upload with {ids:[...]}. The auth header is your raw API key, so a build step that mass-generates a code per product SKU and uploads each one is a short loop.

Prefer SVG when the code will be scaled across business cards, billboards, and on-screen banners — vector stays crisp at any size and stays tiny over the wire. Use PNG when a downstream tool only accepts raster.

The genuinely useful trick for anything that hits a printer: put a permanent link (p-link) in front of the image. The p-link URL is what you embed in your design files, but you can repoint it at a newly uploaded image later. So if you reprint signage and want a fresh styled code — different finder-pattern color, an updated logo in the center — you upload the new artwork and re-point the p-link, and every place that referenced the p-link now shows the new image without a code change.

(Note this swaps the displayed image, not the data the code encodes; design the encoded URL to be stable up front.)

Unlike free online generators that stamp watermarks or gate high-resolution downloads, files.link stores exactly the bytes you upload with no branding added. Unlike standing up a storage bucket and bolting on a CDN, you get edge delivery in the same call that stores the file. Billing is prepaid credits against real storage and delivery, which fits the spiky pattern of generating thousands of codes for a campaign and then serving them heavily for a few weeks.