Why Slack is heavy on Linux specifically
The official Slack app uses the same Electron architecture on every platform — it bundles the full Chromium browser engine regardless of OS. The architecture is covered in detail here, but the short version: opening Slack is opening a second Chrome. That baseline cost exists on Windows and macOS too, but Linux users feel it more acutely for a few reasons.
Many Linux users run on older or more constrained hardware. Developers on Linux are also more likely to run htop — which means the memory use is actually observed rather than silently accepted. And Linux lacks the aggressive memory compression that makes macOS users less likely to notice the overhead.
The full memory spectrum
Measured with a single workspace, logged in, idle for five minutes:
| Client | RAM at startup | RAM after 1 hour | Desktop UI | Full features |
|---|---|---|---|---|
| Official Slack | 400 MB – 1 GB | 1 – 2 GB+ | Yes | Yes |
| CrabChat (Tauri) | 200–300 MB | 300–400 MB | Yes | Yes |
| Browser tab (Chrome) | 180–220 MB | 200–280 MB | Partial | ~90% |
| Browser tab (Firefox) | 140–180 MB | 160–240 MB | Partial | ~90% |
| msga | ~60 MB | ~80 MB | Yes | Core features |
| slk (TUI) | <20 MB | <20 MB | Terminal only | ~25% |
The browser tab result surprises most people. Because Chrome or Firefox is already running, adding a Slack tab only adds the memory for that tab's renderer process — you're not starting a second browser. For secondary workspaces or for anyone already using a browser heavily, this is often the pragmatic choice before considering a dedicated client at all.
What you give up at each tier
Browser tab vs. desktop app
The gaps are mainly around OS integration. There's no system tray icon, desktop notifications are less reliable (they depend on browser notification permissions and can miss messages when the tab is backgrounded), and slack:// deep links from other apps won't work. For a primary workspace where you need to catch every message, these gaps matter. For a secondary workspace you check occasionally, they probably don't.
msga vs. official app
msga covers the core communication loop fully: messaging, channels, DMs, threads, search, file sharing, and emoji reactions. What it doesn't have yet is Huddles (Slack's always-on audio spaces) and some advanced app integrations. If your work depends on Huddles or specific bots with rich interactive UI, you'll still need the official client for those moments.
For teams that primarily use Slack for written communication, msga covers everything that matters day-to-day. The full comparison of Linux Slack clients covers the other alternatives if you want a broader view.
Terminal clients
slk and similar TUI clients are genuinely minimal — under 20 MB — but the feature gap is large. No images, no rich formatting, no file previews, no voice or video. This is the right choice for a narrow audience: developers or sysadmins who live entirely in the terminal and only need to read and send text messages. For anyone else, the tradeoffs are too steep.
The practical recommendation
If you're on Linux and memory matters to you, the decision tree is straightforward:
- If you need Huddles or advanced integrations → use the official app, and consider the memory-reduction tips to keep it manageable.
- If you primarily use Slack for messaging → msga at ~60–80 MB is the sweet spot: full desktop UI, a tenth of the memory.
- If you have a secondary workspace you rarely check → a browser tab is the most memory-efficient option with no setup required.
- If you live in the terminal → slk is worth a look, with eyes open about what you're giving up.