What Meshtastic firmware version should I run?

Always Run Stable Releases on Infrastructure

Meshtastic releases three types of firmware builds:

Version numbers below are illustrative examples only. Firmware versions change frequently - always check the official Meshtastic releases page for the current stable and beta versions (examples shown reflect the 2.x release line as of 2026).

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 - the 1.x and 2.x lines use different protocol and encryption defaults and are effectively incompatible on the same mesh.

Public Key Cryptography (PKC/PKI) Direct Messaging was introduced in firmware 2.5.0 and requires both nodes to run 2.5.0 or newer for public-key-encrypted DMs. Channel messages still work across 2.x versions regardless; only direct messages between nodes that 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