From a new project to a working environment
Explore the responsibilities and actions at each step.
Choose an engine and template
Create a Chrome / Chromium or Firefox profile on Windows or macOS. Apply a template for settings you use repeatedly.
Configure its identity and network
Bind a proxy and review the device, language, timezone and network configuration in the identity summary.
Make the profile easy to find
Name it for the project, add a folder and tags, and leave a short note about its purpose.
Open, work and return
Launch the profile for the task. Its browser data stays in its own environment, with Cookie import and archiving to support session continuity.
A profile list you can work from
Use folders for clients or projects and tags for categories that span folders. Search and filter the list, then update names, proxies, tags and notes in place. Quick create and templates shorten recurring setup; bulk actions handle common changes across selected profiles.
| Folder | Profile | Useful context |
|---|---|---|
| Studio | Operations | Internal tools and everyday work |
| Client A | Customer support | Client identity and handoff note |
| QA | Storefront checks | Test environment and task description |
Repeat the task with the right tool
Use window synchronization for repeated interactive browser operations. Local API lets a script create, open and manage profiles; MCP lets an external AI tool select an environment and interact with its pages. Templates keep recurring configuration reusable across these workflows.
Bring existing environments into Mango
Mango includes migration connections for AdsPower, BitBrowser and DICloak. Select source profiles, review the import settings, choose a destination folder and follow the results. Supported data includes proxies, compatible fingerprint settings and Cookies.
Mango creates its own fingerprint identity during import. Review field differences and confirm the session after opening the imported profile; some services may require signing in again.