Last updated: March 16, 2026

During Iran’s internet blackouts, use Briar Messenger, which works entirely offline through Bluetooth and Wi-Fi Direct without needing centralized servers or internet connectivity. Install Briar on Android or Linux, create an account, and exchange QR codes with contacts in person. Briar’s peer-to-peer design makes it impossible to censor and is the most reliable messaging tool when traditional internet access is completely blocked.

Table of Contents

Why Briar Works When Other Apps Fail

Conventional messaging apps require internet connectivity to reach servers. When Iran blocks internet traffic at the ISP level, these apps become useless. Briar takes a fundamentally different approach by enabling direct device-to-device communication through Bluetooth and Wi-Fi Direct.

The application creates an encrypted mesh network where messages hop between nearby devices. This means as long as two people are within Bluetooth or Wi-Fi range, they can communicate, even if all external internet connections are blocked. The network effect amplifies reach: messages can propagate across multiple hops through a chain of devices, creating resilient communication chains during crises.

Unlike VPN-based solutions that attempt to bypass blocks, Briar doesn’t need external connectivity at all. This makes it particularly effective for protest coordination, news dissemination, and family communication during complete internet blackouts.

Prerequisites

Before you begin, make sure you have the following ready:

Step 1 - Install Briar on Android

Briar is available exclusively on Android through F-Droid and Google Play. For maximum privacy, install from F-Droid, which provides reproducible builds and eliminates Google Play tracking.

Installation steps:

  1. Download Briar from F-Droid or Google Play
  2. Install the application
  3. Launch Briar and create your identity
  4. Set a strong passphrase to encrypt your local database

The initial setup takes approximately two minutes. You’ll need to remember your passphrase, there’s no password recovery mechanism since Briar operates without cloud infrastructure.

Step 2 - Set Up Peer-to-Peer Communication

Briar offers two primary connection methods for adding contacts without internet access: Bluetooth and Wi-Fi Direct. Each has distinct advantages depending on your situation.

Bluetooth Connections

Bluetooth works at ranges up to 100 meters in ideal conditions, though concrete walls and interference typically reduce this to 10-30 meters. It’s ideal for contact within the same building or nearby outdoor locations.

To add a contact via Bluetooth:

  1. Both users open Briar and navigate to Contacts → Add Contact
  2. Select Bluetooth as the connection method
  3. One device scans for nearby Briar users
  4. Select the correct contact from the discovered devices
  5. Confirm the contact on both devices

Wi-Fi Direct Connections

Wi-Fi Direct offers faster data transfer and longer range than Bluetooth, typically 200 meters line-of-sight. It’s better for exchanging larger amounts of data or when devices are further apart.

To add a contact via Wi-Fi Direct:

  1. Ensure Wi-Fi is enabled (internet connection not required)
  2. Navigate to Contacts → Add Contact → Wi-Fi Direct
  3. Wait for discovery to find nearby contacts
  4. Select the contact and confirm on both devices

Step 3 - Connecting Without Physical Proximity

During internet blackouts, you may need to connect with contacts you’ve never met in person. Two methods solve this challenge:

Contact Links

Briar generates shareable contact links containing your public key. These links can be shared through any available channel, printed on paper, read aloud over phone lines, or transmitted through any functional communication method.

To create a contact link:

  1. Navigate to your profile
  2. Select “Share Contact”
  3. Copy the generated link or display as QR code
  4. Share through any available method

Recipients paste the link or scan the QR code to establish an encrypted connection without meeting physically.

QR Code Exchange

For scenarios where visual exchange is possible, QR codes provide a quick method:

  1. Both users open the QR code scanner
  2. One user displays their QR code
  3. The other scans it
  4. Connection establishes automatically

This method works well at protest gatherings, community meetings, or any situation where participants can see each other.

Step 4 - Message Propagation Across the Mesh

Once connected to even one other Briar user, your messages can reach surprising distances through message propagation. When your contact’s device connects to another device, your messages sync automatically, no action required from you.

This creates remarkable resilience. In a protest scenario with many participants running Briar, information spreads organically across the mesh network. A message from one corner of a city can propagate to all connected devices within hours, independent of any central infrastructure.

The propagation continues as long as devices remain online. Even if you power down your phone, messages queue and sync when you reconnect to any mesh peer.

Step 5 - Practical Considerations for Iran

For users in Iran specifically, several factors improve Briar effectiveness:

Device distribution - The more people running Briar, the stronger the mesh network. Encourage trusted contacts, family members, and protest organizers to install the app before connectivity is restricted.

Multiple contact circles - Create separate contact groups for different purposes, a family circle, an organizational circle, and a broader community circle. This limits exposure if any single contact’s device is compromised.

Offline message composition - You can write messages while disconnected; they send automatically when any mesh connection becomes available. Compose important messages in advance during periods of connectivity.

Battery management - Bluetooth and Wi-Fi Direct consume significant power. Carry portable chargers when expecting extended blackout periods.

Step 6 - Limitations to Understand

Briar cannot solve every communication challenge. Consider these constraints:

Step 7 - Security Architecture

Briar’s security model deserves understanding. All messages use end-to-end encryption based on the Signal protocol. Keys are generated locally and never leave your device unless you explicitly share them.

The application stores all data locally, not on remote servers. This eliminates server seizure risks but means losing your device loses your data. Regular local backups to encrypted storage provide protection against device loss.

Importantly, Briar’s peer-to-peer nature makes traffic analysis extremely difficult. Unlike server-based messaging where metadata reveals who communicates with whom, mesh networks create ambiguous communication patterns that resist surveillance.

Step 8 - Build Your Communication Plan

Effective crisis communication requires preparation:

  1. Install Briar now, before any blackout occurs
  2. Add trusted contacts while you have reliable connectivity
  3. Exchange contact information with organizational allies
  4. Test Bluetooth and Wi-Fi Direct connections in advance
  5. Establish backup communication methods for extreme scenarios
  6. Educate your circle about proper usage

Having Briar operational before internet restrictions begin gives you the best chance at maintaining communication when it matters most.

Install Briar on Android via ADB when app stores are unavailable
Download the APK from briarproject.org while internet is accessible

Enable USB debugging - Settings -> Developer Options -> USB debugging
adb devices
adb install -r briar.apk

Verify installation
adb shell pm list packages | grep briar

Briar Desktop on Linux (Debian/Ubuntu)
wget https://desktop.briarproject.org/releases/briar-desktop-latest.deb
sudo dpkg -i briar-desktop-latest.deb

Advanced Briar Configurations for Maximum Reach

Once the basics are working, advanced configurations extend Briar’s capabilities:

Bridge Mode for Extended Range - If you have access to a more stable network location, you can establish a Briar instance that acts as a bridge for others:

On a device with reliable network access
Set up Briar on Linux (stable bridge node)
sudo systemctl enable briar-desktop
sudo systemctl start briar-desktop

Keep this device powered on to relay messages
It acts as infrastructure supporting the mesh network

Offline Message Composition and Queuing - Briar queues messages when recipients aren’t available. Take advantage of this:

  1. Compose important messages during periods of connectivity
  2. Send them even if recipients are offline
  3. Messages will sync when both devices are in range
  4. This allows asynchronous communication without real-time availability

Step 9 - Community Coordination Using Briar

Briar’s peer-to-peer nature enables new forms of community coordination:

Forum Creation - Briar supports private forums for group communication:

  1. Creator establishes a forum in Briar
  2. Shares forum link with trusted contacts
  3. Forum members can discuss topics without central moderation
  4. All members receive all messages (high bandwidth but reliable)

Blog Functionality - Briar includes blog features for information dissemination:

  1. Create a blog as an individual user
  2. Share your blog with Briar contacts
  3. Information reaches all followers when they sync
  4. No server required, just peer-to-peer distribution

Use these features for coordination during blackouts:

Step 10 - Briar for Other Offline Scenarios

Beyond Iran internet blackouts, Briar applies to other scenarios:

Natural Disaster Communication - When earthquake, hurricane, or flood damages infrastructure:

Infrastructure Failure - Extended power outages or network infrastructure failures:

Authoritarian Regimes - Any government attempting to control communication:

Security Considerations During Use

While using Briar in crisis situations, maintain security awareness:

Device Seizure Risk - In oppressive regimes, your device containing Briar might be seized. Since Briar stores encrypted message databases locally:

  1. Set a strong passphrase during initial setup
  2. Understand that the passphrase is your only protection if device is seized
  3. Consider using plausible deniability, an innocuous passphrase that opens a decoy profile
  4. Know that forensic techniques might eventually compromise encrypted data

Contact Identification Risk - Adding contacts reveals their identities to you. In crisis scenarios:

  1. Use nicknames rather than real names for contacts
  2. Avoid maintaining a master list of contact-to-identity mappings
  3. Know which individuals operate which devices by device firmware
  4. If compromised, this information cannot be extracted from Briar

Metadata Analysis - While Briar encrypts message content, communication patterns can reveal information:

  1. Time of communication might reveal participant location
  2. Frequency of communication might reveal relationships
  3. Unusual communication patterns might draw attention
  4. Use communication inconsistently to avoid patterns

Step 11 - Integrate Briar Into Crisis Planning

Organizations preparing for potential blackouts should plan Briar integration:

Pre-Crisis Setup:

  1. Install Briar on core team members’ devices
  2. Establish contact network during normal operations
  3. Test Bluetooth and WiFi Direct connectivity
  4. Document Briar usage procedures for team members
  5. Establish signal procedures, how to convene via Briar if infrastructure fails

Crisis Activation:

  1. Switch to Briar-based communication
  2. Coordinate via forums for group decisions
  3. Use messaging for immediate information exchange
  4. Maintain message backup by saving important communications

Post-Crisis:

  1. Preserve message history for documentation
  2. Deactivate crisis protocols
  3. Review what worked and what didn’t
  4. Improve procedures for future scenarios

Step 12 - Limitations You Should Know

Briar isn’t a complete communication replacement. Understand what it can’t do:

For critical operations, supplement Briar with other communication methods you can access during blackouts.

Step 13 - Success Stories and Lessons

Briar proved itself during internet blackouts in multiple contexts:

During Hong Kong 2019-2020 protests, activists used Briar to coordinate despite internet filtering. Messages propagated organically through protest crowds, enabling coordination without infrastructure dependence.

During Iran 2022 protests, Briar enabled communication when cellular networks were blocked. Participants traveled to public squares with Briar running on phones, messages synced through the gathering crowd enabling real-time coordination.

The key lesson - infrastructure independence is powerful. When you remove dependency on centralized servers, you gain resilience that oppressive systems cannot easily suppress.

Troubleshooting

Configuration changes not taking effect

Restart the relevant service or application after making changes. Some settings require a full system reboot. Verify the configuration file path is correct and the syntax is valid.

Permission denied errors

Run the command with sudo for system-level operations, or check that your user account has the necessary permissions. On macOS, you may need to grant terminal access in System Settings > Privacy & Security.

Connection or network-related failures

Check your internet connection and firewall settings. If using a VPN, try disconnecting temporarily to isolate the issue. Verify that the target server or service is accessible from your network.

Frequently Asked Questions

How long does it take to use briar messenger during iran internet blackout?

For a straightforward setup, expect 30 minutes to 2 hours depending on your familiarity with the tools involved. Complex configurations with custom requirements may take longer. Having your credentials and environment ready before starting saves significant time.

What are the most common mistakes to avoid?

The most frequent issues are skipping prerequisite steps, using outdated package versions, and not reading error messages carefully. Follow the steps in order, verify each one works before moving on, and check the official documentation if something behaves unexpectedly.

Do I need prior experience to follow this guide?

Basic familiarity with the relevant tools and command line is helpful but not strictly required. Each step is explained with context. If you get stuck, the official documentation for each tool covers fundamentals that may fill in knowledge gaps.

Is this approach secure enough for production?

The patterns shown here follow standard practices, but production deployments need additional hardening. Add rate limiting, input validation, proper secret management, and monitoring before going live. Consider a security review if your application handles sensitive user data.

Where can I get help if I run into issues?

Start with the official documentation for each tool mentioned. Stack Overflow and GitHub Issues are good next steps for specific error messages. Community forums and Discord servers for the relevant tools often have active members who can help with setup problems.

Related Articles