Meshtastic vs MeshCore: which LoRa mesh should you use?

Both projects are open source firmware for LoRa radio boards such as the Heltec V3, and many of the same boards can run either one. The difference is in the network design, and that design decides how each behaves once a few dozen nodes share a city.

How routing differs

Meshtastic broadcasts use managed flooding. A node that hears a packet waits briefly and cancels its own rebroadcast if it hears someone else rebroadcast first, and nodes with weaker signal tend to go first. The default hop limit is 3 and the docs say "really, 3 is fine". Since firmware 2.6 direct messages switch to next-hop routing after the first delivery and fall back to flooding. See roles explained for which nodes rebroadcast.

MeshCore's FAQ describes the opposite habit: its repeaters "do not forward or retransmit every packet" they receive. The first message to a contact floods. The reply carries back the list of repeaters used, the sender stores it as a direct path, and later messages carry that path. A repeater retransmits only if its own hash matches the next hop. If the path breaks, the app retries and then floods again.

The trade-off is real. Path routing can cut airtime on a large network, and the MeshCore FAQ presents that as a way to avoid congestion and collisions. It also depends on repeaters being placed well and staying up. Flooding is simpler and survives a missing node with no planning, but every extra rebroadcaster uses shared airtime.

Range

Neither project changes the physics. Both use LoRa radios, so antenna height, line of sight and the spreading factor set the link distance. The MeshCore FAQ gives no range figures, and the Meshtastic docs do not promise one either. Use the range calculator for either.

Where they differ is network reach. MeshCore allows far more hops than Meshtastic's default 3 to 7, which suits long chains of fixed repeaters on hills. Meshtastic networks stay shallow on purpose, because flooded traffic grows with every hop.

Devices and setup

Both flash from a browser. Meshtastic uses the web flasher; MeshCore has its own at flasher.meshcore.io. The MeshCore FAQ lists these among supported boards: Heltec V3 and V4, Heltec T114, RAK4631, LilyGo T-Deck and T-Pager, Seeed T1000-E and Station G2. Meshtastic supports a longer list; see our device list.

MeshCore splits firmware by job: BLE companion, USB companion, repeater and room server. A room server acts like a bulletin board and delivers up to 32 stored messages on login. Meshtastic has one firmware per board and uses device roles in the settings.

Features you may miss

Meshtastic has built-in position sharing, telemetry, the Meshtastic map and an MQTT bridge. The MeshCore FAQ describes a text-first system for messaging, emergency use and sensors, with a map at map.meshcore.io. If you want to track people on a hike, Meshtastic has the more complete feature set today.

On privacy, Meshtastic channels use AES with a pre-shared key and the default key is public, so see channels and encryption. MeshCore says adverts are signed and message payloads are encrypted; its FAQ does not state the cipher.

Community and risk

Meshtastic has the larger user base and a lot of public nodes in cities, which matters if you only buy one device and hope to find a mesh. MeshCore networks are growing city by city, and you may need to check your area on its map before you buy. A smaller network means less coverage, but also less noise. You can run both: a board can only run one firmware at a time, but nothing stops you owning two.