Briar: Peer-To-Peer Messaging Over Tor And Wi-Fi
Briar review: peer-to-peer messaging over Tor and local Wi-Fi without internet, plus how its architecture differs from Signal, Session, and SimpleX Chat.
App summary
- App
- Briar
- Developer
- Briar Project
- License
- GPL-3.0-only
- Version
- unknown
- Size
- unknown
- Price
- Free
Briar over local Wi-Fi without internet: local transport, not long-range coverage
The search query that brings most people to Briar is some version of “can I send a message with no internet and no mobile data?” The documented answer is yes, with a qualifier that matters more than the yes itself. Briar’s feature set lists Bluetooth and Wi-Fi as local, offline communication paths, sitting alongside Tor as the route used for internet connections. That is a meaningful distinction. The app is not built around a single radio, and it is not built around a single network condition.
What “local” means here is narrow and specific. Wi-Fi is a transport option, not a promise of internet-style reach. Two devices on the same wireless network, or close enough for the radios to find each other, can exchange messages without an uplink to the wider internet. That is genuinely useful in a building with a dead connection, a conference floor with saturated Wi-Fi, or a region where mobile data is expensive or unavailable. It is not a mesh network, and nothing in Briar’s documented facts suggests otherwise. The exact Wi-Fi range, the setup steps, and the minimum requirements are not specified in the available material, so any article that promises unlimited distance or blanket coverage is inventing detail.
The two paths stay separate in the design. When both parties reach each other across the internet, Briar uses Tor. When they are in the same place, Bluetooth or Wi-Fi can carry the conversation instead. That split is the whole point of the architecture: the app does not force every message through an anonymizing network when a short-range radio would do, and it does not pretend a short-range radio is a substitute for the internet.
One question follows immediately, and it deserves a direct answer: how do you receive messages while you are offline? Based on the documented transports, local delivery depends on proximity or a shared network. The fact sheet describes no store-and-forward relay, no offline queue held by a third party, and no server that sits waiting to hand you messages when you reconnect. If your phone is off, or out of radio range, or not on the same local network, there is no described mechanism that will hold the message for you. That is a consequence of removing central servers, and it is the kind of trade-off you should decide about before, not after, you rely on the app.
Briar vs Signal, Session, and SimpleX Chat: how architecture changes the privacy trade-off
Signal is the reference point most people carry in their heads, and the contrast is clean. Signal is described as a widely used end-to-end encrypted messenger that relies on centralized servers and a phone number. That combination produces a particular trust model: you trust the operator’s infrastructure to relay your traffic, and you accept that a phone number ties the account to something real. For a lot of people that is a perfectly reasonable bargain, and it comes with the convenience of a contact list that already exists.
Briar inverts the arrangement. It is peer-to-peer with no central server dependency, it uses Tor for internet connections, and it requires no phone number or email address. There is no operator holding your message queue, because there is no operator in that sense. The trust shifts outward, to the person on the other end and to the routing layer carrying the traffic. Setup shifts too: without a phone number to look up, contact discovery has to happen some other way, which is why contact links and QR codes exist in the app.
Session and SimpleX Chat occupy their own corners of this space. Session is described as a decentralized messenger using onion routing, with a different architecture from Briar’s. SimpleX Chat is described as designed without user identifiers, which is another approach to the same underlying problem of removing the obvious hooks that tie a messenger account to a person. None of these three is a reskin of the others. They make different bets about where the weak point is and what should be removed first.
What the comparison does not establish is the thing people most want it to establish. None of this architecture makes a user anonymous. Briar removes the phone number and the email address, and it removes the central server, but it does not remove the content of what you type or the fact that the person you are messaging knows who you are. If you write your home address into a Briar message, the recipient has your home address. The design changes who holds what and which parties have to be trusted; it does not erase the information you volunteer. Treating Briar as an anonymity switch is the most common way to misuse it.
Briar is not a WhatsApp replacement: no calls and Briar-only contact exchange
Start with the feature that ends the conversation for most casual users: Briar has no voice or video calling. Not a limited version, not a beta, not a feature behind a toggle. It is a text-first messenger, and the documented shortcomings list says so plainly. Anyone whose messaging life runs on voice notes and video calls is looking at the wrong app, and no amount of enthusiasm about Tor routing changes that.
Contact exchange is the second wall. Both people have to be using Briar, and they have to exchange contact links or QR codes to connect. There is no phone-number lookup, no email search, no address book scan that quietly matches you to everyone you already know. That is a direct consequence of not requiring a phone number or an email address, and it is a feature as much as a cost. The cost is friction. Adding one contact is a small ceremony; adding twenty is an afternoon.
Briar’s own documented shortcomings acknowledge the convenience gap. The app may be less convenient than mainstream messengers because of its Tor and peer-to-peer design. That sentence is doing a lot of work. It covers slower connection setup, the absence of a server that keeps your messages warm while you are away, and the general fact that a decentralized system asks more of the user than a centralized one does.
This is why the wrong audience is easy to name. Casual users who want voice and video calling will bounce off immediately. People unwilling to manage QR code or link-based contact exchange will find the app hostile within minutes. Non-technical users who want zero-setup messaging, and anyone expecting cloud backup and easy account recovery as a default, are all outside the intended group. Briar is not hostile to those people; it simply was not built with them in mind, and the documentation is honest about it.
Briar on iPhone: Android-only platform makes iOS a non-starter
Briar is listed as an Android app. That is the whole platform story in the available facts, and it is worth stating without hedging. There is no official iOS version in the material, and no indication that one exists. An iPhone user cannot treat Briar as an App Store download, and an article that implies otherwise is setting up a disappointment.
The practical consequence shows up in mixed households and mixed teams. If the person you most want to message carries an iPhone, the conversation ends before it starts. That is not a small edge case. Most social circles are split across platforms, and a messenger that only exists on one of them is a messenger you use with a subset of your contacts, or not at all. Anyone planning to move a group chat to Briar should check devices first.
Platform guidance beyond that has to stay inside verified territory. The exact latest version number is unknown, the APK size is unknown, the minimum Android version is unknown, and the download count is unknown. That means this review cannot tell you whether your five-year-old phone will run it, how much storage to set aside, or how large the installed user base is. What can be said is that the app is free, it is developed by the Briar Project, and it is distributed through Google Play and F-Droid, with briarproject.org as the official starting point.
Anonymity and metadata: correcting the assumptions
The first assumption to retire is that Briar makes you fully anonymous. It does not, and it does not claim to. What it does is remove the phone number and email requirement and remove the central server dependency. Those are structural changes to who can collect what. They are not a cloak. If you reveal personal details inside a conversation, the person you are talking to has those details, and no routing layer takes them back.
The second assumption is that Briar hides metadata from everyone, including your contacts. Your contact knows you are messaging them. That is not a flaw; it is what a conversation is. What the peer-to-peer design removes is the middle party that would otherwise sit between you and hold a record of the exchange. The distinction matters when you are deciding what to trust the app with. It protects the channel and removes the intermediary. It does not make you invisible to the person on the other end.
The third assumption is that messages are disappearing or ephemeral by default. Nothing in the documented feature set describes disappearing messages as a default behavior, so do not install Briar expecting conversations to evaporate. If that property matters to you, verify it inside the app rather than assuming it from the privacy framing. The same caution applies to Tor. The documented role of Tor is as the path for internet connections, not as a content shield. It changes how traffic reaches the other side. It does not change what you wrote.
Licensing, cost, and official distribution
Briar is free, and it is open source under GPL-3.0-only. Those two facts together explain a lot about the project’s posture. The license permits inspection and modification, and the documented advantage is straightforward: the code is open source and auditable, which means claims about how it works can in principle be checked rather than taken on faith. That is a real difference from a closed messenger, even if most users will never read a line of it.
The developer is the Briar Project, and the official site is briarproject.org. Verified distribution runs through Google Play and F-Droid. Those are the channels to use. Sideloading a repackaged APK from a random mirror defeats the entire point of an auditable open-source messenger, because you no longer know whether the binary matches the code anyone audited. If you want the app, start at the official site and follow its links.
Being open source is not the same as having been audited by a specific outside party on a specific date, and the available facts do not name one. That is a distinction worth keeping straight. The license guarantees that scrutiny is possible. It does not guarantee that any particular scrutiny has happened, and it certainly does not guarantee that the current build on your phone is the one anyone looked at.
What the fact sheet leaves open: version, size, minimum Android, groups, recovery
Several things a normal app review would cover are simply not established here. The exact latest version number is unknown. The APK size is unknown. The minimum Android version is unknown. The download count is unknown. Those gaps are not trivial, because they are exactly the details a reader uses to decide whether an app fits their device and their patience. This review will not fill them in with guesses.
Group features are another open question. Readers ask whether Briar supports group chats, forums, and file sharing. The documented feature list covers peer-to-peer encrypted messaging and the transports that carry it: Tor, Bluetooth, and Wi-Fi. It does not enumerate group functionality, forum-style discussion, or file transfer. Treat those as unverified until you confirm them in the app itself. The same goes for large public channels and very large groups, which are a poor fit for a peer-to-peer design in general and are not described as a supported use case here.
Account recovery deserves its own warning. Nothing in the available facts describes cloud backup or a recovery mechanism. Combine that with the absence of a phone number or email address, and there is no obvious account anchor described anywhere in the material. If you lose the phone, do not assume you can restore the account and its history. That uncertainty is a direct cost of the same design that keeps a central server out of the picture, and it is the kind of cost that only hurts once.
What this review does not claim: battery, notifications, transfer speed
Battery behavior is not covered by the available facts, so this review makes no claim about it. It is reasonable to expect that a messenger routing internet traffic through Tor and using Bluetooth or Wi-Fi for local delivery will draw power in ways a simple client-server app does not, but reasonable expectation is not documentation. If battery life is your deciding factor, test it on your own device rather than trusting a number from an article.
Notification reliability is in the same category. There is no data here on how promptly messages arrive, how the app behaves when the system restricts background activity, or what happens on aggressive battery-saving configurations. Those are real concerns for peer-to-peer messengers, and they are exactly the kind of concern that gets asserted confidently online without evidence. This review will not add to that pile.
Transfer speed and large-file handling are also undocumented. Heavy media sharers needing fast large-file transfers are already the wrong audience for a peer-to-peer, Tor-routed messenger, and the absence of any stated performance figures reinforces that. If your use case involves moving big video files between phones on a deadline, Briar is not the tool the documentation describes.
Verdict
Briar is a credible Android-only, open-source, peer-to-peer messenger for text communication without a phone number or an email address. It routes internet traffic through Tor, it can fall back to Bluetooth or Wi-Fi for local exchanges, and it does not depend on a central server. Those are unusual properties, and they are documented rather than implied. For a journalist working in a place where the local network is unreliable, a small team that needs to talk without a middle party, or anyone who objects on principle to handing a phone number to a messaging company, the design has a clear argument behind it.
It is not a mainstream replacement for WhatsApp, and the reasons are concrete rather than ideological. There are no voice or video calls. Contacts must already use Briar and must exchange a link or a QR code before anything works. The Tor and peer-to-peer design makes the app less convenient than the messengers most people use, by the project’s own account. Local Wi-Fi is a transport, not a coverage guarantee, and the exact range and setup are not specified anywhere in the available material. The version number, APK size, minimum Android version, and download count are all unknown, so device-fit guidance has to stop at “it is an Android app.”
iPhone users are out entirely. Casual users who want calls will be unhappy within a day. People who need large public channels or very large groups, heavy media sharers, and anyone expecting cloud backup and painless account recovery should look elsewhere. Non-technical users who want zero-setup messaging will find the contact exchange alone to be a barrier.
The right way to decide is to ask what you actually need. If you need a text channel that does not require a phone number, does not route through a company’s servers, and can work when the internet does not, Briar is one of the few apps that matches that description. If you need a messenger that everyone you know can install and use without instruction, with calls and effortless contact discovery, Briar is the wrong tool, and its own documentation says so. Start at briarproject.org, install from Google Play or F-Droid, and go in with the limits in view rather than discovering them later.
Pros
- Open source and auditable
- Does not require a phone number or email address
- Can communicate without internet access via Bluetooth or Wi-Fi
Cons
- No voice or video calling
- Contacts must use Briar and exchange contact links or QR codes
- May be less convenient than mainstream messengers because of its Tor and peer-to-peer design
The link goes straight to Briar Project. We do not host app files.
Frequently asked questions
Is Briar free?
The recorded pricing model is Free.
What license does it use?
It is listed under GPL-3.0-only.
Where can I download the official version?
The official link points to https://briarproject.org/.