| 1 |
--- |
| 2 |
title: Tor support |
| 3 |
nav_title: Tor support |
| 4 |
category: faq |
| 5 |
--- |
| 6 |
|
| 7 |
Feather works with Tor out of the box. You don't have to manually install Tor to use it. |
| 8 |
|
| 9 |
Feather releases are bundled with a Tor binary. If the presence of a local Tor daemon on the default port (9050) is not detected, Feather will place the bundled Tor binary in the [config folder](paths) and run it on port 19450. |
| 10 |
|
| 11 |
If you are unable to connect to the Tor network on your machine, you may configure Feather to use a different proxy (or no proxy at all). |
| 12 |
|
| 13 |
Feather can be configured to handle traffic to nodes in three different ways: |
| 14 |
|
| 15 |
- Never over Tor |
| 16 |
- Switch to Tor after initial synchronization (**default**) |
| 17 |
- Always over Tor |
| 18 |
|
| 19 |
You have the option to select the desired mode when Feather is started for the first time **before** any network connections are made. You can also change the mode in the **Settings → Network → Proxy** tab. |
| 20 |
|
| 21 |
By default, Feather routes all network traffic over Tor, except for wallet synchronization. Synchronization requires a lot of data transfer and is therefore very slow over Tor. A remote node does not learn much about your wallet during synchronization (for more information see [Nodes](nodes)). We believe this is a reasonable privacy / convenience trade-off. |
| 22 |
|
| 23 |
On Tails, Whonix, or when Feather is started with `torsocks`, all traffic is routed through Tor regardless of application configuration. Traffic to a [local node](local-node) is never routed over Tor. |