Element

Element is a Matrix messaging client for individuals, communities and organizations. The desktop application wraps Element Web and connects to a Matrix homeserver, allowing communication across participating federated servers when server policy permits it.

Communication tools

• Send direct messages and participate in group rooms and Spaces.
• Share files, use threads, reactions, polls and searchable conversations.
• Use end-to-end encrypted rooms and verify devices or recover encrypted history.
• Join supported voice and video calls using the services configured by the deployment.
• Manage room membership, notifications, account profiles and multiple desktop profiles.
• Connect to a chosen homeserver, including organizational or self-hosted deployments.

Installing the desktop app

Download the official macOS archive and place Element in Applications, or use brew install --cask element. The current cask requires macOS 13 or later. The exact 1.12.30 universal Mac ZIP is 280,426,177 bytes, verified by HEAD against the official packages.element.io asset; it is the universal macOS distribution rather than an architecture-specific build. Local caches, downloaded files and encrypted-message indexes require additional disk space. The checked product and repository sources do not give a numeric minimum RAM for this release. Windows and Linux desktop builds and separate native mobile clients are available. A packaged desktop build does not require a user-installed Node.js toolchain; building the source does. The cask declares no named conflict.

Accounts, network and services

You need a Matrix account on a reachable homeserver. Registration, SSO, invitations and allowed integrations depend on that server's policy. Element's open-source app can be used without buying a desktop-app subscription, while hosted services, enterprise products, support and some deployments have paid plans and separate terms. The repository offers AGPLv3-or-later or GPLv3-or-later use, or an Element commercial license; this does not make a hosting service free of charge.

Messaging and synchronization require network access to the homeserver, and federation, media downloads, calls and integrations may contact additional services. Offline access is limited to cached data and is not a substitute for a functioning server. The chosen server can retain account and room metadata, and users should inspect the homeserver's privacy and retention rules. End-to-end encryption protects supported encrypted content, not every piece of metadata or every room by default.

Permissions and recovery

Allow notifications if desired, microphone and camera access for calls, and Screen Recording only when sharing a screen. Keychain access is used by relevant desktop credential-storage workflows; denying it should not be handled by granting unrelated blanket file permissions. File access is needed for selected uploads and exports. Keep encryption recovery keys securely: an account password alone does not guarantee recovery of encrypted history. Verify devices before trusting sensitive conversations, understand room membership and federation, and review public-room warnings. Shared files, exports and notifications can reveal information outside the encrypted room. Bridges and integrations introduce their own trust boundaries. The current release fixes a Windows/macOS crash when Keychain access is denied and improves recovery behavior.

Sources: Official downloads, Official app, Source and supported environments, Official releases.