ConnectBot Alternatives in 2026: What to Use Instead (and When Not to Switch)

The short answer

ConnectBot mostly doesn’t need replacing — it needs supplementing, and only if you hit one of its specific gaps. Unlike JuiceSSH, it is genuinely alive: F-Droid lists 1.10.9-oss added on 10 June 2026, it is Apache-2.0, it asks for no account, and it costs nothing with no tiers. If that already describes your requirements, stop reading and keep it.

People search for alternatives because of five concrete missing things. Match yours to the answer:

The rest of this article covers where ConnectBot actually stands, what each alternative costs you, and — the part most listicles skip — how to migrate without locking yourself out of a server you can only reach from your phone.

Where ConnectBot actually stands in 2026

Worth establishing before you shop, because a lot of “ConnectBot is dead” commentary online is recycled from years ago.

It is the original. ConnectBot was the first SSH client for Android, started by Kenny Root, and the source has lived at github.com/connectbot/connectbot under Apache-2.0 throughout.

It still ships. F-Droid’s listing shows a steady cadence through 2026 — 1.10.5-oss added 22 April 2026, 1.10.9-oss added 10 June 2026 — and the Play Store listing was last updated in April 2026. AppBrain’s stats page puts it at 5,000,000+ installs and a 3.77 / 5 rating across roughly 43,000 ratings. The F-Droid build uses the oss flavour: it bundles its own cryptography provider and depends on no Google Play Services.

What it does well: multiple simultaneous sessions, public-key auth including ed25519, port forwarding and tunnels, agent forwarding, telnet, a local shell, per-host colour schemes and fonts, and a genuinely useful on-screen key bar. On a device with a hardware keyboard it is still one of the most keyboard-correct terminals on the platform.

The honest criticism isn’t that it’s abandoned — it’s that a large share of recent releases are dependency bumps, toolchain updates and CI maintenance rather than features. The 1.9.11 release in April 2025, for instance, was substantially Gradle plugin, Mockito, AssertJ and error-prone version bumps. That’s a healthy sign for security hygiene and a flat line for capability. If you filed a feature request, it is probably still open.

So: not abandonware, not evolving fast. Compare that with JuiceSSH, unpublished from Google Play in December 2025 after four years without a release — that is what actual abandonment looks like, and ConnectBot is nowhere near it.

The five reasons people actually leave

1. No SFTP, and probably never

This is the big one. ConnectBot does interactive sessions and tunnels. It does not do SFTP or SCP — no file browser, no upload, no download.

The request is neither new nor overlooked. Issue #52, “scp/sftp functionality”, was opened on 7 January 2015 and is still open eleven years later; people keep re-asking in threads like #1044. Treat it as a deliberate scope boundary, not a roadmap item.

Workarounds exist and all of them are worse than a file browser: cat a file into the terminal, base64 it through the clipboard, or curl it to and from a server you control. If you edit config files, pull logs, or drop deploy artefacts from your phone with any regularity, this alone justifies a second app. The best SFTP client for Android covers that field specifically.

2. No sync, no backup, no second device

ConnectBot’s hosts and keys live in the app’s own storage on one device. There is no account and no cloud — which is exactly why many people chose it — but the flip side is real: a lost or wiped phone takes your host list and your private keys with it, and there is no first-class export-and-restore story.

If you also work from a laptop and want one canonical host list, that’s a structural mismatch rather than a settings problem.

3. The interface shows its age

ConnectBot’s UI is functionally dense and visually from an earlier Android era. Host list, tap to connect, done. Whether that’s a feature or a flaw is genuinely a matter of taste — but if you’re coming from a desktop client with tabs, snippets, saved commands and a file pane, the gap is obvious.

There are also recurring rough edges in soft-keyboard and hardware-keyboard handling on newer Android releases; the tracker carries a long tail of them, including a January 2026 report that shifted-8 (*) is swallowed on some setups. Most users never hit these; the ones who do find them maddening.

4. No Mosh, no session roaming

Requested many times (#123, #2041), never implemented. On a train with patchy signal, an SSH session drops and takes your work with it.

Switching clients is mostly the wrong fix here. The durable answer is server-side: run inside tmux or screen so the work survives any disconnect from any client. Keeping a process running after SSH disconnects covers the patterns, and Mosh vs SSH explains what Mosh does and doesn’t buy you.

5. Reaching machines that aren’t publicly exposed

ConnectBot connects to whatever your phone can already route to. A home server behind CGNAT, a VPS with port 22 firewalled to an allowlist, a lab box on another network — each needs a VPN or tunnel, which means a second app to install, configure, and keep alive against Android’s battery optimiser.

A client with a built-in mesh VPN collapses that into one app. That’s an architectural difference, not a feature-list line item.

The alternatives, by what you’re missing

TermAI — phone-first ops, SFTP, Tailscale, AI suggestions

This is our app, so weigh it accordingly. It exists because of the gap above: the good mobile SSH clients were built as companions to desktop apps, and the phone-native ones were unmaintained.

What it adds over ConnectBot:

• SFTP with a real two-pane file browser, alongside the terminal — the number-one ConnectBot gap.
• Built-in Tailscale. Reach a home server or a firewalled VPS without exposing port 22, and without a second VPN app that Android will eventually kill. Tailscale SSH covers the model.
• AI command suggestions, assistant-style. You describe the goal; it writes the journalctl / systemctl / awk incantation onto your input line and waits for you to press enter. It never executes anything itself. On a production box at 2am that is the correct default, and we made the full argument in letting AI run shell commands on mobile, safely.
• iOS and Android, so changing phones doesn’t mean changing clients.

Pricing: the free tier is 5 AI requests per day, with SSH and SFTP unlimited; Pro is $2.99/month; Team is $7.99/seat/month.

What ConnectBot still does better: it is fully open source, and it wants nothing from you at all. If those are your top two criteria, that is a legitimate reason to stay put.

Termius — if a laptop is also in the picture

The mature cross-platform option: Windows, macOS, Linux, iOS and Android, with an encrypted vault of hosts, keys, snippets and history. If the requirement is “the same host list everywhere,” this is the strongest answer in the category and it isn’t close.

The costs: an account is mandatory, sync is a paid feature, the mobile app is heavier than ConnectBot, and the pricing is enterprise-shaped. Paid tiers start at Pro, $10 per user per month billed annually, then Team at $20 and Business at $30 per user per month (termius.com/pricing). The free tier is a usable single-device client — we mapped exactly where the paywall falls in Termius free vs paid, and Termius vs ConnectBot is the direct head-to-head.

For a ConnectBot user the trade is stark, and worth naming plainly: you are exchanging “no account, nothing leaves the device” for “credentials in someone’s cloud, synced.” That’s a fine trade for many people and an unacceptable one for others.

Termux — only if what you wanted was a local shell

Termux is not an SSH client. It’s a terminal emulator plus a Linux package manager for Android, where ssh is one package you install with pkg install openssh. You get the real OpenSSH binary, ~/.ssh/config, ProxyJump, rsync, scp — everything a Linux box has, driven entirely by typing.

What you don’t get is the layer ConnectBot already gives you: a tap-to-connect host list, key management UI, reconnect handling, a key bar. Moving from ConnectBot to Termux is a downgrade for connecting to servers and an upgrade for doing work on the phone itself.

ConnectBot vs Termux is the direct comparison; Termux alternatives covers the same ground from the other direction.

Staying on ConnectBot — a real option

Underrated, so stated explicitly. If you connect to a handful of servers, never move files, and don’t need a laptop to share the list, there is no upgrade available to you. Adding a second app for the one thing ConnectBot lacks — an SFTP client next to it — is often the smallest correct change, and it costs nothing.

Side by side

That last row is a warning, not a recommendation — see below.

Two columns do most of the deciding. “Account” separates the people who chose ConnectBot on principle from the people who chose it because it was the first result in 2014. “SFTP” separates the people who are genuinely fine from the people who have spent years cat-ing config files into a terminal without realising there was a better way.

What about the ConnectBot forks?

You’ll find these recommended in old forum threads, so it’s worth being clear about them.

VX ConnectBot (github.com/vx/connectbot) is an enhanced Apache-2.0 fork that folded in changes from Irssi ConnectBot, aimed at devices with physical keyboards — extra key mappings, added terminal features. It solved a real problem in the era of slide-out QWERTY phones.

Irssi ConnectBot was a fork built around running IRC clients over SSH, developed mainly by Iiro Uusitalo and Ville Kerminen. Its original home was a Google Code archive, which tells you most of what you need to know about its timeline.

Both fixed gaps in a version of ConnectBot from over a decade ago. Before installing either, check the last commit and last release date yourself — a stale SSH client is a worse proposition than a slowly-evolving one, because it means old crypto libraries and unpatched dependencies in an app that holds your private keys. Upstream ConnectBot’s steady 2026 dependency bumps, unglamorous as they are, are exactly what a stale fork is missing.

What not to switch to

JuiceSSH. Still the most-recommended ConnectBot alternative in older blog posts and Reddit threads, and the wrong answer in 2026: unpublished from Google Play in December 2025 after roughly four years without a release, with Pro licence validation failing for a number of users. Full account in JuiceSSH was removed from the Play Store; migration paths in JuiceSSH alternatives.

Anything called “PuTTY for Android.” There is no official PuTTY for Android — PuTTY is Windows and Unix desktop software. Play Store listings using the name are third-party apps trading on the brand, and the ones that look most like PuTTY tend to be the least maintained. PuTTY for Android covers what to use instead.

Unbranded “SSH Client” apps with five-figure install counts, no visible source and no homepage. This is a category where the app holds your private keys and your production credentials. The bar for trust should be higher here than for a photo editor: open source, or a named company with a support address and a changelog. ConnectBot clears that bar easily — which is a good reason to leave it installed while you evaluate anything else.

Migrating off ConnectBot without locking yourself out

The failure mode is specific and unpleasant: you switch clients, find the new one can’t authenticate, and the only device that could reach that server is the phone you just changed. Do it in this order.

1. Inventory first. Go through ConnectBot’s host list and record, for each entry: hostname, port, username, which key it uses, and any port forwards configured on it. Port forwards in particular are easy to forget and annoying to reconstruct — SSH tunnels explains what those settings mean if you inherited them from a past version of yourself.

2. Install the new client alongside ConnectBot. Don’t uninstall anything yet. Two SSH clients on one phone conflict in no way whatsoever.

3. Generate a fresh key in the new client — don’t export the old one. This is the step people try to skip. Exporting a private key means it passes through a clipboard or a file, which is exactly the exposure you avoided by keeping it inside an app. Generate a new ed25519 key in the new client; ed25519 vs RSA has the reasoning, and on iOS a Secure Enclave–backed key beats a file on disk outright.

4. Append the new public key while ConnectBot still works. From a live ConnectBot session, add it to ~/.ssh/authorized_keys on each host. Copying an SSH key to a server covers the mechanics — on a phone, appending by hand with cat >> beats trying to run ssh-copy-id from a client that doesn’t ship it.

5. Verify from the new client on a cold start. Force-close it, reopen, connect fresh. A session that’s already warm proves nothing.

6. Only then remove the old key from authorized_keys, and only then consider uninstalling ConnectBot.

Before step 6, confirm you have a second way in — a provider web console (DigitalOcean, Hetzner, OVH), Proxmox, IPMI, or a physically reachable keyboard. That console is your undo button, and the moment you need it is a bad moment to discover it doesn’t work.

One more thing while you’re in there: ConnectBot’s known-hosts database goes with it. Your new client will prompt you to accept a host key on first connection to every server. That’s a genuine trust decision, not a formality — where you can, check the fingerprint against one printed on the server itself rather than tapping through. Host key verification and trust-on-first-use explains the model you’re re-enacting.

FAQ