Skip to content

Orbot: Tor Routing for Privacy-Focused Android Users

Orbot: Tor Routing for Privacy-Focused Android Users

Orbot review: when system-wide Tor routing beats Tor Browser on Android, VPN-mode push limits, and why banking, DRM, or captcha apps need exclusions.

App summary

App
Orbot
Developer
The Guardian Project
License
BSD-3-Clause
Version
unknown
Size
unknown
Price
Free

Orbot gets recommended as a privacy app, which is true in a narrow sense and misleading in a broad one. The app routes internet traffic through the Tor anonymity network and acts as a proxy or VPN-style service for other Android apps. That is the whole job. Confusion starts when people expect a full VPN, a complete anonymity guarantee, or a drop-in replacement for Tor Browser, none of which Orbot claims to be.

This review treats Orbot as what its documentation supports: a selective, open-source Tor routing layer. The sections below focus on the decisions that determine whether it helps or hinders — which apps you route, how VPN mode interacts with Android’s background behavior, where Tor exits leave traffic exposed, and what the battery and data costs actually depend on.

Orbot vs Tor Browser for Android: When System-Wide Tor Routing Is Unnecessary

Orbot is built to route internet traffic through Tor and act as a proxy or VPN-style service for other Android apps. That is a different job from browsing. Tor Browser for Android is the official Tor Project alternative that uses Tor without system-wide app routing. If your only goal is to browse through Tor, Tor Browser already does that, and Orbot becomes an extra layer you do not need.

Where Orbot earns its place is app-level routing. It can route selected apps through Tor, which is something a browser cannot do. The free, open-source, no-account model is a practical advantage here — no sign-up, no subscription, no vendor account tied to your routing. For someone who needs a specific app’s traffic to leave through Tor, that combination is the reason to install Orbot rather than just a browser.

The anonymity caveat is not optional. Orbot does not guarantee anonymity if users log in or reveal identity, and the fact data is explicit that Tor exit nodes can observe unencrypted traffic. Nothing here protects a compromised device. So the comparison is not “Orbot versus Tor Browser, which is more anonymous” — both rely on the same network — but “which one matches the job.” If the job is browsing, Tor Browser. If the job is routing other apps, Orbot.

A common mistake is treating the two as interchangeable. They are not. Orbot is not the same thing as Tor Browser, and installing one does not give you the other’s behavior. The other common mistake is assuming Orbot is a full VPN that hides all phone traffic by default. It is not; per-app routing in VPN mode means the selection matters.

Orbot VPN Mode and Push Notifications: What Android Background Sync Can and Cannot Promise

Orbot’s VPN mode uses Android’s VPNService, and per-app routing means not every app necessarily goes through Tor. That detail matters for notifications because delivery depends on whether the relevant app is selected for routing. If an app is excluded, its background connection behaves as it would without Orbot. If it is included, its traffic takes the Tor path, with everything that implies.

The fact data does not document current push-notification or background-sync behavior. That is a real gap, not a footnote. Anyone who needs reliable notifications from a routed app should treat the outcome as unknown and test it on their own device rather than assume Tor routing preserves timely delivery. I will not promise that notifications survive Tor routing, because the source material does not support that promise.

What the fact data does say is that Tor routing can reduce connection speed and add battery and performance overhead. For always-on background apps and sync-heavy apps, those costs compound. A messaging app that syncs constantly through Tor is a different proposition from a browser you open occasionally. The overhead is not a bug; it is the cost of the route.

VPN mode may also conflict with other VPN apps. Stacking VPN services on Android is not a way to improve background reliability — it is a way to break connectivity. If notifications stop arriving after you enable Orbot, the first thing to check is whether another VPN service is active, not whether Tor is “blocking” notifications. The fact data does not document specific failure modes, so this is a process of elimination, not a diagnosis.

Orbot With Banking, DRM, and Captcha-Heavy Apps: When to Exclude an App From Tor

The single most important fact for this section is that Tor exit nodes can observe unencrypted traffic. Orbot routes traffic through the Tor network, but it is not end-to-end encryption beyond the exit. Anything that leaves an app unencrypted at the exit is visible there. That is a property of Tor, not a flaw unique to Orbot, and it should shape which apps you route.

Banking and account-based apps are identity-revealing scenarios by definition. Logging in or revealing identity defeats the anonymity benefit, and the fact data says so directly. That does not mean Orbot is useless for them — it means the anonymity framing does not apply. If you are going to authenticate, you are not anonymous, and routing through Tor mainly adds latency and the chance of a failed connection.

Per-app routing in VPN mode is the fact-backed way to exclude selected apps from Tor routing. That is the lever. You do not need root for VPN mode; it uses Android’s VPNService. The catch is that VPN mode may conflict with other VPN apps, so exclusion decisions have to be made with the rest of your VPN setup in mind.

The provided fact data does not document banking, DRM, or captcha compatibility. I am not going to pretend otherwise. Treat these as test-and-exclude scenarios: route the app, see whether it works, and exclude it if it does not. DRM playback and captcha flows are the usual suspects for friction behind Tor exits, but concrete compatibility for any specific app is unknown in the source material. The honest position is that you will find out by trying, and per-app routing is what makes trying reversible.

Orbot Battery and Mobile-Data Cost by App Category: Why Per-App Routing Changes the Bill

The fact data lists battery and performance overhead plus slower Tor routing as known costs. It does not list per-app benchmark numbers, and I will not invent them. The right way to read the cost is qualitative: every app you route pays some combination of slower connections and additional battery drain, and the total depends on how much that app uses the network.

Per-app routing in VPN mode is the main fact-backed lever for reducing unnecessary Tor exposure. If an app does not need to go through Tor, excluding it removes both the routing overhead and the risk of Tor-related breakage for that app. The bill, in battery and data terms, is shaped by the selection, not by Orbot’s presence alone.

Troubleshooting battery or connectivity problems has to include checking for competing VPN services, because VPN mode may conflict with other VPN apps. A phone running two VPN-style services is not a phone with better privacy; it is a phone with unpredictable connectivity and, often, worse battery behavior. The fact data does not document specific power figures, so any claim about exact drain would be fabricated.

Current version, APK size, and exact minimum Android version are unknown in the fact data, which rules out precise claims about data use or battery for the latest release. What can be said is that the costs exist, they scale with routed traffic, and per-app routing is how you keep them proportional. If you see a disconnected state on mobile data, the fact-backed suspects are VPN conflicts, restrictive networks that may need bridges, and per-app selection — not a documented Orbot bug.

The Open-Source, No-Account Model and What It Does Not Promise

Orbot is free and open-source software under the BSD-3-Clause license, developed by The Guardian Project. It requires no account. The source code is published on GitHub under the Guardian Project, and the app is available on Google Play and F-Droid under the package name org.torproject.android. Those are verifiable facts, and they matter for a privacy tool because they let people inspect and redistribute the code rather than trust a vendor’s description.

The no-account model is a practical advantage, not a privacy guarantee. It means there is no sign-up identity attached to your use of the app, but it does not mean your traffic is anonymous. The fact data is clear that Orbot does not guarantee anonymity if users log in or reveal identity, and that Tor exit nodes can observe unencrypted traffic. Open source and no account change who you have to trust; they do not change what the network can see.

What the model does not promise is equally important. It does not make Orbot a full VPN, it does not make it an anonymity guarantee, and it does not make it a malware shield. A permissively licensed routing tool is still a routing tool. The license tells you what you can do with the code; it tells you nothing about whether a given app will work through Tor.

Distribution matters too. Google Play and F-Droid are both listed as availability channels, and the official project page at guardianproject.info is the reference point for the app. The fact data does not include current version, APK size, or install counts, so any claim about “latest” or “most popular” would be unsupported.

Per-App Routing: The Design Decision That Defines Orbot

Per-app routing in VPN mode is the feature that makes Orbot useful rather than merely present. It lets you choose which apps go through Tor. That single design decision is why the app is best judged as a selective routing layer rather than a blanket VPN. The difference is not cosmetic: a blanket VPN would route everything, including apps that break behind Tor exits, while per-app routing lets you keep those apps working.

This is also where the “full VPN that hides all phone traffic by default” misconception falls apart. Orbot can act as a proxy or VPN-style service for other Android apps, but the selection is yours. If you route nothing, nothing goes through Tor. If you route everything, you inherit every compatibility problem at once. The middle ground — route what benefits, exclude what breaks — is the intended use.

VPN mode uses Android’s VPNService, which is why Orbot works without root in that mode. Root is not a requirement for VPN mode, contrary to a persistent misconception. The cost of not needing root is that you are working within Android’s VPN framework, which is also why VPN mode may conflict with other VPN apps.

The trade-off of per-app routing is that it requires judgment. You have to know which apps need Tor and which ones merely tolerate it. The fact data does not document per-app compatibility, so that judgment is empirical. The design gives you the control; it does not give you the answers.

Bridges and Restrictive Networks: Where Orbot Earns Its Keep

Bridge support for censorship circumvention is one of Orbot’s key features, and it is the reason the app matters in networks where Tor is blocked. The fact data lists “supports bridges for restrictive networks” as a strength, and bridge configuration is a verified capability. For users in those environments, bridges are not a power-user extra; they are the difference between the app working and not working.

The fact data does not document specific bridge types, current bridge behavior, or a setup procedure, so this section will not pretend to walk through one. What can be said is that bridge support exists as a feature and that restrictive networks are the scenario it addresses. Bridge configuration is a verified capability, and the official project page is the place to check current instructions, since the fact data does not document a procedure. If you are on a network that interferes with Tor, bridges are the fact-backed thing to investigate.

Bridges do not change the underlying privacy model. They are a circumvention mechanism, not an anonymity upgrade. Tor exit nodes can still observe unencrypted traffic, and Orbot still does not guarantee anonymity if users log in or reveal identity. A bridge gets you onto the network; it does not change what the network can see.

For readers outside restrictive networks, bridges are mostly irrelevant. The app works without them in ordinary conditions, and the fact data does not suggest otherwise. The feature is best understood as targeted: it exists for the networks that need it, and it is not a general performance or privacy improvement for everyone else.

What Orbot Is Not: Full VPN, Anonymity Guarantee, or Malware Shield

Orbot is not a full VPN that hides all phone traffic by default. It can act as a proxy or VPN-style service for other Android apps, and per-app routing in VPN mode means the selection determines what is routed. Treating it as a blanket tunnel is the most common way to be disappointed by it.

Orbot is not an anonymity guarantee. The fact data says plainly that it does not guarantee anonymity if users log in or reveal identity, and that Tor exit nodes can observe unencrypted traffic. It also cannot protect against a compromised device. Anonymity is a property of behavior and environment as much as of tooling, and no routing app changes that.

Orbot is not end-to-end encryption beyond the Tor exit. It routes traffic through the Tor network; it does not encrypt what an app sends in the clear. If an app transmits unencrypted data, the exit node can see it. That is a Tor property, and Orbot inherits it.

Orbot is not a malware shield, and it does not speed up or improve internet connections. Tor routing can reduce connection speed, and the fact data lists battery and performance overhead as known costs. It also does not hide Tor usage from your ISP in any documented way — the fact data makes no such claim, and readers should not assume it. What Orbot is, precisely, is a free, open-source, no-account routing layer with per-app control and bridge support. That is a narrower claim than the marketing around “privacy apps” usually implies, and it is the claim the evidence supports.

Verdict

Orbot is best judged as a selective, open-source Tor routing layer for Android. It is not a full VPN, not an anonymity guarantee, and not a replacement for Tor Browser when browsing is the only goal. Its value comes from per-app routing, bridge support for restrictive networks, and a free, no-account, BSD-3-Clause model that lets people inspect and redistribute the code.

Who it is for: users who need specific apps routed through Tor, users on restrictive networks who need bridge support, and users who want an open-source tool with no account and are willing to troubleshoot apps that Tor routing disrupts. Per-app routing in VPN mode is the feature that makes those use cases practical, and it works without root.

Who it is not for: people who want a free VPN for streaming or geo-unblocking; people expecting one-tap complete anonymity without changing app behavior; online bankers and anyone who needs stable low-latency connections; mobile gamers sensitive to latency and connection drops; users who will not troubleshoot apps that block Tor exits; and people who assume Orbot hides Tor usage from their ISP. For those audiences, the app will either underdeliver or actively get in the way.

The honest summary is that Orbot does a narrow job well and a broad job badly. If your need matches the narrow job — selective Tor routing with per-app control and bridge support — the free, open-source, no-account model is a reasonable fit. If your need is a general privacy blanket, the fact data lists Tor Browser for Android as the official Tor Project browser that uses Tor without system-wide app routing, and InviZible Pro as another open-source Android privacy app that can provide Tor-based routing. The fact data does not include version, size, minimum Android version, or install counts, so judge the app on its documented behavior, not on numbers nobody has published.

Pros

  • Free and open-source software
  • No account required
  • Can route selected apps through Tor
  • Supports bridges for restrictive networks

Cons

  • Tor routing can reduce connection speed
  • VPN mode may conflict with other VPN apps
  • Does not guarantee anonymity if users log in or reveal identity
  • Can add battery and performance overhead
Download from the official source

The link goes straight to The Guardian Project. We do not host app files.

Open official page →

Frequently asked questions

Is Orbot free?

The recorded pricing model is Free.

What license does it use?

It is listed under BSD-3-Clause.

Where can I download the official version?

The official link points to https://guardianproject.info/apps/org.torproject.android/.

This article was drafted with AI assistance using official developer documentation, release notes, privacy policies, and public data, then reviewed by an editor. We do not claim lab testing. The full method is on our Review Method page.