Session Desktop 1.18.1
A privacy-focused desktop messenger using distributed Service Nodes, onion routing and end-to-end encryption; this guide covers signature checks, recovery phrases and offline-message boundaries.
Distributed private messaging
Session uses a local account identifier, end-to-end encryption and a distributed Service Node network. It is not the same as a centralized account server; delivery, offline storage, push notifications and attachments have separate timing and metadata boundaries.
Recovery phrases and multiple devices
The recovery phrase is the key material for moving an account. Save it in a separate protected location and complete a test recovery before replacing a device. Confirm messages and attachments on the new device before cleaning the old profile.
Onion routing and local privacy
Onion routing can reduce direct network-address exposure between participants, but notifications, screenshots, contacts, device logs and shared computers still reveal context. Use application locking together with the system lock screen.
Version and signature maintenance
Session Desktop 1.18.1 offers Windows, macOS, Linux and FreeBSD builds. Before upgrading, check system requirements and a trusted hash or signature record, and keep a recoverable configuration copy.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Session Desktop 1.18.1 to this cloud drive
Baidu Netdisk
Save Session Desktop 1.18.1 to this cloud drive
Session Desktop installation, verification and recovery guide
Verify the package and recovery material first, test messages and attachments on a separate account, then migrate a production account only after recovery works.
Before you start
- Select the matching Windows 10+, macOS 13+, Linux glibc 2.35+ or FreeBSD build.
- Save the recovery phrase offline in a location separate from the computer and never paste it into a chat or screenshot.
- Prepare two devices and a test contact for recovery, messaging, attachment and sign-out checks.
Installation steps
- 01
Install and verify the build
Install the matching platform package, compare its trusted hash or signature record and confirm the architecture and minimum system version.
- 02
Create a test account
Create an account in an isolated workspace, record the identifier and recovery phrase, enable local locking and send a test message.
- 03
Check network and attachments
Test short messages, offline queueing and a small attachment while observing delivery delay and Service Node state.
Quick start
- 01
Configure notifications and locking
Allow only required notifications, set an automatic lock interval and lock or exit before leaving a shared computer.
- 02
Recover on a second device
Use the recovery material on the test device, compare messages, contacts and attachments, and keep the old device until the result is confirmed.
- 03
Record backup and update state
Note version, system, recovery-test date and known issues; preserve the old configuration before upgrading.
Usage tips
- A recovery phrase grants account recovery and should be stored offline and tested periodically.
- Distributed routing reduces some network exposure but does not remove local-device, screenshot, notification or contact metadata.
- Service Nodes, client versions and network conditions affect delivery time; keep independent copies of important attachments.
Troubleshooting and uninstall
What if a message stays pending?
Check the network, application lock, client version and Service Node state, then retry with a short message rather than sending repeated large batches.
Why are old messages missing after recovery?
Confirm the recovery phrase and account identifier, wait for synchronization and keep the old device and local configuration as a recovery source.
- Finish account migrationVerify the recovery phrase, messages and attachments on the new device and confirm the old device is no longer the only recovery source.
- Exit and clear local dataSign out through Session, uninstall through the system manager and clear configuration only after the recovery material has been stored separately.
Frequently asked questions
Does Session require a phone number or email?
It uses a locally generated account identifier and recovery material, so its account flow differs from traditional phone-based registration.
What does onion routing protect?
It can reduce direct network-address exposure between participants, while device, timing, Service Node, push and local-system metadata remain separate boundaries.
What should be done before replacing a computer?
Verify the recovery material on the new device, check messages and attachments, and keep the old configuration until the migration is confirmed.
Where should the recovery phrase be stored?
Keep it offline in a protected location separate from the device and never expose it in chats, screenshots or public backups.