yapfast / yapfast
git clone https://github.com/yapfast/yapfast.git
v0.1.0 · 4d ago
The chat app that doesn't eat your PC. A lightweight, native Discord client in Rust.
—
stars, 24h
+90
stars, 7 days · #593
+90
stars, 30 days · #2,581
90
★ total · +90% this week
8
forks · 16 open issues
Star history starts 2026-10-20; the chart appears after the second daily snapshot.
LanguageRust
LicenseGPL-3.0
Created2026-10-16 (4d ago)
Last pushtoday
Watchers0
OwnerOrganization
GitHub topics
chatdesktop-appdiscorddiscord-clientlightweightlinuxlow-memorymatrixmatrix-clientnativeopen-sourcerustskiaslintvoicevoice-chatwebrtcwindows
Links
- GitHub: github.com/yapfast/yapfast
- Homepage: https://yapfast.com
- Releases · Issues · Hacker News mentions
README excerpt
Yapfast A Discord client without the web browser. About 40 MB of RAM, where Discord's own app takes 800. Download for Windows · yapfast.com · Discord server · Features · Build it yourself A test account on a fake Discord server. Nobody in there said any of this, or endorses Yapfast (sadly). ## Why? Discord's desktop app is a whole ass Chromium running Discord's website, and it sits at about 800 MB of RAM doing nothing (insane, I know right?!?). That annoyed me enough to write my own in Rust. Yapfast does the same job (doing nothing) in about 40 MB. There's no browser engine anywhere in it or near it: it talks to Discord's API itself and draws its own window with Slint and Skia, like a game would. Your servers, DMs, friends, voice and GIFs are all there, and if you know Discord, you already know where everything is. It opens fast af, too. I timed both, from clicking the icon to reading my messages: Discord took 8 seconds on my PC, Yapfast took 0.22, because it shows the messages it saved last time and catches up while you read. Sitting in a call with the window open, it's about 60 MB, and noise suppression alone eats 20 of those; that's as small as I could get it :( There's a GPU renderer too, behind **Render with the GPU** in Settings, but it takes about 120 MB, and drawing on the processor already keeps a 180 Hz monitor fed, so the processor is the default. Your numbers will depend on how many servers and DMs you have. How I measure. It's a 0.1 beta, and it's what I use for Discord every day, so it had better be usable. Still, there are rough edges; when you hit one, open an issue and I'll fix it, or come hang out on the Yapfast Discord server and tell me there. The connection drops every now and then (no more often than Vesktop's or the official app's does for me), and the noise suppression could be better. Know an open source one that does a better job? PLEASE tell me. ## Will Discord ban me? > [!WARNING] > Probably not, but I can't promise it. Third-party clients, Yapfast included, > are against Discord's Terms of Service. In practice Discord rarely bans anyone > for using one; the accounts that get banned are almost always spamming or > running automation. Yapfast only does what you click, and keeps to the same > limits Discord's own app does. > > If losing your account would be a disaster, don't use any third-party client, > this one or another. And don't post screenshots of it in a server whose > moderators might ban you for it. Yapfast tells you all this again before it > shows the sign-in code. ## Where your messages go Straight from your PC to Discord, or to your Matrix server. I don't run a Yapfast server, so nothing in between could keep a copy (I'd have to pay for servers just to snoop on your DMs, and no thanks :D). - You link your account by scanning a QR code with Discord's phone app, so Yapfast never sees your password. - The login token stays in your system's credential store, and only ever goes to