Tor Portable: a standalone Tor core for people who cannot use the browser bundle

A Tor core separated from the browser

The project's premise is stated in the README as a principle rather than a feature list. Tor is not a browser, and the author says so twice, in the tagline and again in the philosophy section.

The argument is that binding the Tor core to a browser creates two problems: an excessive dependence on the browser, which always requires a connection to the Tor network, and a lack of exits hidden from external censorship. The author also notes that binding to a browser prevents maintaining support for Windows 7. The philosophy section claims the exits issue has been officially acknowledged upstream, with a link to a Tor Project issue, and that an independently built core was what made an early patched and censorship resistant Webtunnel possible for a community before similar changes reached the official development version.

So the deliverable is a simple, fully portable core with configuration files for interacting with it, described as working on Linux and on Windows 7 and 8 and later, with 2025 version Webtunnel protocol support. The stated goal is to provide free access to the internet for as many people as possible while living under strict censorship.

The project also states its method plainly: freely combining, modifying and distributing available open source solutions, and it says the aim is popularity through simplicity and accessibility. The author is explicit that the motivation is opposition to authoritarianism rather than any larger claim, which is a useful thing to know when you are assessing how the project will be maintained.

AntiTor and service-manager are the two launch paths

The README's installation section names exactly which files matter, and that is the most operationally useful paragraph in the document. After unpacking the archive you select the Tor build you need, and the advice is to avoid special characters in the folder path.

Running AntiTor opens Tor for the current session, while running service-manager creates a service. AntiTor and service-manager are described as the only two files that will run Tor correctly. Tor is launched through AntiTor.exe, which minimises itself immediately, and that is what makes it compatible with startup entries and with pinning the executable to the taskbar; autostart does exactly that, and running it again removes the service or the autostart entry.

There is a third path with a caveat. Opening tor.exe inside the tor folder launches a pure, bridgeless core Tor, and the README warns it can take a significant amount of time to find its directory, although if it succeeds it might even work quite well. That is a debugging path rather than a supported one, and the word bridgeless in that sentence is doing important work: a core without bridges configured will not reach the network in most censored environments.

For a Windows 7 build there is an extra constraint, and the wording is blunt: do not mix up the bitness. If you have, the README points to a reset-oldwin-patch file and to downloading the correct version.

Webtunnel, the hosts list and the pieces borrowed from elsewhere

The repository credits a long list of contributors and upstream projects, and the credits section is effectively the architecture of the distribution.

The core is the Tor Expert Bundle from the Tor Project, with the core code attributed to the Tor Project's own core repository and to the lyrebird pluggable transports repository. On top of that sit community projects: a Win 7 patcher by stunnard, a hosts list by dartraiden, SwitchyOmega and ZeroOmega for browser side switching, and the Antizapret proxy by ValdikSS. The README also credits work on the Discord related tooling, with separate projects for a Discord drover and a Linux bypass, and credits for testing the Win 7 builds and the Linux portable deployment, with the Linux deployment work referenced against nixpkgs issues.

The anti-censorship transport story is the interesting part for an engineer evaluating this. The README states that the Russian community used a patched, censorship resistant version of Webtunnel several months before the developers introduced similar changes, while noting that the official development version is safer and therefore significantly better. That is an unusually candid statement about the trade-off between a fast community patch and an upstream implementation, and it also explains why an independent core build is necessary at all: a patched transport has to be compiled into a core that the official bundle does not provide.

The concept, the configurations, the Win 7 patch, the Linux portable deployment, the update system, the services, the guide and the executable code are all attributed to the project author, and the elevation system for the batch files is credited with review and editing from outside.

Distribution over IPNS, and an updater you pipe to bash

Where you get the build is unusual, and the reasoning is documented. Tor Portable is hosted on IPNS, described as an eternal cloud, and the stated reason is that proprietary clouds are unreliable, with the additional note that GitHub has mistakenly removed Tor Portable several times, making it unavailable. The distribution uses pinata.cloud and ipns.ipfs.network, and the author explicitly advises against free proprietary clouds such as MEGA because of their censorship and lack of features, and because dependence on them deprives users of technological sovereignty.

The download link points at an orbitor.dev IPNS path, and on Linux the README gives a one line command:

`curl -fsSL https://eu.orbitor.dev/ipns/k51qzi5uqu5dldod6robuflgitvj276br0xye3adipm3kc0bh17hfiv1e0hnp4/updater.sh | bash`

The script downloads and unpacks the build, after which you select the Tor variant you want.

Two practical cautions belong next to that command. Piping a remote script straight into a shell means the code you run is whatever is at that address at that moment, so for a security critical tool the hash or signature of the artifact is the thing to check, and the README does not describe a verification step for the downloads. And a content addressed network gives you a name that resolves to changing content, so pinning is a deliberate act rather than a default.

What the repository actually contains

The file list at the top level is short and mostly scripts and launcher sources rather than the Tor binaries themselves.

On the Windows side there are the batch files and their sources: AntiTor.cpp, AntiTor.exe and AntiTor.ico as the launcher, service-manager.cmd and service-manager.sh for the service, autostart.cmd for the startup entry, change-mode.cmd and change-mode.sh to switch mode, service-check.sh, reset-oldwin-patch.cmd for undoing the Windows 7 patch, and updater.cmd and updater.sh. The Linux counterparts are the.sh files, including AntiTor.sh, lyrebird.sh for the pluggable transport, conjure.sh, discord.sh, full-stop.sh and service-manager.sh.

The resource files icon.rc, icon.res, version.rc and version.res are what a Windows executable is compiled from, and build-commands.txt sits alongside them, which tells you the build recipe is in the repository rather than in a wiki page. README-RU.md is the Russian translation of the README, and the main README links to it at the top.

The primary language of the repository is listed as Batchfile, which tells you the real logic of the distribution is in the Windows batch scripts with the C++ launcher as the one compiled component.

For the release history, the tags are unusual strings rather than plain numbers, with a pattern that combines the Tor version, a Webtunnel component, and three short codes, for example a v2.95W-2.90.1L tag dated 2026-10-12, alongside tags named Tor Portable rather than Tor for the portable build. The last push to the repository was on 2026-10-12, and the releases are frequent, with tags in September and October 2026.

An unofficial build, and what that means for trust

Two things about the legal and trust position are worth stating plainly.

On the licence, the philosophy section says the project shares the BSD-3 license common to Tor, and the LICENSE file is in the repository. The project metadata, however, classifies the licence as a custom one that the platform cannot categorise, which is a signal worth checking rather than assuming, because the repository combines code from several upstream projects with different terms, and the bundled Tor core carries the Tor Project's own licensing. A team redistributing these builds should read the LICENSE file and the upstream terms rather than rely on the one line summary in the README.

On trust, this is a custom build of a security critical tool. The core is compiled by the project rather than downloaded from the Tor Project, the transports are patched, the bridge configuration is the author's own work, and the distribution channel is a content addressed network with a shell script installer. The README's own framing, an independent core build enabling fast community patches, is the upside and the downside at the same time. It means a censorship resistant transport can ship quickly, and it also means the binary is not the one the Tor Project publishes and signs.

None of that makes the project unsafe to use, particularly for the audience it targets, but it does change the evaluation. You are trusting a maintainer and their build chain, not upstream release signatures, and the relevant verification is whether the release you run matches the tag in the repository, whether the configuration you rely on is the one you configured, and whether the update mechanism you use is the one you inspected.

Editorial conclusion

Adopt Tor Portable if you need the Tor core without the Tor Browser, you are on a platform the browser bundle no longer supports, or you need a configuration set for a specific censored network and can work with a community build. Do not adopt it as a default client for everyday browsing, since the browser bundle remains the maintained path, and do not deploy it where provenance matters without auditing it first, because these are custom builds of a security critical tool distributed over a content addressed network. Verify first that the binary you download matches the release notes for your platform, that the bridge and transport configuration you rely on is the one you configured, and that the licence file in the repository covers the redistribution you intend, since the project metadata classifies the licence as a custom one while the README states it shares the BSD-3 licence common to Tor.

Frequently asked questions

Official sources

1. Chara-Freedom/Tor-Portable on GitHub
2. Issues
3. README
4. Releases