MeshCore vs Meshtastic: which mesh network should you join?

The one thing to know first: MeshCore and Meshtastic are separate networks. Many radios can run either one, but a radio running MeshCore cannot exchange messages with a radio running Meshtastic. Everyone you want to reach must be on the same system.

So the most practical way to choose is often: which one do the people near you already use? A mesh is only as useful as the nodes around it.

What both do

Both turn small, cheap LoRa radios into a text-messaging network that needs no cell towers and no internet. Messages hop from radio to radio until they reach the recipient. Both:

• Carry short text messages and location, not voice, photos or web pages.
• Typically use the 902 to 928 MHz band in the US.
• Run on many of the same boards, such as the RAK4631, Heltec V3 and V4, and LILYGO T-Deck family.
• Usually pair with a phone app over Bluetooth, though some devices work standalone.

Neither replaces 911, cellular service or broadband. Range depends on height, terrain, antennas and how many other nodes are around.

How they differ

Routing: flood versus learned paths

MeshCore’s FAQ describes the core difference this way: Meshtastic floods every message, meaning each node rebroadcasts what it hears, while MeshCore learns paths and sends direct messages along a known route. MeshCore’s repeaters, its FAQ notes, do not repeat every packet they receive.

What that means in practice: flooding is simple and robust when the network is small and changes often. Learned routing uses airtime more efficiently as networks grow, but depends on routes staying valid.

Device roles

MeshCore uses distinct firmware roles, per its FAQ:

• Companion (Bluetooth or USB): connects to a phone or computer app as your messenger.
• Repeater: forwards packets toward their destination, usually mounted high.
• Room server: stores message history and pushes it to users who connect later.

Meshtastic devices run one firmware and take roles through configuration settings.

Standalone devices

If you want to type and read messages without a phone, look at keyboard devices like the LILYGO T-Deck Plus. MeshCore’s FAQ describes standalone T-Deck firmware, and notes that direct messaging works without paying, while map zoom and server administration need a $10 per-device unlock. The FAQ also notes the T-Deck firmware itself is not open source, unlike the core MeshCore code. Meshtastic also lists the T-Deck family as supported.

US radio settings

MeshCore’s FAQ gives its recommended USA/Canada preset as 910.525 MHz, SF7, BW62.5, CR5. Meshtastic has its own US region setting. Either way, set the region before you transmit, and buy hardware sold for the 915 MHz band. A radio built for Europe’s 868 MHz band is not a substitute.

Privacy

Do not assume your messages are private just because a protocol supports encryption. MeshCore’s FAQ publishes the key for its default public channel, which means anyone can read that channel. Treat any default or public channel on either system as public, and use private channels or direct messages for anything personal, following each project’s current documentation.

Hardware support is per board, per firmware

Support is not universal, and it changes with releases. Examples from our research:

Always check the current device list on each project’s site against your exact board and revision before buying.

How to choose

1. Ask around. Local mesh groups, ham clubs and community forums will tell you which network has nodes near you.
2. If nobody nearby runs either, you are building your own network. Pick based on what matters most:
   • Want the larger, longer-established community and app ecosystem? Meshtastic is the common starting point.
   • Want structured repeaters and room servers, and expect your network to grow? MeshCore’s design targets that.
3. Buy radios that can run both when you can. Then you can switch if your area settles on the other one.

Ready to set up radios for your household? See the family mesh messaging starter guide.