transfer.sh

Easy file sharing from the command line.

Slowing · 37
37/100
Slowing

Activity has dropped noticeably. Check the repository before committing to it.

Maintenance 4/40
Releases 1/25
Community 17/20
Momentum 15/15

Commit activity more than 9% of tracked projects; popularity more than 85%. How this is calculated.

Commits, last 11 months

2025-12: 0 commits 2026-01: 0 commits 2026-02: 0 commits 2026-03: 0 commits 2026-04: 0 commits 2026-05: 0 commits 2026-06: 1 commits 2026-07: 0 commits 2026-08: 0 commits 2026-09: 8 commits 2026-10: 11 commits
2025-12 20 total 2026-10
Stars16k
Latest releasev1.6.1 · 4 Dec 2023
Repo updated19 Nov 2026
LicenceMIT
Built withGo

Is transfer.sh actively maintained?

Development is ongoing. The repository recorded 20 commits over the same window, and the last three months alone account for 19 of them.

Activity is accelerating: the last quarter carried 1800% more commits than the one before it.

The last tagged release, v1.6.1, is over 3 years old. If you deploy, expect to build from the default branch rather than a stable tag.

transfer.sh ranks #24 of 34 tracked file transfer - single-click & drag-n-drop upload projects. Several better-maintained options exist in the same category — they are listed below.

What transfer.sh actually does

Transfer.sh is an open-source utility designed for sharing files directly through terminal interfaces using standard HTTP commands. It allows users to upload documents and scripts via tools like curl without needing a complex web browser interface. The software is written in Go and distributed under the MIT licence.

Best fit: It is well-suited for developers and systems administrators who prefer command-line workflows for temporary file sharing between servers or local machines.

Worth knowing: The repository exhibits low maintenance activity, which may mean delayed security patches or lack of compatibility updates for newer systems. It also competes in a crowded space of file transfer tools.

Deployment notes

As a Go application, it typically compiles into a single static binary that requires persistent storage for uploaded files and a reverse proxy to handle TLS termination. You will usually need to configure storage backends, such as local disk or S3-compatible storage, depending on your scaling requirements.


Alternatives to transfer.sh

Projects in the same categories, ordered by health score.