Guides · updated 2026-10-31

Meshtastic® vs MeshCore: which should you pick?

Meshtastic® and MeshCore are both free firmware for small LoRa radios that pass text messages along with no cell service or internet. Many radios can run either one, but a radio runs one at a time, so the real question is which network you want to join.

We haven't tested either one for this guide. We checked each project's own documentation on 2026-10-30 and 2026-10-31 and wrote the details in our own words, with links. Anything we couldn't confirm is marked "not confirmed".

The short answer

• Join whatever your local group runs. A mesh only helps if there are other radios in range running the same firmware. Find a group near you and ask before you buy.
• Meshtastic if you want the widest choice of supported radios, apps that are fully open source, and the most local groups in our directory.
• MeshCore if the people you'll message already use it, or you like its design: phones and handhelds don't relay, and dedicated repeaters carry traffic along remembered paths.
• Neither is an emergency SOS service. For that, see satellite messengers and phone satellite texting.

What each one is

Meshtastic is a community-run, open-source project that turns low-cost LoRa radios into an off-grid messaging network (Meshtastic docs). Your phone connects to your radio over Bluetooth, USB or a network connection, and the radios carry text messages and positions to each other over LoRa. The firmware is licensed GPL-3.0 (meshtastic/firmware on GitHub).

MeshCore is a LoRa mesh system for encrypted text messaging, built around a few firmware types: companion radios that pair with an app, repeaters that extend the network, and "room servers" that hold message history for people who come back later (MeshCore FAQ). The firmware is MIT-licensed (meshcore-dev/MeshCore on GitHub). The project started in January 2025, according to a MeshCore blog post.

There's a public dispute over the MeshCore name between people who worked on the project. We don't take a side. This guide cites meshcore.io, docs.meshcore.io, blog.meshcore.io and the meshcore-dev/MeshCore GitHub repo.

How messages get relayed, in plain words

Meshtastic uses what its docs call managed flooding. When a radio hears a new message, it waits a short random moment and then repeats it. Radios that hear a weaker signal wait less, so the farthest radios tend to repeat first and carry the message furthest. If a radio hears a neighbor repeat the message first, it usually drops its own copy. Every repeat uses up one hop, and once the hops run out the message stops spreading. For direct messages, once a radio learns which neighbor can reach the person you're messaging, it sends through that neighbor and goes back to flooding if that stops working (Meshtastic docs: overview).

MeshCore splits the jobs up. Radios that people carry and pair with the app don't repeat anything. Only repeaters (and room servers set to repeat) pass messages on. The first direct message to someone floods through the repeaters. The reply that confirms delivery lists the repeaters it went through, and later messages follow that path, so only the repeaters on it retransmit. If the path breaks, the app retries and then falls back to flooding to find a new one. Group channels always flood, but repeater owners can cap how far. The firmware allows up to 64 hops (MeshCore FAQ).

What that means for you: on Meshtastic, any radio can help relay unless it's set not to. On MeshCore, the network only reaches as far as its repeaters, so a MeshCore area needs someone to put up repeaters, ideally high up.

Can they talk to each other?

Treat them as two separate networks. Each project documents its own packet format, and the Meshtastic docs say radios only form a mesh with others using matching radio settings. Neither project's docs that we read describe a bridge between the two. If your friends run MeshCore and you run Meshtastic, plan on not reaching each other. You can switch a supported radio from one firmware to the other by reflashing it.

Range and battery

Range mostly comes down to the hardware, the antenna, the terrain and the radio settings, and the Meshtastic docs don't promise a single distance. They do cite a record link of 331 km, which shows what's possible in ideal conditions, not what to expect. The MeshCore FAQ says many regions have moved to "narrow" radio settings that fit between interference and send faster. Neither project gives a typical everyday range, so neither do we.

Battery: both run on the radio's own battery, so your phone can sleep while the radio stays on the mesh. The chip matters: the Meshtastic hardware docs note that nRF52-based radios use less power than ESP32-based ones (Meshtastic docs: supported hardware). MeshCore's site says its power use lets batteries last over a week on one charge (meshcore.io). That's the project's own claim, and it doesn't name the radio. We haven't found a like-for-like test of both firmwares on the same radio, so we won't say which lasts longer. Battery sizes are in our device table where makers publish them.

Which radios run them

Meshtastic supports a long list of boards from RAK, LILYGO, Seeed, Heltec, Elecrow, muzi works and others (Meshtastic docs: supported hardware). Our device table compares the ones we track.

MeshCore: these radios from our device table appear on meshcore.io or in the MeshCore FAQ's hardware list. For the full, current list, check the MeshCore web flasher.

• Pair with the app (companion): RAK WisMesh Tag, Seeed SenseCAP T1000-E, Heltec Mesh Node T114, Seeed XIAO ESP32S3 with Wio-SX1262 (meshcore.io, MeshCore FAQ). meshcore.io also lists a RAK WisMesh Pocket but doesn't say which version, so check the flasher for your model.
• Repeater: Seeed SenseCAP Solar Node P1 Pro (meshcore.io).
• No phone needed (standalone): LILYGO T-Deck Plus, T-Deck Pro and T-Lora Pager (meshcore.io). The T-Deck Pro comes in more than one version, so check the flasher for yours.

The Meshtastic supported-hardware docs list every radio named above too. Prices and specs for all of them are in our device table.

Buy the right band. In the US that's 915 MHz, whichever firmware you choose. MeshCore supports the 868 MHz range (UK/EU) and the 915 MHz range (US, Australia, New Zealand), per its FAQ.

Apps and cost

Meshtastic has free apps for Android and for iPhone, iPad, Mac, Apple Watch and Vision Pro (Meshtastic docs: Android, Apple). Radios with a keyboard and screen, like the T-Deck and T-Lora Pager, can be used without a phone (Meshtastic docs: T-Deck, T-Lora Pager). Version details are on our mesh apps page.

MeshCore has a free app for Android, iOS, Windows, Mac, Linux and the web (meshcore.io). The Android listing on Google Play (checked 2026-10-31) names Liam Cottle as the developer, shows in-app purchases, and says you need a supported radio flashed with MeshCore companion firmware, paired over Bluetooth. It's also on the App Store. According to the MeshCore FAQ:

• The radio firmware is free and open source.
• The phone apps and the standalone T-Deck firmware are free to use but not open source.
• Paid unlocks are optional extras. On the phone apps, a purchase removes a wait timer on managing repeaters remotely. On the T-Deck, a paid key adds deeper map zoom and remote admin. Basic messaging needs neither.
• The Windows and Mac apps are fully unlocked.

Community size

Meshtastic: our US groups directory lists 116 local mesh groups, and almost all of them are Meshtastic groups. Part of the reason is that we built it from the Meshtastic list of local groups, so it undercounts MeshCore. Not confirmed: total Meshtastic user or node counts, since we haven't found a figure from a source we can cite.

MeshCore: a MeshCore blog post from April 2026 said the project's map showed more than 38,000 nodes worldwide and its app had more than 100,000 active users. Those are the project's own figures. The Google Play listing showed 100K+ downloads on 2026-10-31. meshcore.io links to these community channels, which need an account: Discord, Reddit, Facebook, Mastodon and X, plus a node map. We haven't found a MeshCore list of local groups.

The best test is local: ask your nearest group what people actually run.

Side by side

FAQ

Can a Meshtastic radio message a MeshCore radio?

Plan on no. Each project uses its own packet format, and neither project's docs that we read describe a bridge, so pick the one the people you want to reach are using.

Can I switch my radio from one to the other?

If both projects support your model, yes. You reflash it, for example with the MeshCore web flasher. Check both projects' hardware lists first.

Do I need repeaters for MeshCore?

For anything past direct radio range, yes. MeshCore radios that pair with the app don't relay, so messages only travel further through repeaters. The MeshCore FAQ suggests putting a repeater high above the ground.

Does either one cost money?

Not to get started. The Meshtastic apps are free. The MeshCore apps are free too, with optional paid unlocks for extra features. You still have to buy the radio either way.

Is either one an emergency SOS service?

No. Neither connects to rescuers. If you need SOS, compare satellite messengers or check whether your phone can text by satellite.

Do I need a phone?

Usually yes. Most radios pair with a phone app. Radios with their own keyboard and screen, like the LILYGO T-Deck and T-Lora Pager, can send messages without a phone on either firmware.

Sources

• Meshtastic docs: introduction, overview, supported hardware and the Apple and Android app pages, checked 2026-10-30 and 2026-10-31.
• Meshtastic firmware license: meshtastic/firmware (GPL-3.0), checked 2026-10-31.
• MeshCore: meshcore.io, MeshCore FAQ, MeshCore blog (April 2026) and meshcore-dev/MeshCore (MIT), checked 2026-10-31.
• MeshCore Android app: Google Play listing, checked 2026-10-31.

Meshtastic® is a registered trademark of Meshtastic LLC. MeshCompare is not affiliated with or endorsed by the Meshtastic or MeshCore projects.