Getting Started
First-run workflow from download to automation.
Learn more →Frequently asked questions
Social Browser FAQ
Short, factual answers with links to the detailed product and support documentation.
FAQ
Product and account basics
The most common questions new users ask before installing or upgrading.
What is Social Browser?
A Windows multi-profile browser and browser-automation platform that combines persistent Profiles, per-Profile proxies, Automation Studio, MCP AI, User Scripts and compatible extensions.
Is signup required to start?
No. The free starting experience supports up to 10 Profiles without signup.
Where is Profile data stored?
Profile data is local on the device by default. Persistent Profiles keep their own cookies and local storage.
Can each Profile use a different proxy?
Yes. Proxy Manager supports saved proxies and per-Profile assignment.
Does Social Browser include automation?
Yes. Automation Studio is built in. User Scripts and Browser API/Puppeteer integrations provide developer paths as well.
What is MCP AI?
A local MCP-compatible connection that lets permitted AI clients discover and use browser/Profile, automation, research, screenshot, proxy and related capabilities.
Does Social Browser guarantee anti-detection or prevent bans?
No. The product does not guarantee bypassing platform security, anti-abuse systems, policy enforcement or bans.
Which operating systems are supported?
The current desktop product is Windows 64-bit. macOS, Linux and mobile versions are not currently published.
Can I use Chrome extensions?
Social Browser supports compatible Chrome-style extensions, with MV2 support and MV3 Beta support in the current product direction.
What is the difference between a Workflow, Automation and Task?
A Workflow defines steps, an Automation defines targets and execution policy, and a Task binds them for manual or scheduled execution.
Can I automate the same Profile I use manually?
Yes. Manual work and automation can use the same persistent authenticated Profile context.
How do I connect external code?
Use Browser API/CDP for external tooling, or run trusted Puppeteer code against the current tab from User Scripts. See /browser-api.
How do pricing plans differ?
The core browser is consistent; plans primarily change quantity and usage limits such as Profiles, installations, saved proxies, User Scripts and Automation Studio runs.
Where do I report a problem?
Use /support to search the knowledge base, check known issues, run diagnostics or create a support ticket.
Where can I see what changed?
Use /releases for release operations and /changelog for public change history.
Next step
Need a deeper answer?
The FAQ intentionally stays concise. The documentation hubs below are the source for implementation details.
Browser API
Developer reference for CDP, User Scripts and Puppeteer.
Learn more →Support Center
Troubleshooting, tickets, status and diagnostics.
Learn more →