Choosing Hardware for MeshCore vs Meshtastic

MeshCore and Meshtastic are both LoRa mesh networking platforms,platforms. They run on largely the same hardware, but theydiffer havein meaningfullyfirmware differentfeatures hardwareand requirements.which boards are best suited to each role. This guide helps you decide which firmware to run based on the hardware you already own, or which hardware to buy if you are starting fresh.

The Fundamental Hardware Difference

The singlebiggest mostpractical importantdifference distinctionis not the radio chipset — both platforms support the common LoRa radios. The real constraint is the radioMCU chipset:and its flash/RAM size, which determines which firmware roles a board can run:

• Meshtastic supports the SX1276, SX1278, SX1262, and SX1268, plus the SX1280 and severalLR111x other LoRa radios.families. Its hardware support surface is broad. The vast majority of currently manufactured Meshtastic hardware uses SX126x chips, which the project recommends; SX1276/SX1278 are the older generation (see the Meshtastic devices page).
• MeshCore requiressupports both SX126x (SX1262/SX1268) and SX127x (SX1276/SX1278) radios. SX126x is preferred for new boards, but SX1276 boards such as the SX1262Heltec LoRa32 V2 and LilyGo T-Beam SX1276 are officially supported via dedicated firmware variants (orwhich SX1268)build with RADIO_CLASS=CustomSX1276). IfSee yourthe boardMeshCore hasvariants any other LoRa chipset, you cannot run MeshCore.list.

This means the decision tree starts at the radio,MCU and how much flash/RAM it has — not the MCU.radio chipset. On older ESP32 boards the limiting factor is the ESP32's flash size and RAM, not the radio.

MCU Considerations

Both platforms run on ESP32 and nRF52840 MCUs, but with different trade-offs:

MCU	MeshCore Support	Meshtastic Support	Key Advantage
nRF52840	ExcellentRuns (all MeshCore firmware types)roles (Companion, Repeater, Room Server, Sensor)	ExcellentFully supported	Hardware AES,AES (128-bit), Bluetooth 5 (BLE 5.0,0), very low sleep current (~1–3 µA)µA System ON idle; ~1.5 µA per the Nordic nRF52840 datasheet), UF2 flashing. Best for both platforms.
ESP32 (original)	Supported (nocompanion/repeater/room server; sensor firmware)builds are limited on memory-constrained 4 MB boards)	ExcellentFully supported	WiFi support (Meshtastic uses thisWiFi for MQTT bridging). Higher power draw.draw than nRF52840.
ESP32-S3	Supported (noe.g. sensorXiao firmware)S3 WIO variant)	Supported	Faster CPU, native USB. StillGenerally higher power than nRF52840.
ESP32ESP32-classic + SX1276 (before S3, originale.g. Heltec V1/V2)V2, T-Beam SX1276)	Not supportedSupported (wrongSX1276 radio)boards run MeshCore via dedicated variants)	Supported	IfSX1276 youis havesupported on both platforms; on these boards,older Meshtasticboards the constraint is yourthe onlyESP32's option.flash/RAM, not the radio. SX1276 wakes the MCU on DIO0 rather than DIO1.

If You Already Own Hardware

Use this decision guide based on what you currently have:

T-Beam v0.7 / v1.0 / v1.1 (SX1276)

RunYou Meshtastic.can run either. These boards use the SX1276 radioradio, andwhich areis incompatiblesupported withby MeshCore.both platforms. They work excellentlywell with Meshtastic.Meshtastic, Thereand they also run MeshCore via the lilygo_tbeam_SX1276 firmware build — no board replacement is no upgrade path short of replacing the board.needed.

T-Beam v1.2 or later (SX1262)

You can run either. Both platforms support this hardware. Choose MeshCore if you want path-based routing and lower channel utilization at scale.scale (this benefit applies to stable, repeated unicast traffic, not to group/broadcast or high-churn networks). Choose Meshtastic if you need WiFi/MQTT bridging, the Meshtastic app ecosystem, or channel encryption compatibility with an existing Meshtastic network.

T-Beam Supreme (ESP32-S3 + SX1262)

You can run either. Same guidance as T-Beam v1.2+. The Supreme is a newer, more capable board and works well with both. On MeshCore it runs the Companion, Repeater, and Room Server firmware variants.

Heltec WiFi LoRa 32 V1 or V2 (SX1276)

RunYou Meshtastic.can run either. The Heltec WiFi LoRa 32 V2 runs MeshCore via the heltec_v2 build (SX1276 radiois makes these incompatiblesupported, with MeshCore.a DIO0-wake hot-fix). Both V1 and V2 are fullyalso supported by Meshtastic.Meshtastic, though Meshtastic's V1 support is increasingly constrained by the board's limited flash size.

Heltec WiFi LoRa 32 V3 (ESP32-S3 + SX1262)

You can run either. The V3 is specificallya small, capable board. Because of the compatibleESP32's revision.limited Noteflash/RAM, thathosting MeshCorea doesRoom not support ROOM_SERVERServer on this board;board ifis younot needrecommended; tochoose hostan nRF52840 board (such as the RAK4631) for a room server, choose a different board.server.

RAK4631 / RAK WisBlock with SX1262

You can run either,either. butMany users consider the RAK4631 (nRF52840 + SX1262) a flagship MeshCore isboard: it runs the strongerfull choiceset here. The RAK4631 is MeshCore's gold standard hardware. It supports allof firmware typesroles, including SENSOR.Sensor, with low power draw and UF2 flashing. It is also a fully supported Meshtastic target if needed.

Heltec HT-n62

MeshCore supported (RepeaterCompanion and RoomRepeater Client only)firmware). This matches the Supported Hardware for MeshCore page. Check Meshtastic's hardware compatibility list for current support status on this board.

If You Are Buying New Hardware

If you are purchasing hardware specifically to run MeshCore, the recommendation is:

1. RAK4631 on a RAK19007 base board - best flexibility, runs all firmware types,roles, lowest power, UF2 flashing. Recommended for repeaters, room servers, and sensor nodes.
2. T-Beam Supreme - good choice if you want onboard GPS and a slightly more integrated form factor. Runs the Companion, Repeater, Room Client, and Room Server.Server firmware variants.
3. Heltec WiFi LoRa 32 V3 - smallest and cheapest option for client-onlycompanion/client or repeater-onlyrepeater nodes. NotHosting suitable fora room servers.server on it is not recommended.

Feature Comparison: MeshCore vs Meshtastic

Feature	MeshCore	Meshtastic
Routing model	Path-basedFlood-first, (learnsthen routes,learned targeteddirect relay)path	Flood-based (rebroadcast to all)
Channel utilization at scale	Lower for stable repeated unicast (targeted forwarding)	Higher (all nodes rebroadcast)
SX1276 support	NoYes (e.g. Heltec V2, T-Beam SX1276)	Yes
SX1262 support	Yes (required)	Yes
WiFi / MQTT bridging	NoWiFi client supported; MQTT bridging via community gateways (planned)not a built-in core feature)	Yes (core feature)
Room server (group chat infrastructure)	Yes (dedicated firmware)	N/A (different model)
Sensor node firmware	Yes (Simple Sensor example; typically nRF52840 boards)	Yes (broader support)
Mobile app	MeshCore app (Android/iOS)	Meshtastic app (Android/iOS)
BLE configuration	Yes	Yes
Community size	Smaller, growing	Larger, mature

Summary: Key Decision Rule

IfBoth yourMeshCore and Meshtastic run on SX1276 and SX1262 boards.
The radio chipset is rarely the deciding factor — the real constraint on older ESP32 boards is the MCU's flash/RAM size, which limits which firmware roles (especially Room Server and Sensor) a board has an SX1276 radio, you cannot run MeshCore - run Meshtastic instead.
If your board has an SX1262 radio, you can run either platform.run. Choose MeshCore for better scaling with path-basedflood-first/direct-path routing,routing on stable networks, or Meshtastic for its broader app and hardware ecosystem compatibility.maturity. For room servers and sensor nodes, an nRF52840 board such as the RAK4631 is the most capable choice.