Operating system
Windows 64-bit is the current supported desktop platform.
System requirements
Social Browser currently targets Windows 64-bit. Hardware demand scales with active Profiles, tabs, websites, extensions and automation concurrency, so the page separates confirmed support from practical sizing guidance.
Supported environment
These are product facts, not guessed hardware minimums.
Windows 64-bit is the current supported desktop platform.
The current product is Chromium/Electron based and exposes Chromium DevTools for developers.
Normal internet access is required for websites, updates and any external proxy or connected service you choose to use.
Performance sizing
A browser Profile consumes CPU, memory, GPU and disk like a real Chromium workspace. There is no single honest RAM number that fits one idle Profile and dozens of concurrent automated Profiles.
| Resource | What affects it | Recommendation |
|---|---|---|
| Memory | Number of active Profiles, tabs, websites and extensions | Size for your peak concurrent workload; do not size only for stored Profile count. |
| CPU | Active rendering, automation, video, page scripts | More concurrency needs more CPU headroom. |
| Storage | Profile caches, downloads, browser data, backups | Use an SSD and maintain free space for active Profile data. |
| GPU | Rendering, video and site graphics | Use current Windows graphics drivers; remote/VPS environments should expose a stable graphics stack. |
Development
Most users need only the browser. Developers may additionally use the built-in local integration surfaces.
External clients connect to the local debugging/API endpoint shown by Social Browser.
Learn more →Local Streamable HTTP and HTTPS endpoints are available for MCP-compatible clients.
Learn more →Chromium DevTools remain available for browser debugging and inspection.
Platform limits
Use this section to avoid planning a deployment around a platform Social Browser does not currently publish.