Download Social Browser
Install the current Windows 64-bit build from the official download route.
Open guide →Getting started
Go from download to a working Profile without guessing.
Start with one persistent Profile, prove the workflow manually, then add automation, proxies, AI or multi-Profile scale only when you need them.
Quick start
Your first 15 minutes
Follow this order to avoid configuring advanced features before the basic browser workflow works.
Open your first Profile
Use a Profile as the persistent workspace that keeps its own cookies and site storage.
Open guide →Add a proxy only if your workflow needs one
Use Proxy Manager and assign the proxy to the intended Profile rather than changing network state globally.
Open guide →Open websites and sign in normally
Manual work and automation can use the same persistent authenticated Profile context.
Choose an automation path
Use Automation Studio for no-code workflows, User Scripts for JavaScript inside the browser, Browser API for external code, or MCP AI for compatible AI clients.
Open guide →Verify before scaling
Test one visible Profile first. Add concurrency, schedules or multiple Profiles only after the workflow is reliable.
Open guide →Pick a workflow
Choose your next path
After the first Profile works, go directly to the documentation that matches your goal.
I manage multiple accounts
Profiles + Proxy Manager + backup/migration guidance.
Learn more →I want browser automation
Automation Studio for reusable workflows and scheduling.
Learn more →I am a developer
Browser API, User Scripts and Puppeteer integration.
Learn more →I want AI browser control
Connect an MCP-compatible client to the local MCP endpoint.
Learn more →I need help
Search Support Center, known issues and diagnostics.
Learn more →I am evaluating the product
Review pricing, system requirements and comparisons.
Learn more →Reliability
Before you automate at scale
Persistent browser state is powerful. Keep target selection unambiguous, verify important side effects, and rediscover runtime IDs after restart/reconnect.
Recommended sequence: one Profile → one manual run → one automated run → verification → multiple Profiles → scheduling.