Your Meshtastic node is on the desk, the app says a newer release is out, and you want to install it without ending up with a silent device or a node that has forgotten its channels. The short answer: the Meshtastic flasher at flasher.meshtastic.org handles most devices right in the browser, as long as you use Chrome or Edge, pick the correct firmware target and back up your configuration first. On nRF52-based devices such as the RAK4631, the last step is copying a UF2 file onto a USB drive that appears in bootloader mode.
Three things usually go wrong: the wrong firmware for the hardware, an unintended full wipe without a backup, and a device the computer never detects in the first place. Each of them is covered below with concrete steps and the limits you should know about.
Which Meshtastic firmware fits your device?
Meshtastic builds a separate firmware target for every supported piece of hardware. Two devices with the same processor can still need different files because the display, buttons, GPS or power circuitry sit on different pins. What matters is the complete product, not just the radio chip. In the web flasher you start by picking your device from the list; for a manual install, the device name is part of the file name, following the pattern firmware-DEVICE_NAME-X.X.X-xxxxxxx.uf2.
One example from our range: the WisMesh Pocket V2 RAK10709 runs on a RAK4631 WisBlock core. That helps you place it, but it does not replace checking the flasher’s device list. If the complete device has its own target there, use that one. The hardware family also decides how the firmware gets onto the device at all:
| Hardware family | Typical method | What you need |
|---|---|---|
| ESP32 | Web flasher over the USB serial connection | Chrome or Edge, possibly a USB-to-serial driver |
| nRF52 (e.g. RAK4631) | Drag and drop a UF2 file onto the bootloader drive, or Bluetooth OTA from a phone | USB data cable, bootloader mode |
| RP2040 | UF2 file onto the drive that appears when you plug in while holding BOOTSEL | USB data cable |
The table shows the key difference: on ESP32 devices the browser talks to the chip directly, while on nRF52 and RP2040 you end up copying a file onto a drive. The web flasher helps with both routes, but the procedures are not the same.
Does the Meshtastic web flasher work in every browser?
No. The flasher relies on Web Serial, a browser interface that lets a web page talk to a USB serial device. The Meshtastic documentation names Chrome or Edge as the requirement. Firefox and Safari do not offer Web Serial, so the page loads but never finds a device. If Firefox is your everyday browser, install one of the two supported browsers for the update instead of hunting for workarounds.
The first time you connect, the browser asks which serial port the page may access. The list usually shows your board’s USB-to-serial chip, not the product name. If the list is empty, the problem almost always sits below the browser: the cable, a driver, or another program already holding the port. The troubleshooting section further down walks through each of these.
For nRF52 devices the browser matters less. You can download the UF2 file from the flasher or the downloads page and then copy it with any file manager. You only need Web Serial if you want the page to send the device into bootloader mode for you.
How to back up settings before a Meshtastic firmware update
A normal update keeps your settings. Still, a config export belongs before every flash, because one wrong checkbox on the erase option is enough to reset everything. The most reliable route is the Meshtastic CLI: meshtastic --export-config > config_backup.yaml writes your configuration to a YAML file. According to the Meshtastic documentation, that export holds the entire configuration, including the public and private keys. You restore it with meshtastic --configure config_backup.yaml.
The keys are the part many people overlook. An erase and reinstall loses the public and private keys and generates new ones. Other nodes still know your old key, so encrypted direct messages only work again once everyone has picked up the new one. The documentation states plainly that backing up your keys is your responsibility. If you would rather not use the CLI, copy both keys from the app into a protected note.
Also write down the values that define your node on the mesh: region, modem preset, frequency slot, device role, channels and enabled modules. That way you spot any difference right after the update. Treat the YAML file like a password, because it contains your private key and the channel keys. If you want to share it in a forum while troubleshooting, remove those lines first.
How to flash Meshtastic on a RAK4631 with UF2
On the RAK4631 and devices built on it, such as the WisMesh Pocket V2, updates go through a UF2 file. The procedure from the Meshtastic guide: download and unzip the matching firmware, connect the device with a USB data cable and put it into bootloader mode. A new drive then mounts on your computer, on Windows, macOS and Linux as well as Android. It contains the files CURRENT.UF2, INDEX.HTM and INFO_UF2.TXT. Copy the UF2 file for your device onto that drive, wait for the copy to finish, and the device reboots and installs the firmware.
The distinction between the RAK4631 and the RAK4631-R matters here. The hardware is identical, but the R variant ships without the bootloader Meshtastic expects. Before you can copy a UF2 file onto it, the bootloader has to be changed, and the Meshtastic documentation has a separate guide for that. Check the marking on the module or your purchase records before you start.
A common mistake is choosing the file by chip instead of by device. The shield on the module reads RAK4630, which is the radio module inside. The firmware target is still rak4631, and for a finished device with its own entry in the flasher you use that device’s target. If you are unsure, open INFO_UF2.TXT on the bootloader drive: it shows which board the bootloader reports.
How do you enter bootloader (DFU) mode?
In bootloader mode, often called DFU mode, the device is not running the normal Meshtastic application but a small program that waits for new firmware. On most nRF52 devices you get there by double-pressing reset: press the reset button twice within about half a second. A single press leaves the bootloader again without flashing anything. If the double press does not work on the first try, the timing is usually the problem, not the device.
On enclosed handhelds the reset button is not always easy to reach. In that case the software route is more convenient: with the device connected over USB, meshtastic --enter-dfu sends it into bootloader mode and the drive appears. The Android app offers the same through its USB File Transfer option. Some single-button devices need their own button sequence, which the documentation describes per model; on an unfamiliar device, do not try random combinations.
On RP2040 boards you hold the BOOTSEL button while plugging in the USB cable instead. On many ESP32 boards the web flasher switches into flashing mode on its own; if it does not, holding the BOOT button while plugging in usually helps.
Meshtastic flasher not detecting your device: what to do
The most common cause is mundane: a charge-only cable. Many USB cables that come with power banks and chargers have no data lines. The device lights up and the battery charges, but the computer sees nothing. Use a cable you know has carried data before, and plug it straight into the computer rather than into a hub or a monitor port.
The second cause is a busy port. Only one program can open a serial port at a time. If the Meshtastic desktop app, the CLI, a serial monitor or a second browser tab with the flasher is still connected, the flasher cannot get access. Close everything else and reload the page.
Third, some ESP32 boards need a driver for their USB-to-serial chip, typically from Silicon Labs (CP210x) or WCH (CH340, CH9102). The Meshtastic documentation has its own section on installing serial drivers and a test page to check whether the port shows up. On Linux, missing permissions for serial devices can block access as well.
nRF52 devices have one special case: in bootloader mode a drive appears, but not necessarily a serial port. If you can see the drive, that is not an error; it is exactly the state in which you copy the UF2 file. If neither a port nor a drive appears after several clean attempts, check the model and variant, such as RAK4631 versus RAK4631-R, before digging further into drivers.
Full erase or update: when do you need to wipe the device?
An update replaces the firmware and leaves settings, keys and the node database in place. A full erase removes exactly those: settings, encryption keys, Bluetooth pairings and the node database. On nRF52 devices the bootloader and the installed firmware are left untouched, and the device then starts as if it were new. For ESP32 devices the web flasher offers the erase as an option during installation.
When do you need it? The nRF52 documentation recommends an erase before installing, because the format and location of stored data can change between releases. The release notes for version 2.8 recommend a full erase and reflash if the device bootloops or crashes repeatedly after upgrading, and advise exporting your config first. On ESP32 devices, the built-in web client at meshtastic.local is also only updated by a full wipe and reinstall.
For nRF52 devices with a current bootloader there is the file meshtastic_factory_erase.uf2. You can tell whether your bootloader supports it by a “Factory-Erase:” line in INFO_UF2.TXT. Older bootloaders need an erase file that matches the SoftDevice version. Be careful here: a mismatched erase file can overwrite part of the SoftDevice, and recovering from that may require a dedicated SWD flashing tool.
Stable, beta or alpha: which Meshtastic firmware version should you use?
Meshtastic publishes firmware at two levels of maturity. On GitHub, released versions carry the “Beta” label, and the one marked “Latest” is the current stable choice. Alpha versions are flagged as pre-releases; they bring new features sooner but with more risk. In October 2026, 2.7.26 Beta was marked “Latest,” while 2.8.1 was available as an Alpha. Two 2.8.0 builds were revoked during that period, one of them because of startup problems on a specific device.
That leads to a simple rule: for nodes other people rely on, such as a fixed router on a roof or a device you take hiking, use the version marked “Latest.” Alpha makes sense when you want to test a specific new feature and the device is always within reach. Within a group, try to stay on similar versions, because bigger jumps can change defaults. In 2.8, for example, new US nodes start with the LongTurbo preset instead of LongFast, and the two cannot hear each other.
Where can you buy Meshtastic devices?
If you are choosing a new device, the same questions that matter for flashing apply. Is the hardware listed as its own target in the web flasher, so you can find the right firmware without guessing? Is it based on ESP32, nRF52 or RP2040, and does the update route fit how you work, whether that is a browser on a computer or a UF2 file and Bluetooth OTA from a phone? Can you reach the reset button, or will an enclosed case leave you relying on the app or the CLI? With nRF52 modules it is also worth checking the exact variant, so you do not end up with a RAK4631-R and its different bootloader by surprise.
A device with a well-documented update path saves you time with every new release, and with the Meshtastic flasher and a UF2 file an update stays a matter of a few minutes. If you are looking for a suitable device, you can find our models in the Meshtastic category.
Meshtastic Firmware FAQ
Can you flash Meshtastic without a PC?
On nRF52 devices, yes. They accept firmware updates over Bluetooth from a phone, and the UF2 drive can also be mounted on an Android device with a USB cable. ESP32 devices, on the other hand, usually need a computer with Chrome or Edge, because the web flasher depends on Web Serial.
Do you lose your channels when updating Meshtastic firmware?
Not with a normal update; channels and settings are kept. A full erase, however, deletes settings, channels and keys. Make a config export before every update so you can restore everything either way.
Can you roll back Meshtastic firmware?
Yes, you flash an older version the same way you would install an update. A configuration from a newer release is not guaranteed to work with an older one, though, and some version changes require a full erase. Back up your current configuration before downgrading and check region, preset and channels afterward.