# Features: what Mosaic does

> Every feature of the Mosaic anti-detect browser: its own Chromium engine, real hardware fingerprints, proxy providers, cookie jars, bulk actions, a REST API and MCP.

Source: https://mosaicbrowser.com/features

## Everything Mosaic does, with the screenshot to show it.

A profile is a fingerprint, a proxy and a cookie jar that agree with each other. Every feature below exists to keep them agreeing, on your computer. Each has a page: what it is, how it works, and what it does not do.

Mosaic is an anti-detect browser with its own Chromium engine. It draws each profile from real hardware, matches it to its proxy exit, keeps its cookies and logins apart, and can be driven by a REST API or an AI assistant over MCP.

Mosaic is a desktop app

Email yourself the link and open it on your computer.

## Identity

An engine of its own and machines that exist.

### The fingerprint is changed inside the engine, not painted on top

Tesseract Chrome is stock Chromium source plus a patch series of our own. Fingerprint values move in C++, so every page, frame and worker reads the same machine.

![A profile fingerprint in Mosaic: GPU, screen, fonts, timezone and language matched to the exit](https://mosaicbrowser.com/shots/fingerprint-detail.png)

### Every profile is drawn from one real computer, not from separate lists

A fingerprint is picked as a whole device: its GPU as the driver names it, its CPU threads, its memory and the screens it really ships with. The parts agree because they came from one machine.

### Timezone, language and location come from where the proxy comes out

Mosaic measures the exit address a profile browses from and sets its timezone, languages and geolocation to match. A Berlin exit gets Berlin’s clock.

### Any desktop OS or an Android phone, from the computer you have

A Mac can make macOS, Windows, Linux and Android profiles, and so can a PC. Your own OS still matches best, so the editor says so before you claim another one.

### Real device fingerprints: a catalogue of machines and phones

Real device fingerprints in the browser: Mosaic builds each profile from one record of a real machine, out of 155 desktops and 3 captured Android phones.

## Proxies

Checked, matched and minted per profile.

### A profile does not open until its proxy has answered

Before every launch Mosaic checks that the proxy answers and tunnels. If it does not, the launch stops and tells you which part failed.

![A proxy check result in Mosaic: latency, exit address, ISP, HTTPS tunnelling and reputation](https://mosaicbrowser.com/shots/proxy-check.png)

### Paste one gateway line. Every profile mints its own exit.

A proxy seller gives you one gateway line with a session id in it. Mosaic keeps that line as a template and mints a new session for every profile, so forty profiles get forty exits from one paste.

### Paste a whole proxy list and deal it out across your profiles

Paste a list in any common format, or a CSV with a header row. Mosaic reads every line, says why any line was refused, and assigns the result to as many profiles as you select.

### A dead proxy session costs a new session, not three retries

A residential pool sometimes hands out a session that reaches nothing, and it stays dead for every attempt on that token. Mosaic mints a different session instead of retrying the same one, and writes the working one back.

### Check an exit address against blocklists before an account sees it

A proxy that connects is not always one worth using. Mosaic checks the exit against public blocklists and reads whether it sits on a home network or a datacentre.

### Watch a profile’s traffic in your own debugging proxy, exit intact

Route launches through Proxyman, Charles, mitmproxy, Fiddler or Burp. The inspector sits in front and forwards back to Mosaic, so the profile still leaves from its own exit.

## Sessions

Cookies, logins and 2FA that stay put.

### Bring a logged-in session in, take it out, keep it sealed

Every profile has its own cookie jar, encrypted on disk. Import cookies in the format you already have, and they apply to a running browser without a restart.

![Importing a cookie jar into a Mosaic profile](https://mosaicbrowser.com/shots/cookies.png)

### Each profile keeps its own passwords and its own 2FA codes

A credential vault per profile holds logins and TOTP setup keys. Codes are typed into pages with real keystrokes, so a login form sees typing, not a pasted value.

### Notes, logins and 2FA codes, inside the browser that uses them

The companion is a small extension in every profile’s browser. It shows that profile’s notes, logins and current codes, and nothing belonging to any other profile.

### Each profile saves its files into its own folder

Files a profile downloads go into that profile’s own folder inside Mosaic’s data, not into one shared Downloads pile. The folder is kept out of Spotlight and deleted with the profile.

## Working at scale

Batches, presets, warm-up and the manager.

### Make 500 profiles in one go, then work on all of them at once

Create up to 500 profiles in a batch with names you choose. Then start, stop, edit, tag and move them together, arrange their windows and type into all of them with human timing.

![Six Mosaic profiles selected, with the bulk bar above the table: Start, Stop, Assign proxy, Edit, More and Move to trash](https://mosaicbrowser.com/shots/bulk-actions.png)

### A profile list built for the keyboard and for three hundred rows

Pin the profiles you open daily, jump anywhere with ⌘K, choose which columns show and page through 25 to 200 rows at a time.

### Write the recipe once, then make forty profiles from it

A preset holds a platform, tags, bookmarks, a note, extensions and where the proxy comes from. Each profile it makes mints its own session from your provider.

### Keep each client in a project, with tags that keep their colours

A project is a folder of profiles with its own colour and icon. Tags are coloured per project, and moving a profile carries its tags into the new project.

### Give a new profile a history before it meets the site that matters

The warm-up robot browses a profile in its own browser, through its own proxy, so it has cookies and history before you sign in anywhere. Mouse and scroll move like a person’s.

### Put a profile on the desktop and open it in one click

A shortcut opens Mosaic for that one profile, without the main window. When the browser closes, Mosaic quits a few seconds later.

### Bring your profiles over from the browser you use now

Mosaic recognises exports from GoLogin, Dolphin Anty, AdsPower, Octo Browser and Multilogin by their shape, and maps each profile across.

### Ask from inside the app, and read the answer there too

Write to support from Mosaic with screenshots attached, and follow the thread in the same window. A person reads each request and answers it.

## REST API

Everything the window does, from your own scripts.

### Everything the window does, from a script on your own computer

A local REST API on 127.0.0.1 covers what the interface covers. Starting a profile returns a CDP endpoint, so Puppeteer and Playwright attach to it.

![Driving a Mosaic profile from Playwright: start it over the local API and attach to its DevTools socket](https://mosaicbrowser.com/shots/api-automation.png)

## MCP server

An AI assistant that makes, starts and drives profiles.

### An AI assistant can make, start and drive your profiles

Mosaic’s MCP server gives Claude or any MCP client the same reach as the window: make profiles, start them, read and click pages, with clicks and keys that move like a person’s.

![The Mosaic MCP server: let an AI assistant manage profiles, proxies and launches](https://mosaicbrowser.com/shots/settings-mcp.png)

### Drive a page without switching on the signal that names a bot

Mosaic reads and drives pages for the REST API and MCP without enabling CDP’s Runtime domain, the switch Playwright flips. Clicks and keys go through the same human-input path as the warm-up robot.

## Safety

Leak tests, backups, app lock, local first.

### Configuration is not evidence. The leak test asks the page.

The leak test opens the profile for real and asks its own page what a site can see: the address it reaches, what WebRTC hands out, the clock, the language and the position. Then it compares each with what the profile should show.

![A pinned profile’s actions menu in Mosaic: edit, leak test, warm up, unpin, duplicate, save as preset, move](https://mosaicbrowser.com/shots/pinned-profiles.png)

### Test a profile the way a site would, before a site does

Run a leak test from inside the profile’s own page, then send it to a catalogue of 49 public detectors and read each verdict next to the others.

### Lock it with a password, and get yesterday’s library back

App lock keeps the library sealed until you type your password. Daily snapshots and a trash that keeps profiles for 30 days cover the mistakes.

### Your profiles, cookies and proxies stay on your computer

Mosaic has no cloud copy of your profiles. Our server knows your plan, your computers and when a profile opens, by a random id. Never what is in it.

### App lock: one password lock for all your browser profiles

App lock wraps the key to Mosaic's store and cookie jars in a password. Until it is typed, nothing decrypts, on this computer or on a copy of its disk.

## Every account its own browser. One price for all of them.

Free holds 3 profiles and 10 profile creations, with no card. Pro is $49 a month for any number, or $490 a year with 2 months free. Try it for 14 days; cancel before day 14 and you pay nothing.

Mosaic is a desktop app

Email yourself the link and open it on your computer.
