What Is Meshtastic? How the LoRa Mesh Network Works

Meshtastic is a free, open-source firmware project that turns inexpensive LoRa radios into a long-range, off-grid text messaging network. Each radio (a “node”) rebroadcasts messages it hears, so a message can hop across several radios to reach someone well beyond the range of your own device, with no cell towers or internet involved.

The official introduction describes it as “a project that enables you to use inexpensive LoRa radios as a long range off-grid communication platform in areas without existing or reliable communications infrastructure.” This guide explains how that works, what you need, and where its limits are. It is a researched explainer based on the official documentation; LoRa Mesh Atlas is not affiliated with the Meshtastic project.

Is Meshtastic a real thing?

Yes. Meshtastic is an established open-source project with public code on GitHub, official documentation at meshtastic.org, and official apps for Android, Apple platforms, and the web. “Meshtastic” is a registered trademark of Meshtastic LLC, according to the project’s licensing and trademark page.

The firmware itself runs on hardware made by many different companies. The project’s Getting Started page groups supported boards by chip family (ESP32, nRF52, RP2040/RP2350, and STM32) and separates officially supported partner hardware from community-supported hardware. For specific devices, see our device database.

How does Meshtastic work?

LoRa radio, not Wi-Fi or cellular

Meshtastic uses LoRa, a long-range, low-data-rate radio modulation. At the physical layer, LoRa uses chirp spread spectrum: each symbol is a tone that sweeps across the channel’s bandwidth (Overview). The trade-off is speed. The default Long Fast preset has a theoretical data rate of about 1.07 kbps, which is fine for short text messages but not for voice, photos, or web browsing. See our modem presets guide for the full table.

Meshtastic uses LoRa peer to peer, not LoRaWAN. The FAQ states plainly that Meshtastic does not use LoRaWAN and will likely not work with other LoRa services.

Managed flooding

When you send a message, your phone or computer passes it to your node over Bluetooth, Wi-Fi, Ethernet, or serial. The node then broadcasts it over LoRa. According to the Overview:

• Each node that hears a packet checks whether it has seen it before and discards duplicates.
• A new packet whose hop limit hasn’t reached zero becomes a candidate for rebroadcast.
• Nodes wait a short random delay before relaying. The delay is weighted by signal-to-noise ratio, so more distant nodes tend to relay first.
• Most nodes that hear a neighbor relay the same packet cancel their own copy. Nodes in router roles relay anyway.
• Each relay decrements the hop limit by one. The default hop limit is 3, and it can be set as high as 7.

The project calls this “managed flooding.” Since firmware 2.6, direct messages work slightly differently: once a node learns which neighbor reliably relays toward a destination, it addresses that one relay instead of flooding, and falls back to flooding if the relay doesn’t respond (Mesh Broadcast Algorithm).

Channels and keys

Nodes form a mesh only when they share the same LoRa settings (spreading factor, bandwidth, and frequency), which Meshtastic bundles into modem presets. On top of that, channels are named, encrypted groups. A node can hold up to eight channels. The default channel uses a publicly known key, so anything sent on it can be read by anyone with Meshtastic. Nodes still relay packets for channels they can’t decrypt (Overview). Our privacy and encryption guide covers this in detail.

What do you need for a Meshtastic network?

Item	Why you need it
Two or more LoRa radios with Meshtastic firmware	A mesh needs at least two nodes. Many boards ship ready to flash; see /devices/.
A region setting	A new node does not transmit until you set its region, which keeps it within local legal limits (LoRa config). In the US, that is US (902–928 MHz).
A matching modem preset	Nodes on different presets cannot hear each other at any distance.
A client app (optional but typical)	Android, Apple, web, and Python CLI clients let you read and send messages and change settings.
An antenna	The docs warn not to transmit without an antenna attached, because it can damage the radio.

If you don’t have the firmware on your radio yet, our flashing guide walks through the official Web Flasher. If you want to join people already near you, see how to find Meshtastic nodes near you.

Is a phone required?

No. The introduction lists “No phone required for mesh communication” as a feature: radios relay traffic on their own. A phone (or computer) is how most people read and write messages, though some devices have built-in screens and keyboards. Each radio supports a connection from only one client at a time, according to the introduction.

Can Meshtastic connect to the internet?

Meshtastic doesn’t require the internet, but it can use it. A node with Wi-Fi or Ethernet, or a node using a connected phone’s network through “client proxy,” can forward packets to an MQTT server. That lets separate meshes exchange messages over the internet and lets software such as home automation tools read mesh data (MQTT module docs).

MQTT is off by default, and it has privacy implications: traffic on the default channel is readable by anyone subscribed to the public server, and unless MQTT encryption is turned on, packets from any uplinked channel are sent to the broker unencrypted. Our Meshtastic MQTT guide explains the settings.

Is Meshtastic open source?

Yes. The project states it is “100% community driven and open source,” and support is volunteer based. The firmware repository’s license is the GNU General Public License v3. The licensing page notes that different software components are “released under various licenses,” so check each repository if licensing matters to you.

What is Meshtastic used for?

The official docs and blog describe these uses:

• Off-grid group messaging for hiking, skiing, biking, and other outdoor trips where cell service is unreliable. Keeping hiking buddies connected was the original goal, per the v2.5 encryption blog post.
• Community and public meshes, where many people in a city or region keep nodes on the same settings so anyone can join.
• Emergency, search and rescue, and disaster communication are mentioned by the project as uses that have grown out of the community.
• Location sharing with optional GPS, with adjustable precision per channel.
• Telemetry and sensors, such as weather or battery data, using the Sensor role and telemetry module.
• Integration with ATAK through dedicated TAK roles.

The listed features include “excellent battery life,” encrypted communication, and long range. On range, the introduction links to a documented 331 km ground-to-ground record. That figure came from two well-placed mountain sites, not typical handheld use; our Meshtastic range guide explains what affects real-world distance.

Limits worth knowing up front

• Low bandwidth. Messages are limited to roughly 200 bytes so the encoded packet fits the 239-byte payload limit (Overview).
• Shared airtime. Every node on a mesh shares one frequency. Large meshes can congest, which is why many communities move to faster presets.
• Security has limits. The docs say directly that Meshtastic is not as secure as Signal, TLS 1.3, or WPA3, because it lacks forward secrecy, among other reasons.
• No firmware updates over the mesh. The FAQ says Meshtastic does not support over-the-air updates via LoRa.
• Region rules apply. In the US, Meshtastic operates in the 902–928 MHz band; see is Meshtastic legal in the USA.

Meshtastic vs. other LoRa mesh projects

Meshtastic is not the only LoRa mesh firmware. MeshCore, for example, uses a different routing design where only dedicated repeaters relay. The two do not talk to each other on the air. See Meshtastic vs MeshCore for a side-by-side comparison, or use the finder to narrow down hardware for either.