← Back to all sparks
E

Element Call

MEETINGS
Velocity5.0

Open-source end-to-end encrypted group video calling built on Matrix

With the protocol cutover behind it, Element Call is back to polishing the in-call experience.

matrixwebrtcvideo callsopen sourceembedded widgets
◆Current state
Element Call finished its architectural transition this summer: multi-SFU routing became the default in v0.21 and MatrixRTC legacy mode was removed in v0.25. The releases since are smaller: audio output defaults, delayed-leave timing tweaks, and now a quick audio menu and bell reaction sound in v0.28.
◆Where it's heading
The team is moving from protocol plumbing to call ergonomics and embedding. Recent work targets audio controls, reactions, and the embedded component used inside Element Web, along with privacy hygiene such as redacting analytics IDs from bug reports. Release cadence has stretched to roughly two to three weeks per release candidate.
◆Prediction
Expect more in-call controls and embedded-widget fixes in the next release candidates. A new breaking change looks unlikely while the post-cutover stack settles.

◆Recent moves

  1. 12d ago

    Quick audio menu, bell reaction sound and redacted analytics IDs

    A quick audio menu and a bell reaction sound make in-call controls faster to reach, and analytics IDs are now redacted from rageshake reports. The release also fixes tooltips in embedded mode, a sign the Element Web integration is getting attention.

    View source ↗
  2. 26d ago

    v0.26.1-rc.1

    Falls back to the browser's default audio output when none is chosen and ties member IDs to the MatrixRTC mode. Small cleanup after the protocol transition.

    View source ↗
  3. 1mo ago

    v0.26.0-rc.2

    Delayed-leave timings now adapt when delegation is available, so departures register more reliably on the new protocol. It is marked breaking because it changes behavior that deployments depend on.

    View source ↗
  4. 1mo ago

    v0.26.0-rc.1

    Screen-share failures now surface instead of failing silently, and per-connection LiveKit logging lands. These are debuggability gains for the multi-SFU stack the project now depends on.

    View source ↗
  5. 1mo ago

    MatrixRTC legacy mode removed — all calls now run on the new protocol

    ⚡ SPARK

    Removing MatrixRTC legacy mode closed out the protocol transition that began with multi-SFU in v0.21, and it shipped with a batch of large-call performance fixes. Everything since has been built on the single remaining protocol.

    View source ↗
  6. 2mo ago

    v0.24.0-rc.1

    Advanced media-quality settings and React Compiler performance gains shipped next to the removal of .well-known transport discovery, one of the steps that cleared the way for the v0.25 cutover.

    View source ↗