Synchronizer — one action, many accounts at once

It turns one master browser window into N replicas. You click, type, scroll or navigate in the master, and Afina injects the same DOM events into every synced child window in real time. Each child stays a fully isolated browser — same input, different identity.

Practically as many as your machine can comfortably run in parallel. 5–10 is effortless on a typical M2 / 16GB; 15–20 starts to push memory; 30+ is fine on workstations. RAM is the bottleneck, not the synchronizer itself.

Synced: clicks, mouse moves, key presses, scrolls, navigation, form input. Not synced: cookies, sessions, fingerprints, local storage, IndexedDB, downloads, network responses. Every account remains its own entity — you're only sharing your inputs.

Yes — toggle sync on/off per window from the toolbar. Open a window unsynced, do something account-specific (different password, unique 2FA), then re-enable sync to continue the batch action.

Not directly — synchronizer is real-time, not record-and-replay. For repeatable workflows use the RPA canvas: build the flow once and run it on the same set of profiles via task groups. Synchronizer is the fast-and-manual sibling of RPA.

Synchronizer is a UI feature — it runs on top of the desktop windows you open from the table or via 'Open synchronized'. Profiles started via API remain available to Puppeteer/Playwright through the CDP endpoint, but they're not part of the synchronizer's tiled view unless you bring them in manually.