Our take
- Activity
- 55
- Community
- 36
- Issues
- 44
- Pull requests
- 63
+33 stars in the last 30 days
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
3,161Forks
90Change since Nov 16, 2026: +1 stars·0 forks
Overview
termscp combines a terminal file explorer with file transfer clients, letting users work with local files and remote storage through one text-based interface. It addresses the need to move between separate command-line tools or graphical clients when browsing, transferring, and managing files across different protocols.
It suits people who prefer a keyboard-driven terminal workflow and need connections to multiple kinds of remote systems. The project supports several desktop operating systems and includes features such as bookmarks, file editing, and an embedded terminal.
Key Features
- Connects over SFTP, SCP, FTP/FTPS, S3, Google Cloud Storage, SMB, WebDAV, and Kubernetes.
- Browse and manage local and remote files, including creating, removing, renaming, searching, viewing, and editing them.
- Save bookmarks and revisit recent connections.
- Authenticate to SFTP and SCP with SSH keys or a username and password.
- Synchronize file changes with a remote host.
- Customize themes, file sorting, explorer display, and text editor settings.
- Use an embedded terminal and save passwords in the operating system key vault.
Use Cases
- System administrators can browse and transfer files on remote servers using a terminal interface.
- Developers can manage files across SFTP, SCP, or cloud storage without switching between separate file-transfer applications.
- Users who prefer terminal workflows can inspect and edit local and remote files from a single interface.
- Teams managing recurring connections can use bookmarks and recent connections to return to familiar hosts.
Getting Started
Install on Linux, FreeBSD, or macOS with:
curl --proto '=https' --tlsv1.2 -sSLf https://termscp.rs/install.sh | sh
For Windows and other installation methods, see the installation guide. For usage details, consult the user manual and the repository README.
Considerations
- Building from source requires platform-specific dependencies. The README lists libdbus-1, pkg-config, and libsmbclient for Linux, and dbus, pkgconf, and libsmbclient for FreeBSD or NetBSD.
- Some optional conveniences need extra software, such as a keyring manager on Linux or an application opener for viewing files.
- The installation script pipes a remote script into a shell. Review the installation instructions and alternatives on the official site if you prefer another installation method.
- Protocol availability does not remove the need to configure credentials and access for each remote service.
Found this useful?
Share it with someone who would like termscp.