Profiles

A profile is one isolated browser: its own data folder (cookies, local storage, history, extensions), its own proxy, its own fingerprint and its own settings. One profile usually stands for one account or one identity.

The engine: MZBrowser

Every profile runs MZBrowser, MZBase’s own Chromium-based engine. The app installs and updates it; you never point MZBase at another browser.

A profile chooses one of two modes, on the same engine build:

• Persona. MZBase composes a complete, consistent device from a seed stored with the profile: operating system, screen, hardware, fonts, graphics and more. The same profile shows the same device every time.
• Real machine. The engine shows this computer as it is, with nothing composed. Useful when a site should see your real hardware.

In both modes the network-facing values follow the profile’s settings: time zone, language, WebRTC IP and location come from the proxy’s exit IP when a proxy is set. In Real machine mode the engine currently keeps this computer’s time zone and language; the profile form says so.

Engine versions

Each profile is pinned to an engine major version, so its fingerprint does not change under you after an app update. The version picker offers the newest major and the one before it. A missing version is downloaded the first time the profile opens.

Opening a profile

When you press Open:

1. Proxy check. With a proxy (and the setting Check proxy on start, on by default) the proxy must answer an IP lookup within 6 seconds. The exit IP, country, time zone and location are saved on the proxy and used for the fingerprint. Profiles that share a proxy and start together share one check; a recent check is reused.
2. Router. If the profile is in a proxy pool, the proxy router picks or keeps its proxy first.
3. Lock. In a team, the app asks the team server for the profile’s lock. A profile opens on one device at a time; if another device holds it you see Opened on another device.
4. Sync. If the team’s copy is newer, the app downloads and decrypts it first.
5. Start. The browser starts as a child process of the app. When the app exits, its browsers close with it.

With Direct (no proxy), the fingerprint takes time zone, location and WebRTC IP from this computer’s network.

Closing

Closing the browser window or pressing Stop ends the session. In a team, the app uploads the changed profile bundle (compressed and encrypted) to the team’s bucket and releases the lock.

Admin takeover

A team admin can ask the device that holds a profile to close and sync it, then open it themselves. If that device does not answer, the admin can open the latest synced version; the other device’s later changes are kept separately as a conflict version and never overwrite.

Organising profiles

• Folders, tags and pins to group and find profiles; the list filters by all of them.
• Notes per profile.
• Selection: click, Shift-click and Ctrl-click rows, or drag across them; right-click for the same menu as the row’s ⋮ button.

Many profiles at once

• Create many: make dozens or hundreds of profiles from one form, with names from a pattern and proxies from a list or a pool.
• Import and export: one row format for both, with a dry-run check before anything is written.
• Edit the selection: change the folder, tags, proxy or settings of every selected profile.

Cookies

Import cookies into a closed profile; they are written into the browser on its next start. Cookies and passwords are always stored encrypted.

Trash

Deleting a profile moves it, with its data, to Trash for 30 days (the default). Restore it from Trash, or purge it for good. In a team, restores and purges go through the team server.

Plan limits

The Free plan allows 10 profiles. When a trial or license ends, the first 10 profiles stay usable and the others are locked (not deleted) until a license is entered again.