Connect with us

NEWS

Discord Bets Its Desktop App on Zed’s GPUI

Discord is betting its desktop app on Zed’s GPUI, not Tauri. A Phoenix build used 290.2 MB with two accounts and no ship date.

Published

on

Discord’s new desktop build used 290.2 MB of memory on Windows 11 while two accounts were signed in. Co-founder and chief technology officer Stanislav Vishnevskiy posted that Task Manager shot on November 4, under the process name Discord Phoenix, and said the company hopes to put the Rust client into user testing soon.

He gave no date. The current Electron app still ships, and the 290.2 MB figure is Discord’s own screenshot, not a public benchmark.

290.2 MB With Two Accounts Signed In

The number that traveled around the internet is easy to misread. Vishnevskiy later said the Phoenix process in the shot was running two accounts at the same time, a layout the new client supports, including two voice sessions. When someone called 290 MB “still vile” for a chat app, he joked that “those 4k avatar decorations gotta render somewhere,” then pointed back at the two-account setup.

The same window put Phoenix next to much fatter web-based tools. Chrome sat at 1,568.6 MB across 19 processes. World of Warcraft used 1,184.8 MB. Notion used 932.5 MB across nine processes, Steam 856.0 MB across seven, Spotify 652.7 MB, and Battle.net 344.0 MB. Phoenix appeared as one entry.

THE SAME TASK MANAGER WINDOW

App in the shot Memory How it showed up
Discord Phoenix 290.2 MB One process, two accounts
Google Chrome 1,568.6 MB 19 processes
World of Warcraft 1,184.8 MB Game client
Notion 932.5 MB 9 processes
Steam 856.0 MB 7 processes
Spotify 652.7 MB Listed beside Phoenix
Battle.net 344.0 MB Closest neighbor above Phoenix

That comparison is still a demo, not a match of 50 servers, live screen share, and Nitro animations. The Electron client Discord sells today regularly uses more than 500 MB on Windows. In December 2025, Discord staff said typical use stays under 1 GB and that the company was testing a restart when memory went past 4 GB. Phoenix has not been measured in public against those loads.

On November 5, Vishnevskiy posted a boot clip from two Lenovo ThinkPads running Windows 11. Discord’s own account posted the same pairing: current client on the left, Rust build on the right. Staff said both launches were cold starts. The new client had a friends list on screen while the Electron app was still on its loading screen. Vishnevskiy wrote that lower memory “is just part of the story,” that clicking around “feels instant,” and that he “can’t go back.”

The Interface Toolkit Came From a Code Editor

People who heard “Rust desktop app” guessed Tauri. Vishnevskiy shut that down in the same November 4 post. “It’s not Tauri, it’s GPUI, so good guess everyone.”

We’ve been early adopters of Rust since 2018 and a lot of our infra, voice tech, and even some of the current client is already Rust, the holy grail was getting the whole client there. That means Electron goes away, and so does React Native, mobile keeps native UI but shares app code with desktop via Rust. We hope to get it into testing with users soon™.

Stanislav Vishnevskiy, Discord co-founder and CTO, on X

GPUI is the GPU-drawn UI kit Zed Industries built for the Zed editor. Antonio Scandurra, writing on Zed’s blog in March 2023, said the team wanted to draw interfaces at 120 frames a second after Electron, on the Atom editor, kept missing frames to garbage collection and DOM layout. GPUI paints rectangles, type, shadows, and images with GPU shaders instead of shipping a browser engine.

Zed’s own crate notes that GPUI is still pre-1.0, with breaking changes between versions. It uses Metal on macOS, Win32 and DirectWrite on Windows, and Wayland or X11 on Linux. Discord is not taking that crate as-is. Vishnevskiy said the company runs its own patches and will “see what we can upstream if relevant to the community.”

That is the bet hiding under the RAM chart. Discord is tying a consumer chat client used by more than 90 million daily users (Discord internal data, Q4 2025) to a toolkit whose public docs still warn about breakage, then forking it. Zed’s account replied on November 5 with a short cheer.

Rust Has Been Inside Discord Since 2018

The language choice is the least surprising part. Vishnevskiy dated Discord’s Rust work to 2018, covering servers, voice, and pieces of the current client. The leap is putting the whole client there, which he called the holy grail.

HOW RUST LANDED AT DISCORD

  1. 2018: Discord starts using Rust in production, including voice and later the game SDK and Go Live video encode path.
  2. February 4, 2020: Engineer Jesse Howarth publishes the post on how Discord moved its Read States service off Go. Read States tracks which channels and messages each user has read, and it sits on every connect, send, and read.
  3. 2020, in that post: Howarth writes that Go’s collector was forced to run at least every 2 minutes and had to scan a huge in-memory cache, causing latency spikes. Rust freed cache entries as soon as they dropped out of the LRU, and the spikes went away.
  4. November 4, 2026: Vishnevskiy says Electron and React Native go away, names GPUI, and shows Phoenix at 290.2 MB with two accounts.
  5. November 5, 2026: Discord posts the side-by-side ThinkPad boot clip. Still no test calendar.

Howarth’s post is useful because it shows Discord will sit on unstable tooling if the gain is real. The team ran nightly Rust to get async, then waited for stable. Phoenix is that habit applied to the pixels users click, which is a harder product problem than a cache service.

Why Discord Skipped Tauri

Tauri would have been the conservative Rust move. It keeps app logic in Rust and draws the interface in HTML, CSS, and JavaScript through the operating system’s webview, which is WebView2 on Windows. You drop the bundled copy of Chromium that Electron ships. You do not drop the browser as the UI.

GPUI does. The desktop chrome becomes native GPU work. Discord still needs a webview for a few surfaces. Vishnevskiy told a bot developer the app “looks and works identically to the current one,” and that the process is native, with the system webview used for things like YouTube and Activities.

ELECTRON, TAURI, AND GPUI

Stack Where the UI is drawn Role at Discord
Electron Bundled Chromium Current desktop app, scheduled to leave
Tauri OS webview (WebView2 on Windows) The guess Vishnevskiy rejected
GPUI GPU, no DOM Phoenix desktop UI, with Discord patches

Asked whether performance would improve, he said, “We expect it to be better.” That is not a benchmark. It is the company talking its book, which is fair, and it is also all anyone outside Discord can quote until a build leaks.

Phones Keep Native Screens and Share the Core

The rebuild is not desktop-only. React Native leaves the mobile apps. iOS and Android keep native screens. Shared application code moves into Rust, the same pool desktop will use. That is how Discord plans to stop maintaining three product brains: Electron on the PC, React Native in the stores, and a growing Rust core behind voice and some desktop work.

WHAT LEAVES, WHAT STAYS

  • Electron: The Chromium shell of the Windows, Mac, and Linux apps is scheduled to go.
  • React Native: The shared mobile UI layer is scheduled to go; native widgets stay.
  • GPUI plus patches: Draws the new desktop interface.
  • System webview: Remains for embedded web, including YouTube and Activities.
  • Multi-account: Phoenix already runs two accounts at once, including voice on both, which is how the 290.2 MB shot was taken.

Discord has not said which desktop OS gets a test first. Every public clip is Windows 11. GPUI itself already targets macOS and Linux, so the kit is not the blocker. Staffing, QA, and overlay behavior in games are.

About 90% of Discord users play video games, per the company’s 2025 survey, and about 40% of PC players start a game within an hour of opening the app. Those people keep Discord running under a full-screen title. They are the reason a 4 GB restart test existed, and they are the reason a 290.2 MB two-account demo got treated as news.

What Users Get Before a Public Beta

Visually, Vishnevskiy is promising no redesign. Same servers, same badges, same Nitro cosmetics. The work is under the chrome: one process instead of a Chromium tree, GPU text and layout instead of a DOM, and a shared Rust core that mobile can call without React Native.

What nobody can check yet is the ugly hour. A 2,000-person server with live stage video, an overlay in a competitive shooter, and a dozen GIF-heavy channels will not look like that Task Manager window. Custom desktop clients already exist for people who wanted a smaller memory footprint and extra plugins. Those builds remain the only lighter Discord you can download this month. They also sit outside Discord’s update and safety model, which is why a first-party native client matters if it actually ships.

Security is the quiet half of dropping Electron. A bundled Chromium means Discord’s patch clock is tied to that engine. A native GPUI process removes that copy of the browser from the always-on chat app. The webview for YouTube and Activities still has to be kept current. The attack surface moves; it does not vanish.

Discord Has Not Posted a Test Date

Discord has not put Phoenix on the download page. It has not published a blog post, a feature matrix, or a platform order. The entire file is X posts from the CTO, one clip from the brand account, and a screenshot of 290.2 MB with two accounts open.

WHAT WE KNOW

  • The stack: Rust client, GPUI on desktop with Discord patches, native mobile UI, shared Rust app code, Electron and React Native on the way out.
  • The demo: 290.2 MB on Windows 11, two accounts, faster cold start on two ThinkPads in Discord’s own video.
  • The promise: Same look and behavior, system webview for YouTube and Activities, user testing hoped for soon.

WHAT IS UNCONFIRMED

  • A date: No beta window, no opt-in flag, no platform sequence.
  • Loaded RAM: No independent figure for a busy server list, voice, or overlay.
  • The GPUI tree: How far Discord’s patches sit from the public crate, and what will actually be sent upstream.

Vishnevskiy closed the November 4 post by saying he was going back to staring at the WoW Forever login screen. Phoenix is still on his machine. Everyone else is still on Electron.

Harry is the editor of IAQABA, an independent publication he owns and runs. A decade in journalism, beginning as a reporter and now as the editor of his own titles, has left him with a clear test for what deserves a story: it has to change what a reader knows or decides, and it has to rest on something he can point to. That rules out recycled press releases, forecasts with no data behind them and rumours that no document supports. It leaves room for a great deal, and the site covers news, business, science and technology alongside sports, entertainment and lifestyle, with travel, auto and gaming given the same standard rather than lighter treatment. Sources are primary wherever possible: the regulator's filing, the company's own statement, the transcript, the dataset, or the product on Harry's desk. Figures are checked before they are published and rechecked if a reader questions them. Mistakes are corrected under a published policy. Readers across the world can reach him directly at support@iaqaba.com.

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending