Skip to content
Guides 3 Connection Type: 2 views

Setting up proxy in Tor Browser

How to configure an additional proxy in Tor Browser: proxy before Tor, bypassing Tor blocking, bridges, and pluggable transports.

Configuring a Proxy in Tor Browser

Why Use a Proxy in Tor Browser

Tor Browser is already a powerful anonymity tool, but sometimes an additional proxy is needed before Tor:

  1. ISP blocks Tor — the provider blocks direct connections to the Tor network
  2. Corporate firewall — access to Tor is blocked at work
  3. Hiding the fact of Tor usage — ISP sees a connection to Tor, a proxy hides this
  4. Additional layer of protection — a proxy between you and the Guard node

Architecture: Proxy Before Tor

Without a proxy: You → Guard node → Middle → Exit → Website
With a proxy: You → Proxy → Guard node → Middle → Exit → Website

The proxy only sees that you are connecting to Tor (Guard node). It does not see which websites you visit.

Your ISP sees a connection to the proxy, but not to Tor.

Configuring a Proxy

On First Launch

  1. Launch Tor Browser
  2. On the connection screen, click "Configure Connection"
  3. Find the "Advanced" section → "Use a local proxy"
  4. Select the proxy type: HTTP/HTTPS or SOCKS4/SOCKS5
  5. Enter the address and port
  6. If authentication is required, enter the username and password
  7. Click "Connect"

In an Already Configured Tor Browser

  1. Open Tor Browser
  2. Click the shield icon or open about:preferences#tor
  3. In the "Connection" section, find "Advanced"
  4. Enable "I use a proxy to connect to the Internet"
  5. Enter the proxy details
  6. Click "OK" and restart the connection

Via the torrc File

For advanced configuration, edit the torrc file:

HTTPSProxy ip:port — for HTTPS proxy
HTTPSProxyAuthenticator user:password — authentication

Socks5Proxy ip:port — for SOCKS5 proxy
Socks5ProxyUsername user — username
Socks5ProxyPassword password — password

torrc location:
- Windows: Desktop/Tor Browser/Browser/TorBrowser/Data/Tor/torrc
- macOS: ~/Library/Application Support/TorBrowser-Data/Tor/torrc
- Linux: ~/.local/share/torbrowser/profile.default/torrc

Bridges

If Tor is directly blocked, instead of a regular proxy, you can use bridges — hidden entry nodes:

Built-in Bridges

  1. Connection Settings → Bridges
  2. Select "Use a bridge"
  3. Select "Select a built-in bridge": obfs4, meek-azure, Snowflake
  4. Connect

Obtaining Additional Bridges

  • Website: bridges.torproject.org
  • Email: bridges@torproject.org (with an empty body, subject: get transport obfs4)

Bridge Types

obfs4 — masks Tor traffic, making it resemble random data. Most effective.

meek — masks traffic as a request to a CDN (Azure, Amazon). Works even under strict censorship.

Snowflake — uses WebRTC for masking. Volunteers provide their browsers as bridges.

Combination: Proxy + Bridge

You can use a proxy AND a bridge simultaneously:

  1. Configure the proxy in Connection Settings
  2. Enable a bridge (obfs4 or another)
  3. Traffic will flow: You → Proxy → Bridge → Tor → Website

This provides maximum obfuscation: your ISP sees regular HTTPS to the proxy, and the proxy sees encrypted obfs4 to the bridge.

Checking the Connection

Checking Tor Operation

  1. Open check.torproject.org
  2. It should display: "Congratulations. This browser is configured to use Tor"

Checking the Circuit

  1. Click the lock icon next to the URL
  2. "Tor Circuit for this Site" will show the chain of nodes
  3. You can click "New Circuit" to change the exit node

Common Problems

"Unable to connect"

  • Check proxy details (address, port, login)
  • Ensure the proxy is working (check in a regular browser)
  • Try a different proxy type (HTTP → SOCKS5)

Slow Connection

  • Bridges (especially meek) work slower than a direct connection
  • Try obfs4 instead of meek — it's usually faster
  • Use a low-latency proxy

Tor Blocks Proxy

  • Tor Browser only trusts certain proxy types
  • HTTP CONNECT and SOCKS4/5 are supported
  • Transparent proxy is not supported

Security

What the Proxy Sees

  • IP of the Tor Guard node (or bridge)
  • Encrypted traffic (cannot read)
  • Time and volume of traffic

What the ISP Sees

  • Connection to the proxy's IP
  • Does not see Tor traffic

Recommendations

  • Use a trusted proxy (not free public ones)
  • SOCKS5 is preferable to HTTP — no logging of HTTP headers
  • If the proxy is unreliable, it adds risk rather than reducing it
  • Bridge + proxy — maximum obfuscation

Conclusion

Configuring a proxy in Tor Browser is useful for bypassing Tor network blocking and hiding the fact of Tor usage from your ISP. For most users, bridges (obfs4 or Snowflake) are sufficient. A proxy is added when bridges are also blocked or an additional layer of obfuscation is needed.

Auto-update: 06.03.2026
All Categories

Advantages of our proxies

25,000+ proxies from 120+ countries