Every account gets its own browser, device and identity
Dual Login runs a custom Chromium engine that applies each profile's fingerprint in the browser core, seals its storage, routes it through its own proxy, and exposes the whole thing to your automation. Here is what that gives you in practice.
Fingerprint protection that holds up
Most antidetect tools work the same way: they load a script into every page and overwrite the browser APIs a detector might read. It works until the detector looks at how those APIs were replaced. An overridden function has a different source string, a different prototype chain, a different call stack. Scripts also arrive after the page starts executing, and they rarely reach Web Workers at all — which is exactly where a serious detector goes looking for the unpatched truth.
Dual Login takes the other route. We ship a custom Chromium engine, and each profile's fingerprint is applied inside the browser core before a single line of page JavaScript runs. There is nothing injected, nothing to enumerate, and no window between page load and protection. The values a site reads are simply the values the browser has. Because the change lives in the engine, it applies identically on the main thread and inside Web Workers, iframes and service workers.
Consistency matters as much as coverage. A fingerprint is only convincing when every signal agrees: a Windows user agent should not report macOS fonts, an Intel GPU string should not appear next to Apple client hints, and a Frankfurt proxy should not serve a browser sitting in a New York timezone. Every profile is generated from one coherent device description, so the signals cannot contradict each other. If you want the theory behind why that matters, read browser fingerprinting explained and how antidetect browsers work.
You do not have to take our word for it. Open a profile on our free fingerprint checker and compare what it reports against your own machine, or see the full walkthrough of how it works.
Signals under your control
Set them per profile, randomise them from a device pool, or let them follow the proxy. Each one is stable for the life of the profile.
- Canvas & 2D renderingPer-profile output at the rasteriser level, stable across reloads and sessions.
- WebGL vendor & rendererMatched GPU vendor, renderer string and supported extensions for the device you claim to be.
- Audio stackAudioContext measurements land on the profile's own values, not your machine's.
- Font enumerationA font list that fits the platform, so a Windows profile never leaks a macOS font set.
- Screen & window metricsResolution, available area, colour depth, device pixel ratio and the real window geometry.
- hardwareConcurrency & deviceMemoryCPU core count and reported memory sized to the device profile, not the host.
- User agent & client hintsUA string and the full Sec-CH-UA set derived from one source, so they can never disagree.
- Timezone & languagesIANA timezone, Intl output and Accept-Language derived from the proxy exit location.
- GeolocationCoordinates you set, or coordinates matched automatically to the proxy IP.
- Media devicesCamera and microphone entries reported consistently, with an optional virtual camera feed.
Complete profile isolation
A separate fingerprint is worthless if the browser still shares state. Dual Login gives every profile its own on-disk browser directory, launched as its own process. Cookies, localStorage, IndexedDB, service worker caches, the HTTP cache and the credential store belong to that profile and nothing else. Two profiles can hold two logged-in sessions on the same site indefinitely, and neither one can see the other's storage.
Sessions that survive restarts
Close the profile, close the app, reboot the machine — the session is still there when you come back. Storage is written to the profile directory rather than held in memory, so you are not re-authenticating and re-triggering security checks every morning.
Portable between machines
A profile is a bundle of fingerprint, proxy and storage, and it syncs to your workspace. Sign in on another computer, open the same profile, and the site sees the same device with the same session — the handoff no longer costs you a verification email.
Cookie import and export
Bring existing sessions in from another tool or another browser with cookie import, and take them out again whenever you like. Bulk login import loads credentials and cookies for many profiles at once, so a migration is a single operation.
Proxies, done properly
Every profile carries its own proxy. HTTP, HTTPS and SOCKS5 are all supported, with or without username and password authentication, and authenticated proxies work without the credential prompts that break unattended runs. Bring residential, mobile or datacentre proxies from any provider — we do not lock you to one.
The part that usually goes wrong is everything around the IP. A German exit node with an American timezone, English-first Accept-Language headers and a WebRTC candidate exposing your real address is a louder signal than no proxy at all. Dual Login derives the profile's timezone, locale and geolocation from the proxy exit automatically, and masks WebRTC to the proxy IP so the local address never leaves the browser.
Proxies live in a reusable pool rather than being retyped per profile. Add a proxy once, test it in place, and assign it to as many profiles as you need. Per-profile bandwidth accounting shows which profiles are actually consuming your traffic allowance, which matters when you are paying by the gigabyte.
Automatic environment matching
- IANA timezone derived from the proxy exit country and city
- Accept-Language and Intl locale aligned to the same region
- Geolocation coordinates matched to the exit, or pinned manually
- WebRTC masked to the proxy IP, never the local interface
Pool management and visibility
- Save a proxy once and reuse it across profiles and teams
- Test connectivity and see the detected exit location before assigning
- Bulk import proxy lists in host:port:user:pass or URL form
- Per-profile bandwidth counters so traffic spend is attributable
Automation without the tells
Automation is normally where a good fingerprint dies. The moment a standard driver attaches, the browser advertises it: navigator.webdriver flips to true, an automation banner appears, and the flags that enable remote control show up in places a page can read. Dual Login drives profiles over raw Chrome DevTools Protocol commands instead, so input events are dispatched the way real input is and navigator.webdriver stays false.
You can drive it from anything that speaks HTTP. Each running profile exposes plain REST endpoints — no SDK required, no language lock-in — and the same action set is available whether you call it from a shell script, a scheduler or your own service. If you already have work built on Selenium, Puppeteer or Playwright, those attach too; point them at the profile and keep your existing scripts.
The action catalog covers navigation and tab control, mouse and keyboard input, element clicks and typing, screenshots, network capture, and OCR-driven actions that click or read text by what is visible on screen rather than by CSS selector — useful when a site rewrites its markup weekly. Flow recording captures a session as you perform it and replays it later across many profiles at once. The full reference lives in the documentation.
Open a page in a running profile
Every action is one request. Same shape locally and over the remote API.
# navigate a profile
curl -X POST http://localhost:4482/api/profiles/PROFILE_ID/goto \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com"}'
# type into a field, then click
curl -X POST .../type -d '{"selector":"#email","text":"you@mail.com"}'
curl -X POST .../click -d '{"selector":"button[type=submit]"}'
# capture what happened
curl -X POST .../screenshot -o shot.png
curl -X POST .../network/start- goto / reload / back
- click / hover / scroll
- type / set-value / press
- screenshot
- OCR click and OCR read
- network capture
Built for teams
Once more than one person touches an account, the password becomes the weak point. Dual Login lets you share the profile instead of the credentials: a teammate opens the profile, the session is already authenticated, and they never see or need the password. When they leave, you revoke the profile rather than rotating logins across a dozen platforms.
Three roles, clear boundaries
Admins manage billing, members and workspace-wide settings. Managers create profiles, assign proxies and delegate access for their part of the business. Members work in the profiles they have been given and nothing else.
An audit trail you can read
Launches, edits, deletions and API calls are recorded with a timestamp and the account responsible. When an account behaves unexpectedly, you can reconstruct who opened it, from where, and what ran against it.
Onboarding and offboarding
A new contractor gets a role, a set of profiles and a bookmark set, and is productive without a credentials handover. Removing them removes their access everywhere at once — no shared vault to clean up afterwards.
Agencies, e-commerce sellers, affiliate teams and QA groups all use these controls differently. See how each one sets things up on the solutions pages, or check seat pricing on the pricing page.
Scale and performance
Running one profile is easy. Running two hundred on a workstation is an engineering problem, and it is the one that decides whether a tool is usable past the pilot stage. Dual Login is built for the second case.
Create in bulk, launch in bulk
Import a CSV with names, groups, proxies, start URLs, countries and notes, and get a fully configured set of profiles with unique fingerprints in one pass. Select a group and launch, stop or delete the whole set with progress you can cancel mid-run.
Low-RAM mode by default
Memory caps and trimmed background work let far more profiles share a machine than a stock Chromium build allows. Hardware acceleration stays on, because the GPU is what makes the WebGL side of the fingerprint believable.
One process per profile
Isolation is enforced by the operating system, not by convention. A profile that hangs or crashes takes nothing else down with it, and you can stop it individually without interrupting the rest of the run.
Resource and traffic visibility
See CPU, memory and bandwidth per profile so you know what a batch actually costs before you scale it, and which profiles are burning proxy traffic you are paying for.
What most tools do vs what Dual Login does
The differences that matter are architectural, not cosmetic. For a head-to-head against named products, see the comparison pages.
| Area | What most tools do | What Dual Login does |
|---|---|---|
| Fingerprint method | JavaScript injected into every page, which a detector can read back or catch mid-override. | Applied natively inside the Chromium core before page scripts run — and it reaches Web Workers too. |
| Proxy handling | A proxy field that changes your IP and leaves timezone, locale and WebRTC pointing home. | Per-profile HTTP/HTTPS/SOCKS5 with timezone, locale and geolocation matched and WebRTC masked to the exit IP. |
| Automation | A driver that flips automation flags and leaves navigator.webdriver true. | Raw CDP or plain HTTP endpoints; navigator.webdriver stays false and no automation banner appears. |
| Teams | Shared credentials passed around in a spreadsheet or a chat thread. | Admin, manager and member roles; profiles shared without ever sharing the password. |
| Storage isolation | One browser directory with partial separation, so cache and storage bleed between accounts. | Cookies, localStorage, IndexedDB and cache sealed per profile and portable between machines. |
| Free tier | A short trial, then a card on file before you can test anything seriously. | 10 profiles free, no credit card, on Windows, macOS and Linux. |
Everything else in the box
Smaller features, but the ones that remove friction from daily work. Several of them are also available on their own in our free tools.
Virtual camera
Feed a prepared video clip into a profile as a real camera device for verification flows and calls.
Bookmarks sync
Push a shared bookmark set into every profile so a new hire opens the right dashboards on day one.
Extensions
Load your own Chrome extensions per profile — password managers, ad blockers, internal tooling.
Geolocation control
Pin exact coordinates per profile or let them follow the proxy exit automatically.
Notes & tags
Label profiles by client, marketplace or campaign, then filter and act on a whole group at once.
Activity log
A timestamped record of launches, edits and API calls, with the account behind each action.
Encrypted sync
Profiles and settings sync to your workspace so the same session opens on another machine.
Bulk cookie import
Import cookies and saved logins for many profiles in one pass, in JSON or Netscape format.
Fingerprint checker
Inspect what a live profile actually reports on our free checker before you trust it with an account.
Try it with ten profiles, free
Every feature on this page is in the free plan. What the tiers change is capacity -- profiles, seats, camera slots -- never capability, because a feature matrix where the important rows unlock at the expensive end is a pricing page pretending to be a product page. Test everything on ten profiles; pay for more profiles when ten is the thing that runs out. And test on the accounts and platforms you actually work with -- a feature list can tell you what exists, but only your own week of use can tell you what holds. The checker linked above runs in any profile, free plan included, so the verification costs you nothing but the evening.
It is the same engine and the same fingerprint layer with a smaller profile ceiling, not a reduced build -- because a trial that runs different software from the product cannot answer the only question worth asking, which is whether your sessions hold over a week of ordinary use.
No credit card, no trial clock. Create a profile, point it at a proxy, and check what it reports before you move a single real account across. Windows, macOS and Linux, with a web console at app.duallogin.com.
Questions first? Read how it works, the plans or the developer docs.