Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

transfer.sh review

Free#87 of 105 in File Transfer Services

A self-hosted transfer server for HTTP uploads, configurable links, and storage choices.

3.0/10Editor score
transfer.sh3.0 Visit transfer.sh

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

For command-line users and operators who want to run their own file-sharing service, transfer.sh combines HTTP transfers with a self-hosted server. Uploads can be sent with requests such as curl, which return download links with direct and inline aliases. It is open-source software distributed as source code, binaries, and Docker images, rather than a vendor-priced hosted plan. The project recommends hosting your own instance; public installations are unrelated to the project.

Its controls suit transfers where access should be bounded rather than left open-ended. Operators can configure link expiration with Max-Days, set maximum download counts, and use delete URLs and deletion tokens. Optional client-side encryption workflows and optional ClamAV upload prescanning add further controls. Upload-size and purge settings are configurable per installation, so the service does not impose one universal maximum size or lifetime. That flexibility is useful for technical teams, but it also makes configuration part of operating the service.

Storage and deployment are the strongest fit considerations. Files can use local filesystem storage or supported providers Amazon S3, Google Drive, and Storj, and Docker-based deployment is available. This gives operators several ways to fit the service into an existing environment, while requiring them to manage their own instance. Documentation and community are the listed support channels. There is no desktop app, and sharing centers on command-line transfers and links rather than a broad user-facing workflow. Choose transfer.sh if self-hosting, CLI access, and configurable transfer controls are priorities; choose another service if you need a desktop client or a more guided sharing experience.

transfer.sh pros and cons

  • Where it wins
    • Upload and download files over HTTP using command-line requests.
    • Set download limits, link expiry, and deletion controls.
    • Choose local storage, Amazon S3, Google Drive, or Storj.
  • Where it doesn't
    • No desktop app for users who prefer a graphical transfer client.
    • Self-hosting means operators run and configure the transfer service.
    • Sharing is centered on links and CLI workflows rather than user-facing features.

transfer.sh fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update