transfer.sh alternatives and similar software solutions
Based on the "Single-click/drag-n-drop upload" category.
Alternatively, view transfer.sh alternatives based on common mentions on social networks and blogs.
8.5 9.3 L3 transfer.sh VS OnionShareSecurely and anonymously share files, host websites, and chat with friends using the Tor network
6.4 0.0 L5 transfer.sh VS YouTransferThe simple but elegant self-hosted file transfer & sharing solution
6.0 3.6 transfer.sh VS linxSelf-hosted file/code/media sharing website. ~~~~~~~~~~~~~~~~~~~ Demo: https://demo.linx-server.net/ [Moved to: https://github.com/linx-server/linx-server]
6.0 0.0 L5 transfer.sh VS ipfs.picsContent-addressable, peer-to-peer method of storing and sharing images on the internet.
5.8 6.5 L2 transfer.sh VS ProjectSendProjectSend is a free, open source software that lets you share files with your clients, focused on ease of use and privacy. It supports clients groups, system users roles, statistics, multiple languages, detailed logs... and much more!
5.7 8.1 transfer.sh VS ChibisafeBlazing fast file uploader and awesome bunker written in node! 🚀
5.3 3.3 transfer.sh VS PlikPlik is a scalable & friendly temporary file upload system ( wetransfer like ) in golang.
4.9 4.1 L2 transfer.sh VS PictShare:camera: PictShare is an open source image, mp4, pastebin hosting service with a simple resizing and upload API that you can host yourself. :rice_scene:
3.1 3.1 transfer.sh VS Kleeja⬇️ File Upload/sharing application, used by thousands of webmasters since 2007.
1.9 4.5 transfer.sh VS ShareSimple yet advanced uploader. Allows users to upload files,images, and text with moderation tools for admins. Can be used for friends and family or just for you. Built with integration, like ShareX but more uploaders will be officially supported.
1.6 3.2 transfer.sh VS Web-File-UploaderA simple tool to let people upload and share images and files
1.2 5.9 transfer.sh VS PsteJust a simple file hosting application inspired by the likes of pomf.se and teknik.io.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of transfer.sh or a related project?
Easy and fast file sharing from the command-line. This code contains the server with everything you need to create your own instance.
Transfer.sh currently supports the s3 (Amazon S3), gdrive (Google Drive), storj (Storj) providers, and local file system (local).
The service at transfersh.com is of unknown origin and reported as cloud malware.
$ curl --upload-file ./hello.txt https://transfer.sh/hello.txt
Encrypt & upload:
$ cat /tmp/hello.txt|gpg -ac -o-|curl -X PUT --upload-file "-" https://transfer.sh/test.txt
Download & decrypt:
$ curl https://transfer.sh/1lDau/test.txt|gpg -o- > /tmp/hello.txt
Upload to virustotal:
$ curl -X PUT --upload-file nhgbhhj https://transfer.sh/test.txt/virustotal
$ curl -X DELETE <X-Url-Delete Response Header URL>
$ curl --upload-file ./hello.txt https://transfer.sh/hello.txt -H "Max-Downloads: 1" # Limit the number of downloads
$ curl --upload-file ./hello.txt https://transfer.sh/hello.txt -H "Max-Days: 1" # Set the number of days before deletion
The URL used to request the deletion of a file. Returned as a response header.
curl -sD - --upload-file ./hello https://transfer.sh/hello.txt | grep 'X-Url-Delete' X-Url-Delete: https://transfer.sh/hello.txt/BAYh0/hello.txt/PDw0NHPcqU
See good usage examples on [examples.md](examples.md)
Create direct download link:
|listener||port to use for http (:80)||LISTENER|
|profile-listener||port to use for profiler (:6060)||PROFILE_LISTENER|
|force-https||redirect to https||false||FORCE_HTTPS|
|tls-listener||port to use for https (:443)||TLS_LISTENER|
|tls-listener-only||flag to enable tls listener only||TLS_LISTENER_ONLY|
|tls-cert-file||path to tls certificate||TLS_CERT_FILE|
|tls-private-key||path to tls private key||TLS_PRIVATE_KEY|
|http-auth-user||user for basic http auth on upload||HTTP_AUTH_USER|
|http-auth-pass||pass for basic http auth on upload||HTTP_AUTH_PASS|
|ip-whitelist||comma separated list of ips allowed to connect to the service||IP_WHITELIST|
|ip-blacklist||comma separated list of ips not allowed to connect to the service||IP_BLACKLIST|
|temp-path||path to temp folder||system temp||TEMP_PATH|
|web-path||path to static web files (for development or custom front end)||WEB_PATH|
|proxy-path||path prefix when service is run behind a proxy||PROXY_PATH|
|proxy-port||port of the proxy when the service is run behind a proxy||PROXY_PORT|
|ga-key||google analytics key for the front end||GA_KEY|
|provider||which storage provider to use||(s3, storj, gdrive or local)|
|uservoice-key||user voice key for the front end||USERVOICE_KEY|
|aws-access-key||aws access key||AWS_ACCESS_KEY|
|aws-secret-key||aws access key||AWS_SECRET_KEY|
|s3-endpoint||Custom S3 endpoint.||S3_ENDPOINT|
|s3-region||region of the s3 bucket||eu-west-1||S3_REGION|
|s3-no-multipart||disables s3 multipart upload||false||S3_NO_MULTIPART|
|s3-path-style||Forces path style URLs, required for Minio.||false||S3_PATH_STYLE|
|storj-access||Access for the project||STORJ_ACCESS|
|storj-bucket||Bucket to use within the project||STORJ_BUCKET|
|basedir||path storage for local/gdrive provider||BASEDIR|
|gdrive-client-json-filepath||path to oauth client json config for gdrive provider||GDRIVE_CLIENT_JSON_FILEPATH|
|gdrive-local-config-path||path to store local transfer.sh config cache for gdrive provider||GDRIVE_LOCAL_CONFIG_PATH|
|gdrive-chunk-size||chunk size for gdrive upload in megabytes, must be lower than available memory (8 MB)||GDRIVE_CHUNK_SIZE|
|lets-encrypt-hosts||hosts to use for lets encrypt certificates (comma seperated)||HOSTS|
|log||path to log file||LOG|
|cors-domains||comma separated list of domains for CORS, setting it enable CORS||CORS_DOMAINS|
|clamav-host||host for clamav feature||CLAMAV_HOST|
|rate-limit||request per minute||RATE_LIMIT|
|max-upload-size||max upload size in kilobytes||MAX_UPLOAD_SIZE|
|purge-days||number of days after the uploads are purged automatically||PURGE_DAYS|
|purge-interval||interval in hours to run the automatic purge for (not applicable to S3 and Storj)||PURGE_INTERVAL|
|random-token-length||length of the random token for the upload path (double the size for delete path)||6||RANDOM_TOKEN_LENGTH|
If you want to use TLS using lets encrypt certificates, set lets-encrypt-hosts to your domain, set tls-listener to :443 and enable force-https.
If you want to use TLS using your own certificates, set tls-listener to :443, force-https, tls-cert-file and tls-private-key.
Switched to GO111MODULE
go run main.go --provider=local --listener :8080 --temp-path=/tmp/ --basedir=/tmp/
$ git clone [email protected]:dutchcoders/transfer.sh.git $ cd transfer.sh $ go build -o transfersh main.go
For easy deployment, we've created a Docker container.
docker run --publish 8080:8080 dutchcoders/transfer.sh:latest --provider local --basedir /tmp/
For the usage with a AWS S3 Bucket, you just need to specify the following options:
If you specify the s3-region, you don't need to set the endpoint URL since the correct endpoint will used automatically.
Custom S3 providers
To use a custom non-AWS S3 provider, you need to specify the endpoint as defined from your cloud provider.
Storj Network Provider
To use the Storj Network as storage provider you need to specify the following flags:
- storj-access (either via flag or environment variable STORJ_ACCESS)
- storj-bucket (either via flag or environment variable STORJ_BUCKET)
Creating Bucket and Scope
In preparation you need to create an access grant (or copy it from the uplink configuration) and a bucket.
To get started, login to your account and go to the Access Grant Menu and start the Wizard on the upper right.
Enter your access grant name of choice, hit Next and restrict it as necessary/preferred. Aftwards continue either in CLI or within the Browser. You'll be asked for a Passphrase used as Encryption Key. Make sure to save it in a safe place, without it you will lose the ability to decrypt your files!
Afterwards you can copy the access grant and then start the startup of the transfer.sh endpoint. For enhanced security its recommended to provide both the access grant and the bucket name as ENV Variables.
export STORJ_BUCKET=<BUCKET NAME> export STORJ_ACCESS=<ACCESS GRANT> transfer.sh --provider storj
Google Drive Usage
For the usage with Google drive, you need to specify the following options:
Creating Gdrive Client Json
You need to create a Oauth Client id from console.cloud.google.com download the file and place into a safe directory
go run main.go --provider gdrive --basedir /tmp/ --gdrive-client-json-filepath /[credential_dir] --gdrive-local-config-path [directory_to_save_config]
Contributions are welcome.
Copyright and license
Code and documentation copyright 2011-2018 Remco Verhoef. Code and documentation copyright 2018-2020 Andrea Spacca. Code and documentation copyright 2020- Andrea Spacca and Stefan Benten.
Code released under [the MIT license](LICENSE).
*Note that all licence references and agreements mentioned in the transfer.sh README section above are relevant to that project's source code only.