XMPP: getting started with portable encrypted communication
XMPP is not a replacement for Signal or WhatsApp as a daily messaging app. It solves a different problem: communication that works on any device you already own, without a phone number, without an approval flow, and without everything depending on one specific smartphone.

XMPP: getting started with portable encrypted communication
XMPP is not a replacement for Signal or WhatsApp as a daily messaging app. It solves a different problem: communication that works on any device you already own, without a phone number, without an approval flow, and without everything depending on one specific smartphone.
An XMPP account works on multiple devices simultaneously — an old Android phone, a laptop, a desktop. You can send messages, make voice calls and video calls, end-to-end encrypted once both sides use OMEMO (step 4). And if your phone is temporarily unavailable, you log into another device and carry on.
This guide gets that working. It assumes a fresh setup; already have an XMPP account? Skip to step 2 and log in with it.
Who this guide is for
This guide is for readers who:
- want an extra communication channel that works without a phone number or tied account
- want to stay reachable if their primary phone is temporarily unavailable
- want encrypted communication on a device they already own — including an old phone or laptop
- are curious about an open alternative to Signal or WhatsApp without locking into one platform or one device
This is not a guide for everyday messaging with friends or family. XMPP works best as a backup channel, a second line, or a communication tool within a small trusted group willing to spend a few minutes setting it up.
What to expect
XMPP is an open protocol, not a single app. That means dozens of clients exist — for Android, iOS, desktop, even the terminal — but quality and encryption support vary a lot. This guide names one maintained client per platform, so you do not have to sort through a long list yourself.
OMEMO encryption starts on its own in Conversations, but at first it trusts your contact’s keys blindly. To be sure nobody slipped in a key of their own, you verify each contact once by scanning their QR code (step 4). After that, Conversations asks you to confirm any new device that contact adds.
Encryption covers the content of your messages, not who you talk to and when: your server sees your contact list and when you are online (see “What your server sees” below).
What you need
- an XMPP account (free on many servers, no phone number required)
- a client app on your device
- a contact to communicate with
That is all.
Step 1: create an account
You choose a public XMPP server. These work like email providers: your account will look like name@servername.com. You can message anyone regardless of which server they use — servers communicate with each other through federation.
Where to look:
- providers.xmpp.net rates public servers. Category A means: best rated, free, and you can register from the app.
- jabber.de — per providers.xmpp.net: free, running since 2001, run by a private person, server in Germany, no password reset, messages kept 60 days.
- conversations.im — run by the Conversations developer and an ejabberd contributor, servers in Germany. Not free: accounts have a payment period. You can add an email address for password recovery.
You can register in the app itself (in Conversations: Create Account) or on the server’s website. jabber.de and conversations.im ask for a username and password; no phone number, and no email address unless you add one.
Keep your password safe: on many servers, jabber.de among them, there is no way to reset it. A server can also close down, and your address goes with it. Want to be able to move later? An address on your own domain lets you switch providers.
Step 2: install a client
Android
Conversations is the usual choice for Android. Actively maintained (2.21.0, October 2026), with OMEMO encryption, voice calls and video calls.
- F-Droid: free. The developer’s advice: if you already use F-Droid, take this version. It adds address book integration and public channel search, and never uses Google push.
- Google Play: listed as free (read November 2026). Instead of those two features it has a Google push fallback, used only when the app’s own connection fails; the push carries no message content.
Using an old phone from a drawer: Conversations works on Android 6.0 and above.
iOS
Monal is a maintained option for iPhone and iPad (6.4.24, October 2026). Free on the App Store, supports OMEMO and audio and video calls. It also runs on macOS.
Desktop (Linux, macOS, Windows)
Gajim runs on Windows, Linux, and macOS and supports OMEMO (2.7.0, November 2026). On Linux it is available as a Flatpak and through distribution packages.
Step 3: log in and set up multiple devices
Open the client and log in with your XMPP address and password. In Conversations, choose I already have an account on the first screen (later: Manage accounts → Add existing account). In Gajim: Add Account….
Want to use the same account on a second or third device? Install the client on the other device and log in with the same address and password. With modern clients and servers, all devices receive your messages.
Each connection has its own resource, the part after the slash (for example name@server.com/phone). You normally don’t need to set it: Conversations has no field for it, and Gajim picks a random one (gajim. plus random characters). If you change it in Gajim’s account settings (Resource), keep it different on each device: when two connections ask for the same resource, the server decides what happens, and one of the options is that it disconnects the older one.
Step 4: enable OMEMO encryption and confirm trust
OMEMO is the end-to-end encryption layer for XMPP. It uses the Double Ratchet, the same ratchet Signal uses. In Conversations it is on by default for new chats, as soon as your contact’s client supports OMEMO too.
Check that it is on. The text field in a chat says Send encrypted message when OMEMO is on, and Send clear text message when it is off. The lock icon at the top of the chat lets you choose between Clear text and OMEMO. Without OMEMO, your server administrator can read your messages.
Verify your contact once. Conversations starts with Blind Trust Before Verification: it trusts new keys of contacts you haven’t verified. That keeps things simple, but someone with access to a server could add a key of their own. So verify the people who matter: meet or call, open the contact’s Contact details and tap Scan QR Code to scan their code. Once you have verified a contact, Conversations asks you to confirm each new device they add. Gajim also starts with blind trust.
OMEMO also encrypts files and voice messages you share. In group chats it only works in private groups (members only, with participants’ addresses visible), not in public channels. In Conversations: Create private group chat.
What your server sees. OMEMO doesn’t hide metadata. Your server keeps your contact list, and by default an archive of your messages and shared files (encrypted if OMEMO was on): conversations.im keeps the archive and files for 90 days, jabber.de keeps messages for 60 days. Choose a server you trust.
Voice and video calls
Conversations supports voice and video calls. In a chat, tap the call icon (left of the lock icon) and choose Audio call or Video call. The icon only appears when you have each other in your contact lists, your contact is online with a client that supports calls (Conversations, Siskin, Dino, Movim and others), and your contact doesn’t have Tor switched on in Conversations.
Important to know about calling: calls need a direct connection between the two devices. On many networks your server has to help, with a STUN or TURN server. If you see Could not connect call, check under Manage accounts → your account → menu → Server info whether XEP-0215: External Service Discovery is available. That is how a server offers this help. If it isn’t, calls on restrictive networks can fail; the developer saw this often on mobile networks.
Gajim on the desktop also has audio and video calls; whether they work with Conversations isn’t documented on the pages we read.
Adding contacts
Share your XMPP address (name@server.com) with whoever you want to reach. They add it in their client (in Conversations: Add contact) and send a contact request. You confirm, and the conversation can start. Accept each other: calls need you in each other’s contact lists, and OMEMO keys may not load without it.
There is no central search function — you share your address deliberately, like an email address.
Stopping point
Account created, client installed, OMEMO active? You now have a working encrypted communication setup that runs on any device you already own — including that old phone in a drawer.
Nothing else needs configuring unless you want to go further. Want full control? You can also run your own XMPP server. The Conversations developer recommends Prosody (easy to set up and light on system resources, by its own description) or ejabberd (built for scale). That is a step beyond this guide; given Prosody’s low resource use, a Raspberry Pi or a cheap VPS should be enough (our estimate). For calls, your own server also needs a STUN/TURN server. For everyday use as a backup channel, a public server is enough.
Next step
More alternatives without a phone number
- SimpleX Chat: messaging without an account or identity
- Session: encrypted messaging without a phone number
When your phone is not at hand
- What happens when your primary device disappears — picking up an old phone and carrying on, because the account isn’t tied to one device