Tor & .onion
Stealth Browse routes .onion traffic through the Tor network using either an embedded Tor client or the Orbot companion app. Onion-name resolution and SOCKS5 proxying are scoped to the WebView so regular browsing stays on your normal connection (or VPN).
Modes
Embedded Tor
Stealth Browse runs its own Tor client (SOCKS5 on port 9150, control on 9151). No companion app needed. Bootstrap may take up to 90 seconds on first start.
Orbot
Use the official Orbot app as the Tor backend (SOCKS5 9050, HTTP 8118). The browser auto-detects when Orbot is in VPN mode and skips its own proxy override since traffic is already routed.
Settings
| Onion resolution | Enable .onion site loading (default On) |
| JavaScript on .onion sites | Default Off for security |
| Block external resources on .onion pages | Default On - non-onion subresources are blocked to prevent deanonymization |
| Require VPN before Tor | Default On - any system VPN counts (Stealth, Orbot VPN, third-party) |
| Tor mode | Embedded or Orbot |
Using Tor
- Go to Settings → Tor & Dark Web and choose Embedded or Orbot.
- If Orbot is selected and not installed, the settings page shows an install link.
- Open the browser menu and tap Tor to start/stop, request a new circuit, or open the settings panel.
- Navigate to any
.onionaddress - the request is sent through SOCKS5 with WebView'sPROXY_OVERRIDE.
New Circuit / New Identity
From the menu Tor popup you can request a fresh Tor circuit (new exit relay) at any time. With Orbot, the browser asks Orbot to rotate identity. With embedded Tor, the control port issues a NEWNYM signal.
Privacy Notes
- JavaScript is disabled on .onion sites by default. Many onion sites use no JS at all - leave this off whenever possible.
- External (non-.onion) resources are blocked while you are on a .onion page so trackers cannot pierce the proxy.
- Tor traffic is stripped of the WebView's normal proxy override the moment you navigate back to a clearnet page.