System requirements
| Requirement | |
|---|---|
| Mac | Apple Silicon: M1 or newer |
| macOS | 13 Ventura or later |
| Intel Macs | Not supported |
| Browser engine | Chrome 152 (fingerprint-chromium, open source, BSD-3 license) |
| Engine download | Inside the app, in Settings → Kernels, checked against a SHA-256 checksum |
| Where data lives | A local database on your Mac, with secrets encrypted and the key protected by macOS Keychain |
Multime is built for Apple Silicon only, and Intel Macs aren't supported. A Windows 10 or 11 PC is the other supported option; see Multime for Windows.
Install Multime on your Mac
The Mac download is a zip file. Installing takes a few steps, and two of them involve a macOS prompt.
- Download the zip. Get the Mac version from the download page. It lands in your Downloads folder.
- Unzip it. Double-click the zip. Finder unpacks it and you get the Multime app next to it.
- Move it to Applications. Drag Multime into your Applications folder, so it runs from there and not from Downloads.
- Open it. Double-click Multime in Applications. If macOS says it can't verify the app, open System Settings → Privacy & Security, scroll down to the message about Multime and click Open Anyway. On macOS 13 and 14 you can also Control-click the app and choose Open.
- Allow the keychain prompt. The first time Multime opens, macOS may ask for your Mac login password so Multime can use its encryption key stored in your Keychain. Multime uses that key to encrypt passwords, 2FA keys, proxy passwords and cookies. Enter your Mac password and click Always Allow so it doesn't ask on every start. macOS may ask once more after an update.
- Download the engine. Open Settings → Kernels and download Chrome 152. Multime checks the download against its SHA-256 checksum before using it. Until an engine is installed, profiles can't open.
- Create your first profile. Add a proxy, leave time zone, language and location set to match the proxy IP, and open it.
What a Mac profile can show to websites
New profiles show macOS by default, matching your computer. You can change that per profile.
| Setting | Options |
|---|---|
| Operating system shown to websites | macOS, Windows or Linux, with a version |
| Browser brand | Chrome, Edge, Opera or Vivaldi |
| User agent | Automatic, matching the engine |
| Time zone, language, location | Match the proxy IP, or set by hand |
| WebRTC | Through the proxy, replace the IP, disabled or real |
| Masking | Canvas, WebGL images, audio and element sizes (ClientRects) |
| Graphics card info | Masked or real |
| CPU cores | From the seed, or a custom number |
| Other | Do Not Track, port-scan protection, hardware acceleration, WebGPU |
Each profile's seed drives its masked values. The profile looks the same every time it opens, and two profiles never share values.
Language on a Mac
On a Mac, the browser's own menus always follow your macOS language, whatever the profile's interface language setting says. To keep the profile consistent, Multime puts that language first in the list of languages the profile sends to websites, followed by the languages that match the proxy. If your Mac is set to English and the proxy is in Germany, the profile's language list starts with English and then German.
A Pixelscan check on Chrome 152
We tested a Multime profile on macOS with the Chrome 152 engine on October 22, 2026. Pixelscan reported the profile as "consistent", with "No masking detected" and "No automated behavior detected". That is one test on one date with one tool. Test sites change, and a good result on a test page says nothing about how any particular platform treats an account. You can run your own check with our browser fingerprint test.
Mac-specific details
- Keychain. Multime's encryption key is protected by macOS Keychain. Copying Multime's database to another Mac doesn't reveal the encrypted secrets.
- Camera and microphone. Media devices aren't masked, so a website that asks for camera or microphone access sees your Mac's real devices.
- Screen size. Profiles always report your real screen size.
- Canvas masking works on the Mac engine. The Windows engine has canvas masking switched off automatically; the Mac engine doesn't have that limit.
A typical Mac setup
A social media manager runs 25 client accounts from a MacBook Air. Each client is a group. Each profile has a proxy in the client's country, so time zone and language follow that country, and a saved login with its 2FA secret. When she needs help, she moves to the Team plan, turns on hosting on her Mac and creates an account for a VA who works on a Windows PC. The team profiles stay on her Mac, and their engine setting stays on "Auto" so they open on both systems.
What doesn't work on a Mac
- Intel Macs and macOS versions older than 13 Ventura.
- Android or iOS profiles, on any system.
- Masking for screen size, media devices, speech voices and custom font lists.
- Automatic sync of profiles between your own Macs. Each computer keeps its own profiles; see local-first for the trade-offs.