Permanent File Links
Permanent File URLs That Outlive Renames, Moves, and Redesigns
Upload files and get permanent, unbreakable URLs. Your links work forever with global CDN delivery.
Permanent URL for every file
Link rot is a quiet, expensive problem. A URL you pasted into a transactional email in March stops resolving in June because someone renamed the file, moved it to a different folder, or migrated the storage layout — and now your password-reset PDF, your invoice download, or your release binary returns a 404 to a real customer. cdn22.net is built so that doesn't happen.
Every public file gets a permanent CDN URL the moment you confirm the upload, and that URL is bound to the file's immutable identity, not its folder path. Rename the file from logo-v2.png to logo-final.png, drag it into a different project, reorganize your whole folder tree — the public URL keeps resolving. There is nothing to re-publish and no redirect to maintain.
For private files the story is different but just as durable: instead of a public CDN URL you create a permalink (POST /p) — a fixed address of your own that, on every hit, mints a fresh short-lived signed URL behind the scenes and redirects to it. The address you hand out never changes; the actual download URL rotates on each access so it can't be hotlinked or replayed.
That gives you one stable, shareable link with signed-URL protection underneath, which is exactly what gated downloads, member-only assets, and revocable shares need. Compare this to the consumer tools people reach for first: Google Drive and Dropbox 'share' links are tied to accounts and change when you move or re-share the file; WeTransfer-style links expire in days.
None of them are safe to embed in a document you expect to live for years. Because a cdn22.net public URL never changes, it is genuinely safe to bake into generated PDFs, README files, knowledge-base articles, RSS enclosures, and third-party apps you don't control. The link's lifetime is tied to the file existing and your account being in good standing — delete the file and the URL correctly returns 404, because the link is permanent, not the file.
If you actually want links that stop working on a schedule, that's a separate, deliberate feature; see temporary file hosting. For a one-off drag-and-drop share, the file-to-link generator wraps the same permanent-URL machinery in a single screen, and file storage with CDN covers the delivery layer that makes each permanent URL a stable CDN URL rather than a single-origin download.
Pick the link that fits
Temporary Transfer Link vs Permanent File URL vs Private Signed Link
Three link shapes come out of the same upload. Broken links usually mean the wrong one got pasted somewhere permanent — a seven-day transfer URL in a knowledge-base article, or a ten-minute signed URL in a README. Match the row to where the link is going.
Temporary transfer link
For a one-time handoff you want to go dead on its own: a proof, a draft, an export. Mark the file private and mint a signed URL — 10 minutes by default, up to 7 days with expiresIn. Never paste one into a document you don't control. See temporary file hosting.
Permanent file URL
For anything embedded, indexed, or handed to a customer: a public file's permanent CDN URL resolves to the bytes forever and survives renames, moves, and folder reorganizations. This is the link to bake into emails, PDFs, docs, and release notes. Upload a file and get a link to try one.
Private permalink (signed underneath)
For gated or revocable downloads that still need one fixed address: create a permalink with POST /p. The address you hand out never changes; each hit mints a fresh short-lived signed URL behind it, so the link can't be hotlinked or replayed. See secure file sharing.
Replacing links that already rotted
Migrating off Drive, Dropbox, or a WeTransfer habit? Re-upload once, collect the permanent URLs, and update the references — after that a rename never costs you another migration. The file upload API turns a directory into a URL manifest in one pass; wetransfer-alternative maps the differences.
Permanent URL readiness checklist
- CMS and marketing assets: the URL must outlive a site redesign or a path change.
- Docs, READMEs, and knowledge base: readers arrive months later — no expiring link belongs here.
- Generated exports, invoices, and receipts: the link ships inside a PDF you can't edit afterwards.
- Customer portals and transactional email: a 404 here reaches a real customer, not you.
- Downloads, installers, and release artifacts: version the filename, not the URL.
- Embeds in apps you don't control: if you can't push an update, the link has to be permanent.
Honest scope
Uploading needs a cdn22.net account with billing activated — permanent hosting is prepaid, not a throwaway drop. Recipients never need an account. The URL stays live for as long as the file exists and the account is in good standing; delete the file and it correctly returns 404.
Benefits With No Complexity
Global CDN delivery
Edge-cached worldwide
Signed-URL security
What You Get
Unlimited files
Unlimited storage
Public + Private storage
CDN ready links
Prepaid credits
More coming soon
How cdn22.net Works
1. Upload
2. Copy
3. Use Anywhere
Why Developers Choose cdn22.net
A Better Way to Store & Deliver Files
| Google Drive | Dropbox | WeTransfer | cdn22.net | |
|---|---|---|---|---|
| URL bound to file identity, not path | ||||
| Survives rename / move / reorg | ||||
| Never expires (public files) | ||||
| Global CDN delivery | ||||
| Stable permalink for private files | ||||
| No recipient account required | ||||
| REST API for automation |
Calculate Your Needs
Storage
Egress
CDN Bandwidth
Get Permanent File Links
- Global CDN delivery
- Edge-cached worldwide
- Signed-URL security
- Unlimited files
- Unlimited storage
- Public + Private storage
- No subscription — prepaid credits keep spend predictable