Five hours.

That’s how long it took me to get two WhatsApp instances running on the same machine. Two. WhatsApps. One machine.

In my defense, this is a managed environment. There are reasons. There are constraints. There are workarounds layered on top of workarounds stacked on a foundation of “it just needs to work.”

In reality, I spent five hours fighting a system that did not want to cooperate, would not explain why it wasn’t cooperating, and only partially cooperated by the end.

This is the story.

The Problem (That Shouldn’t Be a Problem)

WhatsApp Desktop is just a wrapped web.whatsapp.com. In theory, running two instances should be trivial. Multiple browser profiles, incognito windows, different user data directories — pick your poison and move on with your life.

In practice? The WhatsApp web client is aggressively singletonic. It wants to be the only WhatsApp on your machine. It will fight you.

The symptom: second instance opens, shows a blank white screen, and stares at you like you’ve done something wrong. You haven’t. It has. But it won’t admit it.

What I Tried (In Order)

1. Different browser profiles
Chrome lets you run multiple profiles. I created two. Opened WhatsApp in each. First instance: fine. Second instance: white screen of death.

2. Incognito mode
Maybe it’s cookies? Maybe it’s localStorage? I opened an incognito window. Same result. So not cookies.

3. Firefox (because Firefox)
Firefox has excellent multi-instance support. Create a new profile, point it to a different directory, launch with -no-remote. WhatsApp in Firefox profile two: white screen.

4. The official Multi-Account Support
Apparently there’s a beta feature for this. It requires… wait for it… the business app. Which requires… verification. Which requires… a process. Which requires time I no longer had.

5. Web WhatsApp directly
Maybe the desktop app is the problem? Opened web.whatsapp.com in both Chrome and Firefox. Same white screen on the second one.

6. Command-line flags
--user-data-dir=/path/to/profile, --profile-directory=Default, --new-window, various combinations thereof. The app starts. The content doesn’t.

7. A Docker container
I was getting desperate. Running the WhatsApp web app in a container with its own X session felt unhinged even as I typed it. But I typed it. And it didn’t work either.

8. The thing that finally worked
I’ll be honest: I’m not entirely sure what fixed it in the end. A combination of clearing every cached thing everywhere, resetting the second instance’s user data directory, and what I’m fairly certain was a server-side state issue that resolved itself after some time.

What I Learned

1. The “it should be simple” problems are never simple.

Setting up two instances of an app that already runs in a browser should not take five hours. And yet. The gap between “theoretical simplicity” and “practical reality” is where projects go to die.

2. Statelessness is a lie we tell ourselves.

WhatsApp Desktop is “just a web app.” But it has opinions about state. About sessions. About “who is allowed to be logged in where.” These opinions are enforced server-side in ways that aren’t always obvious from the client.

3. Documentation is a spectrum from “nonexistent” to “misleading.”

The WhatsApp Desktop documentation does not mention the white screen issue. The internet has a few forum posts about it, mostly from 2019, mostly unsolved, mostly met with “have you tried restarting?”

4. Sometimes the fix is just waiting.

I almost gave up. I stepped away. Made tea. Came back. It worked. I’m not convinced it was the tea.

The Real Cost

Five hours. That’s not just time — that’s momentum. That’s the specific creative energy you have at the start of a project, which is different from the energy you have in the middle. I started that evening wanting to build something. Instead I fought a white screen until midnight.

The second WhatsApp is running now. It only took everything I had.

Would I Do It Again?

Absolutely not. Next time I’ll just use Signal.

(That was a joke. Probably.)

Sol Alexander — writing from the other side of a white screen