Element Desktop
Element Desktop 1.12.13 is a Matrix client for rooms, direct messages, voice and video calls, and device verification. This page explains homeserver selection, encrypted rooms, and migration boundaries.
What Element Desktop provides
Element Desktop brings Matrix rooms, direct messages, calls and file sharing into a desktop client. A client and a homeserver are separate layers, so account policy, retention, federation and encryption behavior still depend on the selected service.
Device verification and migration
Encrypted rooms depend on device keys and recovery material. Verify a new device before using it for important conversations, keep recovery information separate, and test message history before retiring an older device.
Maintenance note
This page reviews Element Desktop 1.12.13 for Windows, macOS and Linux, including the archived desktop repository context, homeserver selection, encrypted rooms and migration checks. Content review date: 2026-08-23.
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 Element Desktop to this cloud drive
Baidu Netdisk
Save Element Desktop to this cloud drive
Element Desktop 1.12.13 installation, verification and migration guide
Use a test account to verify the homeserver, device keys, encrypted rooms and file sharing before moving important conversations to a new device.
Before you start
- Prepare the Windows, macOS or Linux package and a test account with recovery material.
- Confirm the homeserver, invitation policy and organization security requirements before signing in.
- Keep two test devices available so device verification and encrypted history can be checked.
Installation steps
- 01
Install and select a homeserver
Install the platform package, enter the homeserver used by the account, and verify the login page and organization identity.
- 02
Verify the new device
Use an already trusted device or recovery material to verify the new device, checking its name, fingerprint and encryption state.
- 03
Test a room and a file
Join or create a test room, send text, an image and a file, then confirm synchronization, download behavior and local permissions.
Quick start
- 01
Organize rooms and notifications
Use spaces and rooms for projects, then set notification levels and mute rules so routine messages do not become urgent alerts.
- 02
Confirm encrypted recovery
Restore test history on the new device and confirm keys, verification status and messages before removing the old device.
- 03
Record the service boundary
Save the homeserver, recovery method and migration date so a future issue can be separated into client or server behavior.
Usage tips
- Matrix clients and homeservers are separate components; server logs, retention rules and account policies affect message availability.
- Keep recovery material after verification. Losing every device and recovery source can make encrypted history inaccessible.
- An archived desktop repository requires extra attention to security updates and a migration plan for important communication.
Troubleshooting and uninstall
Why is encrypted history missing on a new device?
Check device verification, recovery keys and whether the old device is still online. Keep the original device until the new one has passed a history test.
Why do messages or files not synchronize?
Check the selected homeserver, account session, network and room permissions, then reproduce the issue in a small test room before changing encryption settings.
- Export and verify important dataSave required room records and recovery material, then test the export or migration copy before removing the client.
- Remove the client and local cacheSign out, uninstall through the operating system, and clear local cache only after confirming that the account and recovery data remain available.
Frequently asked questions
Does Element Desktop provide its own Matrix server?
No. The client connects to a homeserver selected during sign-in. Server federation, retention and account policy are controlled by that service.
Does encryption cover every room automatically?
Encryption depends on room settings, device keys and verification. Complete verification and keep recovery material instead of relying only on a visual lock indicator.
What should be saved before changing devices?
Save recovery material, verify the new device and test encrypted history before signing out or removing the old device.