Rambox
Also called rambox workspace, rambox app
A workspace app that wraps WhatsApp, Slack, and mail in one Electron window. The process is Rambox.exe.
What you need to know
Rambox is a commercial workspace shell. It is not Ferdium.
Rambox.exe wraps WhatsApp, Slack, and mail. Ferdium.exe is the community Franz/Ferdi fork. Native messenger exes are separate.
- What is it?
- Workspace messenger
- Still current?
- Yes, see Current status
- Official download?
- Use the vendor link in this article
What is Rambox?
Rambox is a commercial Electron workspace that embeds web messengers and mail. The Windows executable is Rambox.exe.
If you have never used it
If you want WhatsApp, Slack, and mail in one paid-or-free workspace, this is Rambox, not Ferdium. Download it from rambox.app. The process is Rambox.exe. Ferdium is the community Franz/Ferdi fork. Native WhatsApp.exe is still optional on the side.
What is it used for?
Those sites run inside Rambox. They are not the native WhatsApp or Slack exes unless you also installed those.
Paid plans add organization features. Ferdium is a different project with different recipes.
The shell stays resident. Closing Ferdium.exe does nothing to Rambox.
Who is it for?
- People who picked the Rambox product, not the Ferdium fork
- Users who want vendor support instead of GitHub-only recipes
- Anyone running both shells by mistake
Current status
Rambox (2016) is a current workspace messenger from Rambox. The vendor still points Windows users at https://rambox.app/.
How old is it?
Rambox launched in 2016 as a multi-service workspace. It is older than Ferdium (2022) and in the same era as Franz. Current Rambox is the company product, not the community fork.
Versions
Major channels first. Exact build numbers are not all verified here.
System requirements
Values follow the publisher's public guidance. Workload still changes the real need.
Minimum
| Operating system | A current supported Windows 10 or Windows 11 release, per the vendor |
|---|---|
| RAM | Enough for Windows plus this app. Heavy projects want more. |
Resource profile
- CPU demand
- Follows what you open inside the app
- RAM demand
- Follows documents, tabs, or libraries
Installed processes
These executables belong to this product when it is installed.
| Rambox.exe | Main Windows executable |
|---|
Startup components
Rambox can start with Windows from its own setting.
File locations
| Typical install | C:\Users\<you>\AppData\Local\rambox\ |
|---|
File formats
Common problems
Session expired inside one tile
Re-login that service in Rambox. A Windows credential wipe is the wrong first step.
Two workspace shells at once
Rambox plus Ferdium doubles RAM. Pick one shell.
Getting unstuck
Install from rambox.app
A Rambox portable from a forum is junk. Freshdesk is the vendor help.
Use rambox.freshdesk.com, not Ferdium GitHub
They are different products. Recipes do not copy 1:1.
Quit Rambox.exe from the tray
Wrapped sites can keep the Electron host awake.
Alternatives
Ferdium if you want the community fork. Wavebox if you want a Chromium workspace browser. Native Slack or WhatsApp if you only need one chat.
Official help and downloads
Start with the vendor. Random exe sites are not a support channel.
| Download | rambox.app/ Official installer or vendor page |
|---|---|
| Help | rambox.freshdesk.com/ Vendor support |
| Official site | rambox.app/ Start here, not a random exe host |
Related hardware
RAM follows wrapped sites. This is an Electron shell.
Technical details
Technical details
Vendor version numbers change. This article does not pin a build.
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Rambox official site · Vendor product page
- Rambox help · Vendor support
- Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.