Skip to content

Search guides, devices and posts

Back to Meshtastic

Meshtastic Web Flasher and Firmware Updates

Meshtastic installs from a web page or straight from the phone app. Update when a release fixes something you need. If your mesh is working, there's no rush.

This guide covers the web flasher, updating over the air, what an update keeps and what an erase wipes, backing up your keys, moving to 2.8, and recovering a flash that went wrong.

Checked October 2026 against Meshtastic 2.7.26 (stable) and Meshtastic 2.8.1 (alpha).

Current Firmware

The current stable release is 2.7.26, and 2.8.2 is the newest alpha. Our release tracker lists every build, what changed, which ones were pulled, and which we'd run.

Stable

Tested releases, and what almost everyone should run. GitHub names these releases "Beta", and the flasher lists the channel as Stable (or Beta).

Alpha

Previews of the next release, with new features and new bugs. Builds that turn out broken are marked "Revoked" on GitHub; never leave a node on one. The tracker flags them.

How to check your current version

  • Android: the Firmware Update screen shows it under Currently Installed. It's also on the node's detail page and the Connections screen.
  • iPhone and iPad: Settings, then Firmware Updates, shows the version on your radio and the latest stable release.
  • Computer: meshtastic --info prints a Metadata block with firmwareVersion.

How to Use the Meshtastic Web Flasher

flasher.meshtastic.org needs a browser with Web Serial; the flasher itself asks for Chrome or Edge. Back up your configuration first (see below).

  1. Plug in and open the flasher

    Open flasher.meshtastic.org in Chrome or Edge on a computer and plug the device in with a USB cable that carries data, not a charge-only one.

  2. Select Target Device

    Pick your board under Select Target Device, or press Auto-detect if the device already runs Meshtastic.

  3. Choose the firmware

    Pick a release. Stable (or Beta) is the tested channel; Unstable (Alpha) is the preview. You can also load a release file you downloaded.

  4. Press Flash

    Flash opens a dialog with the steps for your chip: Update or Erase Flash and Install on ESP32 boards, or a UF2 file to copy for nRF52 and RP2040 boards.

ESP32 boards (Heltec, T-Beam, Station G2)

  • Leave Full Erase and Install off and press Update to keep your settings.
  • Turn it on and the button becomes Erase Flash and Install, which wipes the device first. The flasher warns you to back up the public and private keys before doing this.
  • If the board isn't detected, try the 1200bps Reset button. On ESP32-S3 boards you may need to power off, then hold BOOT (or USR) while plugging in.
  • If flashing is unreliable, pick a lower baud rate; 115200 is slower but can be more reliable.

nRF52 and RP2040 boards (RAK, T-Echo, T1000-E, Pico)

  • Press Enter DFU Mode. The board reappears as a USB drive.
  • Press Download UF2 and copy the file onto that drive. The board reboots into the new firmware on its own.
  • Manual DFU mode: double-press reset quickly on nRF52, or hold BOOTSEL while plugging in an RP2040.
  • A copied UF2 doesn't erase your settings. The trash-can icon next to Flash erases the board instead.

Meshtastic OTA Updates

Over-the-air updates go over Bluetooth or Wi-Fi from a phone or computer nearby. There's no update over LoRa, so a node on a tower still needs someone within Bluetooth or Wi-Fi range.

BoardHowWhere
nRF52BluetoothAndroid app: Advanced, then Firmware Update (only shown for radios that support it). iPhone app: Settings, then Firmware Updates.
ESP32BluetoothiPhone app: Settings, then Firmware Updates.
ESP32 on Wi-FiWi-FiAndroid app connected over the network, or meshtastic --host <ip> --ota-update firmware.bin (firmware 2.7.18 or newer).

Before an OTA update

Meshtastic's docs warn that a failed OTA update can leave the device not working until someone gets physical access to it. Charge the battery above half, stay close, keep the app open, and update the app itself first. ESP32 OTA needs the OTA loader that the web flasher's Update installs, so a board last flashed some other way may need one USB update first. Older T-Echo bootloaders can't do OTA.

If the update stalls

On Android, the app waits up to 60 seconds after writing for the radio to come back. If it still hasn't ("Verification timed out"), power-cycle the radio and check Currently Installed before trying again. If the radio won't boot, connect it to a computer and flash it over USB.

What an Update Keeps, and How to Back Up

A normal update keeps your settings, channels and keys. A full erase removes settings, keys, Bluetooth pairings and the node list, and the node makes new keys. Since your private key is what other nodes know you by, back it up before any erase.

Android

Settings, then Backup & Restore, then Export configuration. The Security screen also has Backup Keys.

iPhone and iPad

Export Device Configuration saves a .cfg file. It contains your private and admin keys, channel keys and passwords, so keep it private.

Computer

meshtastic --export-config > backup.yaml saves everything, including the private key. meshtastic --configure backup.yaml restores it.

Upgrading from 2.7 to 2.8

2.8 is a bigger jump than most releases. Read what changes in 2.8 first. The parts that matter while updating:

  • Back up, and expect to reconfigure. The settings file format changed. Meshtastic's advice: if the node bootloops after upgrading, do a full erase and flash, then restore your configuration.
  • Your node gets a new ID, because 2.8 derives it from the public key.
  • Position sharing turns off on public channels, and telemetry broadcasts turn off, until you turn them back on.
  • Update the app too, before or with the firmware.
  • Skip 2.8.0. Both 2.8.0 builds were revoked.
  • New US nodes set up from the device's screen or the current Android app start on LongTurbo, which can't hear LongFast meshes. How to check and switch back.

2.7 and 2.8 nodes talk to each other, so you don't have to move the whole mesh at once.

Troubleshooting a Failed Flash

The flasher doesn't see the device

Try a cable you know carries data, and plug straight into the computer. Close anything else using the port (another tab, the Meshtastic desktop client, a serial monitor). Some ESP32 boards use a USB chip that needs a driver: Meshtastic lists CP210X and CH9102 (CH34x) drivers for Windows, macOS and Linux, and suggests a reboot after installing. nRF52 and RP2040 boards need no driver.

Permission denied on Linux

Add your user to the serial group, then log out and back in (on Arch the group is uucp):

sudo usermod -a -G dialout $USER

The device bootloops or won't start after an update

Check you flashed the right target; similar boards need different builds. On ESP32, flash again with Erase Flash and Install, then restore your backup. On nRF52, stale data from an older version can cause crash loops; a factory erase clears it (next card).

Erasing an nRF52 board

Enter DFU mode and open INFO_UF2.TXT on the drive. If it has a Factory-Erase: line (OTAFIX bootloader 2.4 or newer), copy meshtastic_factory_erase.uf2 onto the drive. If not, use the erase file from the firmware release that matches your SoftDevice version (S140 6.1.0 or 7.3.0), then run meshtastic --noproto so the erase can finish ("Formatting... Done"). The wrong file can leave the board needing a hardware programmer, so check before copying. Then flash the firmware again.

Flashing from the command line

The meshtastic CLI doesn't flash over USB. Each ESP32 release zip includes device-install.sh (a fresh install from the .factory.bin) and device-update.sh (an update), which run esptool for you. For nRF52 and RP2040, copy the UF2 file. meshtastic --enter-dfu puts an nRF52 board into DFU mode without touching the reset button.

Meshtastic Firmware FAQ

How do I update Meshtastic firmware?

Use the web flasher at flasher.meshtastic.org in Chrome or Edge with the device on USB: choose the device, choose a Stable release and press Flash. On ESP32 boards choose Update to keep your settings. Many boards can also update over Bluetooth from the Meshtastic app (Android: Advanced, then Firmware Update; iPhone: Settings, then Firmware Updates).

Does a Meshtastic update erase my settings?

A normal update keeps them. On ESP32, Update writes only the firmware; Erase Flash and Install wipes everything first. On nRF52 and RP2040, copying a new UF2 file doesn't erase stored data. A full erase removes settings, keys, Bluetooth pairings and the node list, so back up your configuration and keys before one.

Can Meshtastic update over the air?

Yes, over Bluetooth or Wi-Fi, never over LoRa. nRF52 boards update over Bluetooth from the Meshtastic apps (or Nordic's nRF tools). ESP32 boards update over Bluetooth from the iPhone app, or over Wi-Fi from the Android app when connected over the network, or from a computer with the CLI's --ota-update option.

Can the Meshtastic Python CLI flash firmware?

Not over USB. The meshtastic CLI has no flash command. For USB flashing without a browser, use the device-install.sh and device-update.sh scripts that come in each ESP32 release (they use esptool), or copy a UF2 file on nRF52 and RP2040 boards. The CLI can start a Wi-Fi OTA update on ESP32 (--ota-update) and put an nRF52 board into DFU mode (--enter-dfu).

Should I update to Meshtastic 2.8?

Only if you need it while it's an alpha. 2.8 gives nodes a new node ID, turns position sharing off on public channels and telemetry broadcasts off everywhere, and changed the settings file format, so back up and expect to reconfigure. 2.7 and 2.8 nodes talk to each other.

Can I switch between Meshtastic and MeshCore?

Yes, on most boards. Flash MeshCore at flasher.meshcore.io and Meshtastic at flasher.meshtastic.org, as often as you like. Identity, contacts and settings don't carry over between them.