What Meshtastic firmware version should I run?

Always Run Stable Releases on Infrastructure

Meshtastic releases three types of firmware builds:

Build Type	Stability	Use for
Stable (e.g., 2.3.14)	High	All production nodes and community repeaters
Beta (e.g., 2.3.15.beta1)	Medium	Personal testing nodes only
Alpha / Nightly	Low	Developers only; may have breaking bugs

Version Compatibility

Meshtastic maintains backward compatibility within a major version (2.x). All 2.x nodes can communicate with each other, though newer firmware may use packet formats that older firmware ignores. Avoid running 1.x firmware anywhere on an active 2.x network - it is not compatible.

ThePublic PKIKey Cryptography (PKC/PKI) Direct Messaging featurewas introduced in firmware 2.35.0 and requires both nodes to run 2.3+5.0 or newer for public-key-encrypted DMs. MixedChannel networks (some 2.2, some 2.3)messages still work foracross channel2.x messages;versions regardless; only DMsdirect messages between 2.3+ nodes getthat are both on 2.5.0+ (and have exchanged keys) receive PKI encryption. DMs to or from devices on 2.4.3 or older firmware are not protected by PKI.

Checking Your Current Version

In the Meshtastic app: Settings → About, or check the device info screen. Via CLI:

meshtastic --info | grep Firmware

Upgrading a Community Network

For coordinated community upgrades across multiple repeaters:

1. Announce the planned update in your community communication channel
2. Update one non-critical repeater first and test for 48-72 hours
3. If no issues, update remaining repeaters in off-peak hours (late night)
4. Document firmware versions for each node in your network inventory