Element Shows “Failed to Decrypt”? Restore the Missing Room Key

If Element Web shows “Failed to decrypt event,” check whether that same event opens on another device you trust. If so, restore keys on the browser using Secure Backup or that trusted device. Do not clear browser storage, sign out of your last working session, or reset your digital identity before checking recovery options; you could lose your remaining keys.

Why can one encrypted event fail to decrypt?

Matrix stores encrypted room events on the homeserver, but the homeserver does not hold the plaintext decryption keys. For group chats, clients share room-session keys with participating devices. A client that never received the relevant key cannot turn that event into readable text, even if it can display newer messages. The Matrix end-to-end encryption guide describes this device-level key sharing and key requests.

The message is a symptom, not a diagnosis. If only a new browser or device shows it, start with that session's key backup. If every device fails, no device you still control may have received the key, or the event may predate your access to the room. A missing key differs from a bad password or a slow network.

A Matrix room timeline contains an event labeled Unable to decrypt this message.
Compare the affected event. One unreadable event among readable messages suggests a missing key for that event, not necessarily a room-wide outage. Exact error text varies. Conceptual UI mockup.

Which recovery option fits your situation?

OptionBest fitTrade-off
Restore with Secure Backup recovery keyA new browser or device needs older keys and you have the recovery key.Restores keys that were backed up; it cannot recreate keys that were never backed up or shared.
Verify from another trusted deviceYou still have an active, verified Element session.Avoids typing a recovery key, but the other device must be available and have the needed keys or be able to respond to a key request.
Ask a room participant or original senderOnly a particular event is missing and another participant can read it.They may be able to share a key or resend the information, but they cannot recover a key they do not have.
Reset the digital identityYou have no working recovery key and no verified session.Last resort: Element warns that prior encrypted history may become inaccessible and contacts can see an identity change.

Choose the least destructive option you still control. Clients can request keys from other devices, but a device must possess the key to share it. A person joining an encrypted room later may not decrypt earlier events if the key was never shared; refreshing will not create it.

How do you restore keys on Element Web?

  1. Compare sessions before changing anything. Open the affected room on another signed-in device you trust. If the event decrypts there, keep that session open and use it as the recovery route. If it fails everywhere, note whether other messages in the same room still work and whether the problem is limited to one event.
  2. Element Web's Sessions screen shows a current session and its verification status.
    Check this browser session. In Element Web, open the profile menu, choose All Settings, then Sessions. Confirm which session is current and verified. This is a conceptual UI mockup; layouts vary by release.
  3. Check this browser's verification state. In Element Web, open your profile avatar, choose All Settings, then Sessions. Find Current session and look for the green shield that Element documents as a verified session. If it is unverified, select Verify session. Element documents verification with another device or with a recovery key; choose the first if you can approve the prompt on a trusted session, or the second if you have your recovery key.
  4. Element Web offers verification with another device or a recovery key.
    Choose a verification path. Element documents another verified device or a recovery key. Verification establishes trust; it does not guarantee every old room key is already on this browser. Conceptual UI mockup.
  5. Restore the backup when the key is available. Element's recovery-key instructions distinguish the key from your account password. In All Settings → Encryption, check Backup. When prompted, use the key saved during Secure Backup setup. Never paste it into a support ticket, chat, or third-party site. If a verified session remains but you have no saved key, use it to get or set up one now.
  6. Element Web's Encryption settings show the Backup section and recovery-key controls.
    Locate the recovery key. Element's current guidance places Backup under All Settings → Encryption. Keep the key private. Conceptual interface mockup, not a live account screenshot.
  7. Let the client request keys, then reopen the room. Keep both the recovering browser and trusted device online, allow them to sync, and accept a key-sharing prompt only when you recognize the requesting session. Reopen the affected room or reload Element once after synchronization. Avoid clearing site data: browser storage can contain encryption state that has not yet been restored from backup.

Labels may vary by release. Element's device-verification instructions document the Sessions route and both methods. For a customized build, follow its administrator's equivalent settings.

What if only one event still fails?

Check whether another verified device can read that exact event, not just whether it can open the room. If it can, keep that device available and use the client's key-sharing or verification flow. If no device can read the event, ask the sender or another participant who can decrypt it to share the information again. For a message sent before you joined, the room's history-sharing policy and whether anyone retained its key determine what can be recovered. No administrator can decrypt a message merely by changing a homeserver setting.

Resetting your digital identity should be the final fallback. Element's account-security guidance warns that losing all recovery methods can mean losing access to encrypted messages. A reset does not decrypt old events; it creates new cryptographic identity material. If you still have any verified device, preserve it and seek help from Element's official support guidance before resetting.

How can you confirm the fix?

After restoration or verification, confirm the browser session is verified, reopen the room, and test the exact event plus a recent encrypted message. If newer messages work but an older event still fails everywhere, the session is fixed but that event's key remains unavailable. Keep your working session and recovery key safe while asking whether a participant can provide the content.

Leave a Comment

Element Shows “Failed to Decrypt”? Restore the Missing Room Key

Element Shows “Failed to Decrypt”? Restore the Missing Room Key

Find out whether the error is limited to one browser or one event, then use Element’s recovery key or a trusted device without risking your remaining encrypted history.

Clean Up Old Synapse Messages and Media Without Losing Data

Use Synapse’s history and media purge APIs or retention settings to remove stale data safely, then verify completion and disk-space recovery.

Build a Matrix Echo Bot in Python with Simple-Matrix-Bot-Lib

Build a Matrix Echo Bot in Python with Simple-Matrix-Bot-Lib

Install the current library, connect a dedicated Matrix account, and run a small !echo bot with safer credential handling and a clear test.

Connect Matrix to WhatsApp, Telegram, and Discord with Separate Bridges

Connect Matrix to WhatsApp, Telegram, and Discord with Separate Bridges

Set up three mautrix bridges with separate registrations, logins, and tests—and avoid Docker networking, account-policy, and sync surprises.

Reclaim Synapse Media Disk Space Without Breaking Shared Files

Find what is filling Synapse storage, set safe media retention, and purge remote cache without deleting files directly from disk.

Deactivate Inactive Matrix Users Without Deleting Room History

Deactivate Inactive Matrix Users Without Deleting Room History

Review device activity, deactivate confirmed inactive Synapse accounts through the Admin API, and learn what the optional erase flag actually removes.

Reduce PostgreSQL Memory Pressure in Matrix Synapse

Find whether PostgreSQL memory comes from query work, shared buffers, connections, or maintenance, then make targeted Synapse-safe changes.

Why Matrix Synapse Room Joins Are Slow—and What to Check

Why Matrix Synapse Room Joins Are Slow—and What to Check

Trace slow Matrix room joins to one remote homeserver, federation backoff, local database load, or an outbound sender queue before changing Synapse settings.

Close Matrix Sign-Ups or Require Invite Tokens on Synapse

Stop open account creation on a self-hosted Synapse server, or keep sign-ups invite-only with limited-use registration tokens.

Element Session Identity Warning: Verify Your Login Safely

Clear Element's unverified-session warning using a trusted device or recovery key, with checks that protect your encrypted chat history.