Freedom Browser — decentralized web browsing with Swarm, IPFS, Radicle, ENS, and Tezos Domains
See the codeFreedom is a browser for the decentralized web, with Swarm, IPFS, onchain applications, Radicle, ENS, and Tezos Domains as first-class protocols. Integrated Ant, freedom-ipfs, Radicle, experimental Myotis, and Tor components provide direct access to decentralized and onion networks without relying on centralized HTTP gateways.
Download the latest build for macOS, Linux, or Windows from the official download page at freedom.baby.
Radicle is available on macOS, Linux, and Windows (x64 and ARM64). The release workflow bundles the Tor (Arti) client for macOS arm64, Linux x64/arm64 and Windows x64. Windows x64 bundling landed in September 2026, so only releases cut after that carry Arti on Windows — an earlier Windows install has none, and updating to the latest build is the fix. No Windows ARM64 build is published at all, so .onion access is unavailable on that architecture.
bzz://, ipfs://, ipns://, web3://, and rad:// navigation, plus optional .onion routing through Tor..eth, .box, .wei, .gwei, and .tez names.See the feature guide for the detailed capability list.
Development uses Node.js 24 LTS. The exact repository version is pinned in .nvmrc.
nvm install
nvm use
npm ci
npm run ant:download
npm run ipfs:download
npm run myotis:download
npm run myotis:build-supervisor
npm start
Swarm and IPFS start automatically. Radicle and Myotis are opt-in under Settings → Startup. Run npm run radicle:download before enabling Radicle under Settings → Nodes; run npm run tor:download (macOS, Linux, and Windows) before enabling Tor under Settings → Experimental — the Tor rows only appear once that build exists. For prerequisites, platform notes, tests, debugging, and local builds, read the development guide.
Freedom is an Electron application. Protocol, node-lifecycle, permission, wallet, download, and persistence logic lives in the main process. The renderer is a modular UI layer that communicates with the main process through the allowlisted channels in src/shared/ipc-channels.js.
The main process handles bzz:, ipfs:, ipns:, web3:, rad:, and .onion navigation, manages per-profile nodes and storage, and resolves supported decentralized names. web3: needs no node or gateway: the handler reads the contract's ERC-8244 html() document through the same chain-data router the wallet uses. Security-sensitive capabilities stay out of page and renderer contexts unless exposed through a narrow preload or IPC API.
| Directory | Responsibility |
|---|---|
src/main/ | Electron main process, services, native nodes, protocol handlers, IPC, and persistence |
src/renderer/ | Browser UI, internal pages, navigation, settings, and dApp integration |
src/shared/ | Constants and utilities shared across processes |
test-e2e/ | Playwright harness and live Electron tests |
config/ | Runtime templates, default data, and platform entitlements |
scripts/ | Build, download, smoke-test, and maintenance tooling |
docs/ | User, protocol, contributor, and maintainer documentation |
Contributors changing process responsibilities or adding IPC channels must follow the architecture boundaries.
freedom:// pages or narrow provider surfaces.Do not post credentials, seed phrases, private keys, or sensitive logs in public issues. See CONTRIBUTING.md for disclosure guidance.
Read CONTRIBUTING.md before opening an issue or pull request. It explains issue scope, local verification, commit conventions, licensing, and the policy for AI-assisted contributions.
Freedom Browser is available under the Mozilla Public License 2.0. Third-party notices are recorded in NOTICES.
JavaScript
90.5%
HTML
6.3%
CSS
2.9%
Freedom Browser — decentralized web browsing with Swarm, IPFS, Radicle, ENS, and Tezos Domains
See the codeFreedom is a browser for the decentralized web, with Swarm, IPFS, onchain applications, Radicle, ENS, and Tezos Domains as first-class protocols. Integrated Ant, freedom-ipfs, Radicle, experimental Myotis, and Tor components provide direct access to decentralized and onion networks without relying on centralized HTTP gateways.
Download the latest build for macOS, Linux, or Windows from the official download page at freedom.baby.
Radicle is available on macOS, Linux, and Windows (x64 and ARM64). The release workflow bundles the Tor (Arti) client for macOS arm64, Linux x64/arm64 and Windows x64. Windows x64 bundling landed in September 2026, so only releases cut after that carry Arti on Windows — an earlier Windows install has none, and updating to the latest build is the fix. No Windows ARM64 build is published at all, so .onion access is unavailable on that architecture.
bzz://, ipfs://, ipns://, web3://, and rad:// navigation, plus optional .onion routing through Tor..eth, .box, .wei, .gwei, and .tez names.See the feature guide for the detailed capability list.
Development uses Node.js 24 LTS. The exact repository version is pinned in .nvmrc.
nvm install
nvm use
npm ci
npm run ant:download
npm run ipfs:download
npm run myotis:download
npm run myotis:build-supervisor
npm start
Swarm and IPFS start automatically. Radicle and Myotis are opt-in under Settings → Startup. Run npm run radicle:download before enabling Radicle under Settings → Nodes; run npm run tor:download (macOS, Linux, and Windows) before enabling Tor under Settings → Experimental — the Tor rows only appear once that build exists. For prerequisites, platform notes, tests, debugging, and local builds, read the development guide.
Freedom is an Electron application. Protocol, node-lifecycle, permission, wallet, download, and persistence logic lives in the main process. The renderer is a modular UI layer that communicates with the main process through the allowlisted channels in src/shared/ipc-channels.js.
The main process handles bzz:, ipfs:, ipns:, web3:, rad:, and .onion navigation, manages per-profile nodes and storage, and resolves supported decentralized names. web3: needs no node or gateway: the handler reads the contract's ERC-8244 html() document through the same chain-data router the wallet uses. Security-sensitive capabilities stay out of page and renderer contexts unless exposed through a narrow preload or IPC API.
| Directory | Responsibility |
|---|---|
src/main/ | Electron main process, services, native nodes, protocol handlers, IPC, and persistence |
src/renderer/ | Browser UI, internal pages, navigation, settings, and dApp integration |
src/shared/ | Constants and utilities shared across processes |
test-e2e/ | Playwright harness and live Electron tests |
config/ | Runtime templates, default data, and platform entitlements |
scripts/ | Build, download, smoke-test, and maintenance tooling |
docs/ | User, protocol, contributor, and maintainer documentation |
Contributors changing process responsibilities or adding IPC channels must follow the architecture boundaries.
freedom:// pages or narrow provider surfaces.Do not post credentials, seed phrases, private keys, or sensitive logs in public issues. See CONTRIBUTING.md for disclosure guidance.
Read CONTRIBUTING.md before opening an issue or pull request. It explains issue scope, local verification, commit conventions, licensing, and the policy for AI-assisted contributions.
Freedom Browser is available under the Mozilla Public License 2.0. Third-party notices are recorded in NOTICES.
JavaScript
90.5%
HTML
6.3%
CSS
2.9%