System requirements
OverRider requires Windows 10 or later (64-bit), 4 GB of RAM minimum with 8 GB recommended, 1 GB of free disk space, and an internet connection. It does not run on macOS or Linux. RAM is the main limit on how many simultaneous visits you can run.
Minimum and recommended
| Component | Minimum | Recommended |
|---|---|---|
| Operating system | Windows 10 (64-bit) | Windows 11 (64-bit) |
| RAM | 4 GB | 8 GB or more |
| CPU | Dual-core | Quad-core or better |
| Free disk space | 1 GB | 2 GB |
| Internet | Required | Stable broadband |
| Screen resolution | 1366 × 768 | 1920 × 1080 |
Why 1 GB of disk space
The application itself is small. Most of the space goes to the browser engine, which downloads on first launch:
- Engine-1 downloads Google Chrome through Puppeteer.
- Engine-2 downloads Chromium through Playwright.
If you install both engines, allow closer to 2 GB. The device profile database and your project files add only a few megabytes.
How RAM limits your visit count
Every simultaneous visit is a separate browser process. This is the single biggest factor in how many threads your machine can handle.
| Your RAM | Comfortable simultaneous visits |
|---|---|
| 4 GB | 2 to 4 |
| 8 GB | 5 to 8 |
| 16 GB | 9 to 16 |
| 32 GB | 17 to 32 |
The Simultaneous Visits (Threads) slider spans 1 to 50, but values above 10 sit behind a lock button that you must unlock deliberately. Ten is the safe ceiling for typical hardware. Pushing past it on an underpowered machine causes page load timeouts, which appear as failed visits rather than as an obvious memory error.
Threads are shared across all running projects. The slider is a global setting, not a per-project one. If you set 10 threads and run two projects at once, each project gets roughly 5.
Not supported
- macOS and Linux — OverRider uses Windows-specific APIs and ships as a Windows executable. There is no native build for other platforms.
- Windows 7, 8 and 8.1 — the bundled browser engines no longer support these versions.
- 32-bit Windows — 64-bit only.
- Windows Server — not officially tested. It may work, but headless browser performance on server editions varies.
Antivirus and firewall
OverRider launches browser processes and opens many network connections, which some security suites treat as suspicious. If visits fail immediately after installation, add the OverRider installation folder to your antivirus exclusion list. This is a false positive caused by the browser automation pattern.
Virtual machines and Remote Desktop
OverRider runs in a virtual machine, but give it dedicated RAM and CPU cores. Running it over Remote Desktop is fine — because browsers run without a visible window, nothing is being streamed to your screen, so RDP bandwidth is not a bottleneck.
Last updated: