Large File Transfer Built for Repeat Delivery

Most "send large files" tools are built for a single hand-off and nothing after it. Filemail lets you upload files free up to 5 GB, pCloud Transfer sends up to 5 GB with no registration, and Wormhole does simple, private, end-to-end-encrypted sharing with expiring links — all excellent when you need to fire one file across once and forget it. But every one of them treats the file as disposable: it lives for a few days, then it's gone, and there's nothing to reuse, embed, or automate.

If you deliver files to clients, customers, or your own app over and over, that one-off model quietly becomes the bottleneck. cdn22.net is built for the repeat case — you upload a large file once, get a fast, permanent CDN download link, and keep the file in reusable storage instead of re-uploading it for every send.

The delivery is the differentiator. A public large file gets a permanent, edge-served CDN URL the moment the upload confirms, so a 2 GB installer, a video master, or a design archive downloads from the nearest edge instead of a single origin server — the same delivery the file storage with CDN and file to link pages cover in depth.

When a send should not live forever, a private file is never given a public URL at all: your backend mints a cryptographically signed link on demand that defaults to a 10-minute window and can stretch to 7 days, then stops working when the clock runs out (the temporary file hosting page walks the expiring-link mechanics).

No recipient ever creates an account — the deliberate contrast with Dropbox, whose large-file shares can drop a recipient onto a login or "request access" wall — and there are no ads on the download page.

Because every transfer is the same three-call REST upload — POST for a presigned URL and id, PUT the bytes, POST to confirm — a backend can turn a finished render, an export, or an invoice into a shareable link in one workflow step (for files big enough to need chunking, the multipart upload planner sizes the parts and retries first), the way file.io exposes an API for programmatic sharing but without the single-download self-destruct.

That makes cdn22.net a fit for software and media distribution, client deliverables, paid digital downloads, and app-generated links (see the file sharing and files SDK surfaces, and the upload a file guide for the full flow). Pricing is prepaid credits with no subscription and no per-seat plan: you pay only for the storage and bandwidth you actually use, so a heavy delivery month costs more and a quiet one costs less, with nothing auto-renewing.

Honest fit check — if you send one big file a year, a free one-off transfer tool is genuinely the right call; cdn22.net earns its keep when large-file delivery is a recurring part of how you work.

Coming from a consumer transfer tool, the tradeoff points the same way every time: those tools win the anonymous one-off send, cdn22.net wins the moment the same file has to go out again. The WeTransfer alternative page compares permanent links against expiring transfers for client work, the Dropbox alternative for developers page compares desktop sync against app file hosting, and the file transfer API reference shows how a backend mints those links itself.