Download the Dual Login app

What you are installing, and what it does to your machine

Two things arrive together: a desktop application that manages profiles, proxies and automation, and a browser engine it launches them with. The engine is a Chromium-derived build, which is why the download is larger than a typical desktop app -- you are getting a browser, not a wrapper around the one you already have. It does not replace or modify Chrome, does not touch your existing browser profiles, and does not set itself as your default browser.

Every profile you create becomes its own directory on disk holding that identity’s cookies, local storage, cache and history. That is what makes the isolation real, and it is also the practical thing to plan for: profiles grow as you use them, and a few hundred active profiles is a real amount of disk. An SSD makes a noticeable difference to launch time, because opening a profile means starting a browser process against that directory.

What it needs to run well

Memory is the constraint that matters, and it is worth being blunt about the number: each open profile is a real browser process, so around five concurrent profiles per 4 GB is a realistic working figure with low-memory mode on. An 8 GB machine runs a handful at a time comfortably; 16 GB is the point where the tool stops being the limit; 32 GB handles dozens at once and hundreds in sequence. Your plan’s profile ceiling and your machine’s concurrency ceiling are different numbers by an order of magnitude, and it is always the hardware that binds first. A GPU is not required, but leaving hardware acceleration enabled is preferable -- the graphics values a site reads are more convincing when a real graphics stack is producing them.

If your antivirus objects

It sometimes does, and the reason is structural rather than sinister: a freshly signed build has no reputation history, and an application whose job is launching browser processes with unusual configuration looks unusual by construction. If a scanner quarantines the installer, check the download came from this site, and report a false positive to your vendor rather than disabling protection wholesale. If a corporate policy blocks unsigned or low-reputation binaries entirely, that is a conversation with whoever owns the policy -- we would rather you had it than worked around it.

The first ten minutes

There is an order that saves a lot of time. Add a proxy first, before creating anything, and test it in the app rather than assuming it works -- proxies are the single most common cause of everything downstream looking broken. Create one profile and open the fingerprint checker inside it: you are looking for values that contradict each other, not for a high uniqueness score, and specifically for the WebRTC test showing your proxy exit rather than your own network. Sign in to something low-stakes and close the profile. Reopen it the next day. That last step is the real test -- session survival across restarts is what determines whether any tool in this category is usable, and it is the one thing no feature list can tell you.

Only after that is bulk creation worth doing, and it is a single CSV: name, group, proxy, start URL, country, notes and cookies per row. Proxies go into a shared pool once and get assigned rather than pasted profile by profile.

Updating, and why it is not optional

The engine is the part of this product that has to keep pace with how sites detect automation, and an out-of-date build is worse than merely stale in two distinct ways: it carries known browser security fixes it has not received, and its version string is itself a detection signal, because a browser reporting a version nobody still runs is immediately interesting. This is the rare piece of maintenance where deferring has a direct, measurable cost in the thing you are paying for.

Which build to choose

Take the one matching your machine rather than the newest-sounding one: Windows 10 or 11 on 64-bit, macOS on Apple Silicon or Intel as appropriate, or a modern 64-bit Linux. They are the same product with the same engine, not a full version and a set of ports, and choosing the wrong architecture is the most common failed install, so check yours before downloading rather than after. If the install completes and the app opens to a blank window, that is almost always a graphics-driver quirk rather than a broken install -- update the GPU driver before reinstalling anything.

Where your data sits on disk

Worth knowing before you have three hundred profiles: each one is a directory holding that identity’s cookies, storage and cache, and those directories are what you would back up. They live under the application’s data folder, they grow with use, and they are ordinary files rather than an opaque database -- which is deliberate, because data you can copy is data you can rescue when a machine fails.

Using it on more than one computer

Install on both and sign in with the same account. Profiles you have chosen to sync arrive on the second machine with their sessions intact, so a laptop picks up where the desktop left off rather than at a login screen. The rule that keeps this safe is worth knowing: a profile checks for a newer copy before it opens, so it will refuse rather than let you browse on a session the other machine has already replaced. That refusal is the feature -- working on a stale session and then saving it over the good one is how logins get destroyed silently in tools that treat every write as authoritative.

Running it on a server

Unattended automation on a VPS is a common arrangement and nothing prevents it, but two things catch people out. Memory, as above -- a small instance runs out of room faster than the profile count suggests, because every open profile is a browser. And graphics: a host with no GPU falls back to software rendering, which produces a renderer string that identifies the session as a virtual machine to anything reading WebGL. Where the host can expose hardware acceleration, turning it on is worth the effort, because it fixes a fingerprint value no other setting can compensate for.

Uninstalling

It depends which route you take, and the difference matters. The desktop uninstaller removes the application and leaves your profile directories alone, so a reinstall finds everything where it was. The one-line CLI uninstaller does the opposite by default: it removes the app and the local profile data together, and you opt out of that with --keep-profiles. Profiles you have synced come back when you sign in again, so the default is survivable -- but anything created while signed out, or never synced, existed only in that folder, and that is the one avoidable loss in this whole process. Export what you might want later before you uninstall, either way.