Threema Web was built to give you quick access to your messages via a browser. But browser sessions time out. Tabs get closed. And if your phone disconnects from the session, you need to start it all over.
Threema 2.0 for desktop (beta) eliminates these issues. Designed for long (work) sessions, it offers stable performance and a seamless workflow across devices.
| Comparison | Threema for Desktop | Threema Web |
|---|---|---|
|
Standalone app |
||
|
End-to-end encrypted communication |
||
|
Works without a constant connection to a smartphone |
||
|
No metadata collected |
||
|
Independent of browsers and sessions |
||
|
Secure media and file sharing |
The desktop app runs independently of the browser and keeps your chats available even when your phone is turned off or not connected to the Internet. No more unexpected disconnects, QR rescans, or session timeouts. Just smooth, uninterrupted messaging.
The new desktop app has a significantly faster response time. Switching between chats, sharing files, and searching your history feels instant. It’s built for everyday desktop use – not just for the occasional browser session.
Notifications integrate with your operating system, files can be dragged and dropped right into conversations, and shortcuts boost typing speed. Everything works the way a modern desktop tool should – on Linux, macOS, and Windows.
To chat from the computer, you can either use the desktop app or the web client (“Threema Web”).
In both cases, you need the Threema mobile app (for Android or iOS), and your mobile device must be connected to the Internet.
Hint: To avoid having to scan the QR code each time you (re)start the desktop app / web client, set a session password in the browser before scanning.
Both the desktop app and the web client allow you to use Threema on a desktop computer. You need the mobile app (for Android or iOS) in both cases, and your mobile device must be connected to the Internet.
Learn how to use the desktop app and the web client →
The desktop app is available for macOS, Windows, and Linux. The web client can be used in most web browsers. In terms of features, there’s no difference between desktop app and web client. Since they are based on the same architecture, they also share the following characteristics:
In terms of security, the desktop app offers slight advantages. For one thing, there’s no way for browser plugins to introduce vulnerabilities. For another, it would be even more difficult for attackers to manipulate the app code since it isn’t loaded from a server each session but permanently stored on the user’s end.
For detailed technical information in regard to security, please refer to the Cryptography Whitepaper.
The desktop app and the web client currently provide the following features:
