A field manual for terminal file transfer — pipe a file
through curl, get a one-shot link back.
No accounts, no JavaScript, no nonsense.
Three commands. That is the whole product. Everything below is footnotes.
$ curl -T ./file.txt https://bashupload.cloud$ tar czf - ./dir | curl -T - \
https://bashupload.cloud/dir.tgz$ curl -O https://bashupload.cloud/<id>/file.txt$ wget https://bashupload.cloud/<id>/file.txtFor when you are stuck in a GUI. Same backend, same rules.
The fine print, set in tabular numerals so you can scan it like a receipt.
Patterns we’ve seen in the wild. Steal freely.
# grab screen, ship it
$ screencapture -i out.png \
&& curl -T out.png https://bashupload.cloud$ pg_dump mydb | gzip | \
curl -T - https://bashupload.cloud/mydb.sql.gz$ journalctl -u nginx | \
curl -T - https://bashupload.cloud/nginx.log$ ssh box 'cat /var/log/syslog' | \
curl -T - https://bashupload.cloud/syslog.txtQuestions we get on repeat, answered once, here.
Yes. No accounts, no payment, no rate limit beyond what abuse prevention requires.
Files are deleted the moment they are downloaded the first time, or after 24 hours — whichever happens first. There is no “extend” button. By design.
Up to 512 MB per upload. If you need more, split with split -b and re-assemble with cat.
Transfers are over HTTPS. Files are not encrypted at rest, but they don’t live long. If you need end-to-end secrecy, encrypt with gpg or age before upload.
No — the link is consumed by the first download. If you need a few recipients, encrypt the file and re-upload, or send each one their own copy.
curl?Yes. There is a browser form below the masthead. Anything that can do an HTTP PUT or multipart/form-data POST works — wget, httpie, powershell’s Invoke-WebRequest, even fetch() in a script.
The webserver keeps minimal access logs for abuse handling. There are no analytics, no cookies, no third-party trackers on this page.