Upload Files via FTP to FastDDL.com
Works even when your browser has blocked FTP access.
Chrome stopped supporting FTP in version 95 (2021). Firefox followed. Edge is moving the same direction. If you try to click an ftp:// link today, nothing happens — no download prompt, no file dialog, just a dead click.
But FTP servers still host millions of legitimate files: open-source mirrors (GNU, Apache, kernel.org), university archives, government datasets, legacy corporate infrastructure. They don't have HTTPS. They don't have a web frontend. They're just FTP.
The FastDDL workaround
FastDDL's Upload from URL feature now supports ftp:// and ftps:// schemes alongside https:// and http://.
Paste any FTP URL into the upload form. FastDDL connects to the FTP server, downloads the file server-side, encrypts it with AES-256-GCM, and gives you a share link. Your browser never touches FTP — it just sees the encrypted file.
How to use it
- Find the file you need on any FTP server (e.g.
ftp://ftp.gnu.org/pub/gnu/wget/wget-1.21.4.tar.gz) - Go to fastddl.com
- Click 🔗 Upload from URL
- Paste the FTP URL
- Click Fetch & Encrypt File
- Wait for the server to fetch + encrypt (typically seconds for small files)
- Receive your share link + decryption password
- Anyone with the link can download — they never see the FTP server
Use cases
Open-source distributions
Many projects still mirror releases via FTP-only. Get the latest kernel source, GNU toolchain, or legacy software release without configuring an FTP client.
Research datasets
Universities and government agencies publish datasets via FTP that are hundreds of GB. Upload to FastDDL (up to 2GB per file), then share a private encrypted link with your collaborators.
Legacy corporate systems
Some enterprise systems still use FTP for B2B file exchange. If you can't open them in your browser anymore, route them through FastDDL.
Anonymous FTP archives
Public FTP archives like ftp://ftp.gnu.org, ftp://ftp.kernel.org, ftp://archive.org are still browsable via FastDDL.
Security considerations
FastDDL blocks FTP connections to private/internal IP ranges (10.x, 192.168.x, 172.16-31.x, 127.x) to prevent SSRF. You can only fetch from public FTP servers.
FTP itself transmits credentials in plaintext. We recommend using ftps:// (FTP over TLS) where available. FastDDL supports both.
Once the file lands on FastDDL, it's encrypted with AES-256-GCM zero-knowledge — so even if the original FTP transfer was insecure, the share link is fully private.
Privacy note (being honest)
Two sides to consider:
For the FTP server: FastDDL's server IP appears in FTP logs, not yours. The FTP server never sees your IP address. So if you're worried about being tracked on a specific FTP server, this approach hides you from that server.
For FastDDL: Your real IP, browser fingerprint, device info, and connection details are publicly displayed on the file page (see the "WHAT WE KNOW ABOUT YOU" panel and the visitor log). That's by design — FastDDL is built on radical transparency.
Use a VPN if you want to hide your identity from FastDDL entirely. But for the specific use case of "I don't want my IP in a specific FTP server's logs" — this works perfectly.