Analysis

Discord is rebuilding its desktop app in Rust and dropping Electron; an early Windows build shows 290 MB of RAM

Discord's CTO confirmed a Rust rebuild without Electron. One early Windows screenshot shows 290 MB of RAM, but no release date or benchmark exists yet.

By ·

On November 5, 2026, Discord co-founder and CTO Stanislav Vishnevskiy confirmed on X that the company is rebuilding its client in Rust, with the GPUI framework drawing the desktop interface and Electron removed. An early Windows 11 build, labeled "Discord Phoenix" in a screenshot, showed 290.2 MB of RAM. It is a plan and a single early screenshot, not a shipped app: no release date has been announced and the figure comes from one capture whose conditions are not stated.

The essentials

What did Discord actually say?

Vishnevskiy said Discord has used Rust since 2018 for much of its infrastructure, voice technology and even parts of the current client, and that moving the whole client was the goal. His wording, as relayed: "Electron goes away, and so does React Native." He also said the plan is not Tauri, which typically uses the operating system's web view; with GPUI, Discord draws its interface natively. The statement is a confirmed direction, not a release.

What does the 290 MB figure show?

Less than the headlines suggest. It comes from one early screenshot of a build labeled Discord Phoenix, and Windows Latest says it does not know whether the number reflects idle use, which accounts were signed in, or whether servers were open. Digg's summary notes that one example does not establish typical savings. Some coverage computes "93% less memory" by comparing with the 4 GB worst case; that compares a single early reading with a peak, so it is not a fair measurement. Another relay lists the current client at 600 MB or more at idle against 290.2 MB, also without a controlled test.

How heavy is the current app?

Discord has acknowledged that its Windows app can reach 4 GB, and in December 2025 a Discord employee said it was testing an automatic restart above 4 GB, adding that normal usage is below 1 GB. Windows Latest's author reports roughly 1 to 2 GB for his own idle background use, from personal use and not a controlled benchmark. Discord reports a 5% cut in 95th-percentile memory so far and attributes some issues to platform, driver and hardware layers.

What is not established?

Summary table

Summary table
PointWhat is stated as of November 6, 2026Source
DirectionFull client rebuilt in Rust, Electron removedWindows Latest, 9to5Windows
InterfaceGPUI, not TauriWindows Latest
MobileReact Native removed, native UI, shared code via RustWindows Latest, ShiftDelete
Early build RAM290.2 MB, one screenshot, conditions unstatedWindows Latest, 9to5Windows
Current app peakUp to 4 GB, Discord says normal use under 1 GBWindows Latest
ReleaseNo date announcedMLQ, BigGo

FAQ

Is the new Discord app available?

No. Only an early screenshot has been shared and no release date or public test has been announced.

Does the Windows app now use only 290 MB?

Not the current app. 290.2 MB is the reading in a screenshot of an early build of the Rust rewrite.

Why does Electron use so much memory?

Electron bundles a full browser engine with every app, which adds memory overhead; Discord's own app history shows how that can grow over time.

Method and limits

Sources checked on November 6, 2026. We read the Windows Latest article in full and search extracts of the other pages; we did not read Vishnevskiy's X post, The Verge's report, or any Discord engineering post directly. The 290.2 MB figure is a single screenshot and not a benchmark.

Sources

Spotted an error in this article? Report it · Our corrections policy

Rekha icon: a house drawn in a single stroke

From the same author Self-promotion

An Eulerian path, drawn with your finger

Rekha, the iPhone game by OrigoTech's author: connect every dot in a single stroke without tracing the same link twice, across 500 drawings that are all solvable.

The OrigoTech newsletter

A sourced weekly digest of AI tool news.

Read next