File Request Links — Collect Files From Clients & Teams

When you need files <em>from</em> people — client deliverables, contractor assets, teammate uploads, customer documents — the job doesn't end when the file lands. You still have to organize it, keep it somewhere durable, and hand it back out again as a link that actually works. Consumer file-request tools stop at the intake: Dropbox File Requests give a sender a no-account upload form, and Google Forms or WeTransfer collect a batch and drop it in a folder — all fine for a one-time gather, but none is built to <em>redeliver</em> what you collected as fast, global, developer-controlled links. cdn22.net comes at the same problem from the storage-and-CDN side: you collect files into organized project folders, then every file gets a permanent CDN download URL or a private, cryptographically signed link the moment it's uploaded — so the same file you collected is instantly deliverable to a client, a teammate, or your own app, with no recipient account required to download.

Here's the honest scope, because promising a feature that doesn't exist helps nobody. Today cdn22.net is developer-first: the intake side is API-driven, not a hosted consumer upload form. You collect files one of two truthful ways — invite teammates as project collaborators so they upload straight into shared folders from the dashboard, or wire the three-call REST upload (request a presigned URL, PUT the bytes, confirm) into your own intake form, client portal, or internal tool.

The file upload API, the upload a file guide, and the files SDK all cover that flow. Once files are in, delivery is the payoff: permanent links for anything public, signed links that default to a 10-minute window (up to 7 days) for anything private, and the same file sharing surface your whole team already uses.

Pricing is prepaid credits with no per-seat plan — you pay for the storage and bandwidth you use, so a heavy collection month costs more and a quiet one costs less, with nothing auto-renewing. If what you actually need is a hosted, no-account public upload request page like Dropbox's, start an account and tell us — the signup CTA carries that intent so we can prioritize it for the people asking.

If you're building the intake yourself and want a real storage + CDN backbone underneath it, that part is here today. When the files clients send you are large, the multipart upload planner sizes the parts, parallel upload width, and retry cost for the uploader you build.