Chrome or Firefox, and which browser version
Pick a profile's browser engine and its Chrome version, and see what the Firefox engine can and can't do.
On this page
Every profile runs on a browser LoginDeck builds and ships itself, never on the Chrome or Firefox you already have installed. You choose two things: the engine (Chromium or Firefox) and, for Chromium, the Browser version.
The version matters because it's the first thing a site reads about you. A profile that has been reporting Chrome 152 for months and suddenly reports Chrome 155 looks like a machine that updated, which is normal — but changing it back and forth is not.
🧭 Choose the engine#
- Open the profile's editor (row ⋯ → Edit).
- On the Overview tab, under Browser engine, pick Chromium or Firefox.
- Click Save changes.
Chromium is the default and the complete one. Pick Firefox when you want a profile that isn't Chrome-shaped, and you don't need automation or cookie sync on it.
🔢 Choose the Chrome version#
- In the editor, on the Overview tab, open Browser version.
- Pick a version. Each line reads like "Chrome 154 · download 198 MB" or "Chrome 152 · default · installed".
- Click Save changes.
If the version isn't on your computer yet, the download starts as soon as you pick it: "Downloading Chrome 155 (198 MB) — the profile launches on it once it is installed." It's about 200 MB, fetched once, and shared by every profile that picks it.
- New profiles start on the newest version LoginDeck offers.
- Existing profiles keep the version they were saved with. They're never moved for you.
- On a Mac, only one version is offered today, so there's nothing to choose.
One version, one engine
The version you pick changes the real binary the profile runs, so the user agent, client hints and everything else follow it. This isn't a user-agent string being rewritten.
Download versions ahead of time#
In the left sidebar, click About. Under Chrome versions each version has a Download or Remove button, and the one this install shipped with is marked default engine. Removing a version frees the disk space; profiles that use it download it again next time they open.
If a profile that used to pass starts failing
Check whether its Chrome version changed before you change anything about the profile itself. The version number is what a detector reads first.
🦊 What the Firefox engine can't do#
Firefox profiles run on the bundled Firefox engine (Camoufox). They get their own fingerprint, language, time zone, screen and proxy, and they restore their tabs. These features are Chromium-only today:
| Not available on Firefox | What happens |
|---|---|
| Automation: the local API, MCP, Flows and Warm up | "automation (API/MCP) is not supported for Firefox profiles yet — run it from the app, or use a Chromium profile" |
| Cookie import and export | "cookie import/export is not available for Firefox profiles yet — it works on Chromium profiles" |
| Cookie and session sync between computers | Nothing is uploaded or restored |
| Extensions | Assignments are saved on the profile but nothing is loaded |
| Paste as human | The right-click item isn't added |
| Browser version picker, WebRTC setting, Launch arguments | Not used |
| The canvas, client rects, audio and WebGL image settings on Advanced | The engine makes its own consistent values |
There's no Firefox version to choose. The engine's version is shown on the About page.
Profile rows show a small orange Firefox mark (tooltip LoginDeck Firefox engine) so you can tell them apart at a glance. Chromium rows say LoginDeck Chromium engine.
❓ Common questions#
Can I switch a profile from Chromium to Firefox later?
Yes, in the editor. It's a different browser, though, so the profile's logged-in sessions and its extensions don't carry across. Treat it as a new browser on the same machine.
Does LoginDeck use the Chrome I already have installed?
No. It only runs its own builds, so what a site reads is the same on every computer you use.
My profile won't start and says a version is not offered by this build.
The version it was saved with isn't on the update feed any more. Open the editor, pick a version from Browser version, save, and run it again. See A profile won't start.
Which engine should I use for Android profiles?
Chromium. Pick Android under Operating system on a Chromium profile. See Android (mobile) profiles.
ℹ️ Good to know#
- The default engine for new profiles is set under Settings → Profile defaults. See Default settings for new profiles.
- Duplicating a profile keeps its version. See Duplicate a profile.
- LoginDeck's own updates and its browser engines update separately. See Updates to LoginDeck and its browser engines.