What did Discord announce?
Discord is rebuilding its desktop and mobile clients in Rust, the company's chief technology officer said on November 4, 2026. The announcement came in a post on X from co-founder Stanislav Vishnevskiy, and three outlets covered it within a day.
A day earlier, Inven Global reported, Vishnevskiy had told a user that the team was “busy with a much bigger update.” The confirmation followed hints that the desktop client would move away from Electron.
The change is unusually broad for a consumer chat app. Discord's desktop client will stop using Electron, the framework that wraps a web app in its own browser engine. Its mobile apps will stop using React Native, Meta's framework for building native-looking apps with JavaScript.
Vishnevskiy wrote that Discord has used Rust since 2018. Much of its infrastructure, its voice technology, and part of the current client already run on the language, he said.
Windows Latest reported that an early build is codenamed Discord Phoenix. A screenshot shared by the CTO showed the Windows client using 290.2 MB of memory, according to the outlet and Inven Global.
The three reports trace back to the same X thread. None cites a press release, and Inven Global noted that Discord had not published its own announcement.
There is no release date. Vishnevskiy said the team hopes to get the client “into testing with users soon,” Inven Global reported.
Why is Discord ditching Electron?
Electron is popular because it solves a staffing problem. Developers write one JavaScript, HTML, and CSS codebase, and Electron embeds Chromium and Node.js so the same app runs on Windows, macOS, and Linux.
The trade-off is that every Electron app ships its own Chromium copy. It cannot reuse the browser already installed on the machine, so the app carries a large runtime even when its window is idle.
Electron also inherits Chromium's multi-process design. A main process runs the Node.js side of the app, and each window renders in a separate process, according to Electron's documentation. That structure limits the damage from a crashed page, but it multiplies the baseline overhead of a chat client.
Discord has felt that cost for years. Windows Latest's editor says the app sits at 1–2GB of memory while idle on his machine. The Verge notes that usage can pass 1GB with only a few servers open.
Discord has acknowledged worse cases. A company employee wrote on Reddit in December 2025 that it was testing an automatic restart when memory passed 4GB. “Yes, we're testing a restart when memory exceeds 4GB (normal usage is <1GB),” the employee wrote, as quoted by Windows Latest.
The same report cites a company update claiming a 5% reduction in p95 memory usage, with more work to do. Discord also said it had found problems at the platform, OS, driver, and hardware level with partners.
Those fixes treated symptoms. Moving the client to Rust changes the foundation, which is why the CTO's post drew attention beyond Discord's user base.
Windows Latest also reports that the new client should skip the Starting screen, because it no longer has to load Electron libraries. That detail comes from the outlet's reporting, not from Discord's post.
How much RAM does the new Discord client use?
The headline number is 290.2 MB. That is what Task Manager showed for the Discord Phoenix build in the screenshot Vishnevskiy shared, according to Windows Latest and Inven Global.
The figure comes with context that cuts both ways. Inven Global reported that the client in the image was running two accounts at once, a feature the new app supports. That makes the reading more impressive than a single-account test, if the screenshot is representative.
It probably is not representative of every session. A screenshot captures one moment, on one Windows machine, with an unfinished build. Memory use grows with servers, voice calls, video, and embedded activities, and none of those workloads appear in the reported test.
No outlet has published a controlled benchmark against the Electron client. The 290.2 MB figure should be read as a demonstration, not a specification.
Measurement method matters too. Task Manager's reading is a snapshot of how Windows accounts for a process, and the number came from Discord itself rather than an outside lab. Discord has not said what hardware produced the reading. Reviewers will need to repeat the test with the same server list, call load, and hardware before comparisons hold.
Rust's design offers a plausible reason for lower overhead. The language has no garbage collector or runtime, and its ownership model enforces memory safety at compile time, according to the Rust project. Those properties remove a class of pauses and leaks, but they do not cap what an app stores.
Vishnevskiy told a user that he expects performance to be better, Inven Global reported. The honest answer to how much memory the new Discord will use is that nobody outside Discord knows yet.
What is GPUI, and why isn't Discord using Tauri?
Some observers guessed Discord would use Tauri, another Rust desktop framework. Vishnevskiy rejected that guess: “And it's not Tauri, it's GPUI, so good guess everyone,” Windows Latest quoted him saying.
GPUI is the interface framework built by Zed Industries for its code editor. Its README describes it as a GPU-accelerated framework for Rust that mixes immediate and retained rendering modes. It is still pre-1.0 and changes often between versions.
The distinction matters. Tauri keeps a web front end and displays it in the operating system's webview. Its own documentation lists a smaller bundle size through the system webview as a main advantage. GPUI draws the interface itself, so Discord is replacing its rendering layer, not just the shell around a web page.
Electron gave Discord more than a packaging format. It supplied Chromium's layout engine, text rendering, input handling, and media stack, all maintained by a large engineering organization. Discord rented that machinery and paid for it in memory.
Replacing it with GPUI means Discord now depends on a much younger framework. GPUI's README warns that it is still in active development, pre-1.0, and subject to breaking changes between versions. Discord is not just adopting GPUI; it is patching it.
Vishnevskiy said the app is native and uses the system webview only for embedded content such as YouTube and Activities, Inven Global reported. He told a bot developer that “The app looks and works identically to the current one.”
Discord maintains its own patches on top of GPUI. Vishnevskiy said the company will see what it can contribute back to the project, according to Inven Global.
That arrangement gives Discord control over rendering, input, and animation without asking a framework team for changes. It also makes Discord responsible for bugs that a mature browser engine would have fixed years ago.
Building a chat client on a pre-1.0 framework carries risk. Discord is betting that control over rendering is worth the maintenance burden, and that its patches can track upstream changes.
What happens to React Native on mobile?
On mobile, the change is less visible but still significant. Discord will keep native UI on iOS and Android, but share app code with desktop through Rust, according to the CTO's post.
Inven Global reported that Discord's iOS app started on React Native. The Android app moved to React Native a couple of years ago because it kept falling behind on features.
Removing React Native means one core written in Rust, with platform-specific interfaces on top. That should reduce duplicate logic across three operating systems, at the cost of maintaining two UI layers.
React Native's promise was to let a JavaScript team ship on both mobile platforms. A shared Rust core moves that logic out of JavaScript and into code all three platforms compile.
The mobile work also has no published schedule. Vishnevskiy's testing comment did not specify platforms, and Inven Global noted that Discord has not published its own announcement.
For users, the practical question is whether mobile performance and feature parity improve. For Discord's engineers, the question is whether a shared Rust core simplifies releases or creates a new bottleneck.
Discord's Rust history explains why this was possible
This is not Discord's first Rust migration. In February 2020, the company published an engineering post explaining why it moved its Read States service from Go to Rust.
Read States tracks which channels and messages a user has read, and it sits on the hot path of every connection and message. The Go version was fast most of the time, but latency spiked roughly every two minutes. Discord traced the spikes to Go's garbage collector.
The port to Rust was completed in May 2019, according to the post. Discord said average times were measured in microseconds, with maximum @mention times in milliseconds.
The scale described in that post is a reminder of how much traffic Discord handles. It reported billions of Read States, one per user per channel. Each cache held millions of users and tens of millions of Read States, with hundreds of thousands of cache updates per second.
The same post lists earlier Rust work: the game SDK, video capture and encoding for Go Live, Elixir NIFs, and several backend services. It also includes a caution that Discord does not think teams should rewrite everything in Rust “just because.”
The post also praises Rust for refactoring. Discord wrote that type safety and the borrow checker make it easier to change code as product requirements evolve. A client rewrite that runs for years depends on exactly that property.
That history explains why the client rewrite is credible. Discord already runs Rust in latency-sensitive paths, so the new work extends an existing practice rather than starting from zero.
It also sets the bar. A backend service can be swapped with limited user impact, but a desktop client touches every feature, every platform, and every user at once.
What could go wrong, and what to watch next
The CTO says the new app should look and work identically to the current one. That sets a high bar. Every dialog, drag target, keyboard shortcut, and embedded activity has to survive the move on each platform.
That helps explain why the project arrived with hints rather than a launch. Rewriting a backend service is contained, but rewriting the interface touches everything users see and every platform team that supports it.
The biggest unknown is timing. Discord has promised testing soon but has not committed to a date, a beta program, or a migration path for the existing app.
Platform coverage is also unstated. The screenshot was from Windows, and Electron supported Windows, macOS, and Linux. Discord has not said publicly whether the Rust client will ship on all three at once.
The existing Electron app will not disappear overnight. Discord has not described how it will run both clients, migrate settings, or handle users who cannot update immediately. Those operational details will matter as much as the memory figure.
Embedded content remains a dependency. YouTube videos and Activities will still run in the system webview, according to Inven Global, so some memory use will remain tied to web technology.
Independent testing is the next real test. A 290.2 MB idle reading is encouraging, but users will judge the app during calls, screen shares, and long sessions with many servers. Reviewers could measure startup time, memory during a voice call, and battery drain on a laptop. Those results, not the codename or the framework choice, will decide whether the rewrite feels different in daily use.
Discord's own restart threshold gives a rough yardstick. A Discord employee described normal usage as under 1GB when the company tested automatic restarts in December 2025, so a client that stays near 290 MB while idle would leave more room for other apps.
Memory also matters more on cheaper hardware. On an 8GB laptop, a chat client that idles at 1–2GB takes a visible share of the machine before any game or browser opens. A client near 300 MB would change that arithmetic.
The wider significance is competitive. Windows Latest argues that Electron and WebView2 have made Outlook, Teams, WhatsApp, and Discord heavy, and that vendors have had little incentive to change. A major consumer app leaving Electron gives that argument a concrete example.
What to watch: a public beta, memory measurements from reviewers, macOS and Linux builds, and whether Discord publishes engineering details about GPUI patches and the Rust core. Until then, the rewrite is a credible plan with one screenshot of evidence.