What Is MeshCore? The LoRa Mesh Protocol Taking On Meshtastic in 2026

TL;DR: MeshCore is open-source mesh networking firmware for LoRa radios that takes a fundamentally different approach to routing than Meshtastic. Instead of flooding every message through every node, MeshCore floods once to discover a path, then sends future messages directly along that learned route. The result: less airtime congestion, better behavior in dense networks, and support for up to 64 hops. It runs on much of the same hardware as Meshtastic (including the T-Beam), and you can flash it from your browser in under a minute.

---

What MeshCore Actually Is

MeshCore is firmware you flash onto LoRa radio hardware to create a mesh network for off-grid text messaging, GPS sharing, and sensor data. If that sounds like Meshtastic, it should. Both projects solve the same core problem: communication without cell towers, WiFi, or subscriptions.

The difference is architectural.

Meshtastic uses managed flooding. When you send a message, every node that hears it rebroadcasts it. Every node that hears the rebroadcast rebroadcasts again. This continues up to 3 hops (configurable to 7). It works well for small networks. It gets noisy in dense ones.

MeshCore uses hybrid routing. The first message to a new destination floods through the network, just like Meshtastic. But when that message arrives, the destination node learns the path it traveled. It sends a path-return packet back along that same route. Now both nodes know the direct path between them. Every subsequent message skips the flood entirely and hops directly from node to node along the learned route.

MeshCore was created by Scott Powell of Ripple Radios (UK), with Andy Kirby as founder and Liam Cottle building the companion apps. The core firmware is MIT licensed and open source. Some device firmware and the official mobile apps are not. As of early 2026, the GitHub repo has thousands of stars and active development, with new releases landing regularly.

How MeshCore Routing Works (The Technical Version)

Three concepts to understand.

Flood Discovery

When Node A wants to message Node C for the first time and has no known route, it broadcasts a flood packet. Every repeater in range picks it up and rebroadcasts. The packet propagates through the mesh until it reaches Node C. This is similar to how Meshtastic handles every message, but MeshCore only does this once per unknown destination.

Path Learning

When Node C receives that flood packet, the packet carries metadata about which repeaters it passed through. Node C extracts that path information. It now knows: "To reach Node A, go through Repeater 7, then Repeater 3." Node C sends a path-return packet back along that exact route. Node A receives it and stores the path in its contact database.

Direct Routing

Now that both nodes know the path, all future messages between them use direct routing. The packet includes the full hop sequence. Each repeater checks if it's the next hop, strips itself from the path, and forwards to the next one. No flooding. No unnecessary rebroadcasts. Minimal airtime consumed.

This is the core advantage. In a network with 200 nodes, a Meshtastic message might trigger rebroadcasts from dozens of nodes that have nothing to do with the conversation. A MeshCore message after path discovery touches only the repeaters on the direct route.

The Tradeoff

Path learning requires that the route stays stable. If a repeater goes offline or moves, the learned path breaks. MeshCore falls back to flood discovery when a direct route fails, so messages still get through. But in highly dynamic networks where nodes constantly move (think: a hiking group where everyone is walking different directions), the path learning advantage diminishes because routes keep breaking and re-flooding.

MeshCore Node Types

MeshCore defines clear roles for devices on the network. This is a deliberate design choice that differs from Meshtastic, where every client node is also a relay by default.

Companion

Your personal device. Connects to your phone via Bluetooth (or USB serial). Sends and receives messages through the mesh. Critically, companion nodes do not repeat packets for other users. This is the biggest philosophical difference from Meshtastic. In MeshCore, your handheld radio is an endpoint, not infrastructure.

Repeater

A fixed (or semi-fixed) node whose only job is forwarding packets between other nodes. Repeaters are the backbone of a MeshCore network. You place them strategically on rooftops, hilltops, or elevated locations. They run lean, no phone pairing needed, no display required.

Room Server

A store-and-forward message board. Think of it as a BBS node on the mesh. Users can post messages to a room server, and other users can retrieve them later, even if they weren't online at the time. This is native to MeshCore. Meshtastic has store-and-forward capabilities, but MeshCore's room server concept is more deliberate and central to the architecture.

Why This Matters

Meshtastic defaults every node to "Client" mode, which means every device helps with routing. More nodes generally means better coverage, but also more airtime congestion from rebroadcasts. MeshCore separates infrastructure (repeaters) from endpoints (companions). This gives network builders more control over how packets flow, at the cost of requiring intentional repeater placement.

How MeshCore Compares to Meshtastic

Meshtastic floods every message through every node, which is simple and works well for small ad-hoc groups. MeshCore floods once, learns the path, then routes directly, which holds up better in dense networks but needs planned repeaters.

Read the full comparison: Meshtastic vs MeshCore

Compatible Hardware

MeshCore runs on many of the same boards as Meshtastic. If you already own LoRa hardware, there's a good chance you can flash MeshCore onto it today.

Recommended Boards

Our Picks

The LILYGO T-Beam is the workhorse. Built-in GPS, 18650 battery holder, and first-class support in both MeshCore and Meshtastic. Flash one firmware today, switch to the other tomorrow. It's the board we recommend for anyone entering the LoRa mesh space, regardless of which firmware you choose.

Every LoRa board we stock is in the Meshtastic collection.

A Note on Hardware Lock-In

There is none. MeshCore and Meshtastic run on the same physical radios. Flashing between them takes a minute via web flasher. Buy the hardware that fits your needs. Firmware is a software choice you can change any time.

How to Flash MeshCore

The process is straightforward. No compiling, no IDE, no command line.

What You Need

• A supported LoRa board (T-Beam, Heltec V3, etc.)
• A USB-C data cable (not a charge-only cable, this catches people every time)
• Chrome, Edge, or another Chromium-based browser (WebSerial support required)

Steps

1. Open the web flasher. Navigate to flasher.meshcore.co.uk in Chrome.
2. Connect your board. Plug it into your computer via USB-C.
3. Select your device. Choose your exact hardware variant from the dropdown. For the T-Beam, make sure you pick the right LoRa chip variant (SX1262 or SX1276).
4. Select the firmware type. For a phone-paired handheld node, choose "Companion Radio BLE." For a standalone relay, choose "Repeater."
5. Click Flash. The flasher writes the firmware. Takes about 30-60 seconds.
6. Pair your phone. Download the MeshCore app (Android, iOS, or web). Connect to your node via Bluetooth.

That's it. You're on the mesh.

If You're Coming From Meshtastic

Flashing MeshCore overwrites the Meshtastic firmware entirely. Your Meshtastic configuration, channels, and contacts won't carry over. MeshCore and Meshtastic are separate protocols and cannot communicate with each other. Nodes running MeshCore only talk to other MeshCore nodes.

You can always flash back to Meshtastic using flasher.meshtastic.org. The hardware doesn't care. It's just firmware.

Who Should Use MeshCore (And Who Shouldn't)

MeshCore is a great fit if you:

• Are building a planned mesh network with fixed repeater infrastructure
• Need a network that handles high node density (100+ nodes in a metro area)
• Want store-and-forward messaging as a first-class feature
• Prefer explicit network architecture over ad-hoc auto-organizing
• Are comfortable with a younger ecosystem that's evolving quickly
• Want to contribute to an early-stage open source project where your input shapes the roadmap

Stick with Meshtastic if you:

• Want the largest possible community and local networks to join
• Need plug-and-play simplicity with minimal infrastructure planning
• Rely on telemetry modules (environment sensors, device metrics, MQTT bridging)
• Want the most mature documentation and troubleshooting resources
• Are deploying in a group where everyone carries a node and you need ad-hoc coverage

The "Both" Option

Many mesh enthusiasts run both. A Meshtastic node for compatibility with their local community network, and a MeshCore node to experiment with the newer protocol. Since the hardware is the same, you can even alternate firmware on a single board depending on the situation. Flash MeshCore for a planned deployment on Saturday, flash Meshtastic for a hiking trip on Sunday.

If you own a T-Beam, you already have the hardware for both.

Things to Build With MeshCore

MeshCore is firmware, but the real question is always: what can you do with it?

• Neighborhood emergency mesh. Place solar-powered repeaters on three rooftops. Every house in range can send texts during a grid-down event. MeshCore's room server means messages persist even if your neighbor's node was offline when you sent it.
• Event coordination network. Set up repeaters around a festival or campground. Companions for every coordinator. The direct routing keeps the channel clean even with 50+ active users, something that would stress a Meshtastic flood network.
• Off-grid property monitoring. Put a repeater with a sensor at a remote cabin. Messages relay through intermediate repeaters to your home node. MeshCore's 64-hop limit means you can chain repeaters across surprisingly long distances.
• City-scale mesh experiment. Recruit 20 friends, place repeaters on apartment roofs across town, and build a MeshCore network that covers an entire metro area. Track coverage, measure hop performance, map dead zones. This is the kind of project where MeshCore's architecture really shines compared to flood routing.

Already running Meshtastic? Read our complete Meshtastic guide for the full picture on both protocols. Ready to build? The LILYGO T-Beam runs both firmwares.

Frequently Asked Questions

Is MeshCore free?

The core firmware is free and open source under the MIT license. Some device firmware and the official mobile apps are not open source, but they are free to download and use. There are no subscription fees or recurring costs.

Can MeshCore and Meshtastic nodes talk to each other?

No. They are separate protocols with different packet formats and routing logic. A MeshCore node can only communicate with other MeshCore nodes. A Meshtastic node can only communicate with other Meshtastic nodes. You cannot mix them on the same network.

What range can I expect with MeshCore?

The same range as Meshtastic on identical hardware. Both use LoRa radio, and range is determined by antenna quality, height, line of sight, and transmit power, not the firmware. Expect 1-5 km in urban environments and 10-30+ km with line of sight and good antennas. The difference is that MeshCore supports up to 64 hops, so your effective network coverage can extend much farther through chained repeaters.

Do I need to set up repeaters, or can I just use companion nodes?

You need repeaters. This is a fundamental design difference from Meshtastic. MeshCore companion nodes do not relay packets for other users. If two companion nodes are out of direct range, they need at least one repeater between them to communicate. For a functional network, plan on deploying dedicated repeater nodes at elevated locations.

Can I flash MeshCore on my existing Meshtastic hardware?

Almost certainly yes. MeshCore supports the T-Beam, T-Beam Supreme, Heltec V3, Heltec V4, RAK WisBlock, T-Deck Plus, Station G2, and Seeed T1000-E, among others. Use the web flasher to check if your specific board is listed. Flashing takes under a minute and you can always flash back to Meshtastic.

Is MeshCore more secure than Meshtastic?

MeshCore uses AES-256-CTR encryption with Ed25519 identity keys and ECDH key exchange for direct messages between nodes. Meshtastic uses AES-256 with channel-based keys and PKC (public key cryptography) for direct messages. Both provide solid encryption for their use cases. Neither should be considered military-grade secure. For most mesh networking scenarios (hiking, emergency prep, community networks), both are more than adequate.