TE
SOFTWARE

Termius

Termius is a cross-platform SSH and remote-connection client for organizing hosts, credentials and terminal sessions. This page covers host profiles, key handling, session checks and safe synchronization boundaries.

Version 9.43.0WindowsmacOS UniversalLinux DEB/SnapiOS/iPadOSAndroidProprietary; feature availability varies by plan

What Termius provides

Termius groups SSH hosts, connection settings and terminal sessions in a desktop and mobile workflow. A host profile can reduce repetitive input, but it also makes target verification important: a saved label is not proof that the address points to the intended machine.

Host and credential boundaries

Keep host notes separate from private keys and passphrases, use the narrowest account that fits the task and confirm the hostname, port and account before running a command. When a profile is synchronized between devices, review what is shared and keep recovery material outside ordinary notes.

Maintenance note

This page reviews Termius for SSH host organization, terminal sessions, SFTP tasks and credential hygiene. Content review date: 2026-08-23.

SAVE TO CLOUD

Save to your cloud drive

Open the cloud drive to get the file directly, or save it for convenient access on another device.

Links checked 2026-08-06
Save first, access when you need itOn desktop, scan with the matching cloud-drive app. On mobile, tap the save button.
GUIDE

Termius SSH host setup guide

Create one verified host profile, connect with a restricted account and record the session result without putting private credentials into shared notes.

Before you start

  • Confirm the target host, port, account and expected authentication method.
  • Prepare a key or approved credential through the normal access process.
  • Keep a separate recovery route and a short record of the intended command.
01

Installation steps

  1. 01

    Create a host profile

    Add the host address, port and account, give the profile a precise label and compare each field with the connection record before saving it.

  2. 02

    Configure authentication

    Select the approved key or credential, keep passphrases protected by the device credential store and avoid pasting secrets into host descriptions.

  3. 03

    Test a read-only session

    Connect, inspect the remote identity and working directory with a harmless command, then close the session if the target does not match the record.

02

Quick start

  1. 01

    Separate environments

    Use clear labels for development, staging and production, and require a second visual check before opening a privileged session.

  2. 02

    Review SFTP paths

    Confirm the remote and local paths before transferring files, and keep a checksum or version note for important uploads.

  3. 03

    Audit synchronized data

    Review which profiles, keys and notes are synchronized between devices and remove stale hosts before a device is retired.

Usage tips

  • Prefer key-based authentication and restricted accounts over reusing an administrator password.
  • Never treat a saved host nickname as a substitute for checking the actual remote identity.
  • Keep session transcripts free of tokens, private keys and unrelated personal data.
Troubleshooting and uninstall

Why does an SSH connection time out?

Check the host, port, network route and server availability, then compare the profile with a known-good connection before changing several settings at once.

Why was the wrong server opened?

Stop the session, inspect the remote identity and correct the profile label or address; use environment-specific labels and a read-only first command to prevent repeats.

  1. Export non-secret host notesRecord only the host fields and operational notes needed for migration, excluding private keys, passphrases and session secrets.
  2. Remove profiles and application dataSign out or remove synchronized profiles, revoke device access through the account policy and uninstall Termius after the migration is verified.
FAQ

Frequently asked questions

Does Termius provide server access by itself?

No. It is a client; the server, account permissions, network path and authentication policy still control whether a session is accepted.

Should private keys be stored in host notes?

No. Keep keys and passphrases in the protected credential mechanism and store only the minimum connection notes needed for the host profile.

Does the download require an extraction code?

The Quark entry does not require one; the four-character code for the Baidu entry is shown beside its download entry.