Software
Flash Meshtastic
Flash firmware onto a LoRa board, set your region and send a first message.
- Difficulty
- Beginner
- Time
- 30 min
- Cost
- Free (software); you need a board, see the hardware guide
Updated 29 Oct 2026
Overview
Meshtastic is a LoRa mesh messaging system: short text messages, positions and telemetry, with no internet or phone signal needed. It does not carry web traffic. This guide takes a freshly bought board to a first message. It assumes an ESP32 board such as a Heltec WiFi LoRa 32 V3 or V4; see the Hardware buyer's guide for choosing one.
You need a board (868 MHz variant), an antenna, a data-capable USB-C cable, and a laptop with Chrome or Edge. No SD card is needed.
Before you start
- Check the cable. If the board does not appear when you plug it in, try another cable. Charge-only cables are common.
- Drivers (ESP32 boards only). Some computers need a USB-serial driver; Meshtastic names CP210x and CH340. The Heltec V3 has a CP2102 chip. The V4 dropped it and uses native USB, so the driver advice is V3-only. nRF52 boards use a UF2 bootloader and need no serial drivers.
- Know your exact board. Meshtastic's firmware files are named per board (for example
firmware-heltec-v4-...), so choose V3 or V4 carefully. - Existing config. If the board already ran Meshtastic and you plan a full erase, export its configuration first.
Flash the firmware
The Meshtastic docs recommend the web flasher for ESP32 boards, and say it requires Chrome or Edge. The flasher page is built with JavaScript and we could not read its layout, so button labels may differ slightly from the outline below. Follow the on-screen prompts.
- Fit the antenna.
- Connect the board to the laptop with the USB-C cable.
- Open flasher.meshtastic.org in Chrome or Edge.
- Select your exact device from the list.
- Choose a firmware version. If unsure, pick the stable release the flasher suggests.
- Connect to the board when the browser asks which serial port to use, and start the flash.
- Wait until the flasher reports completion, then leave the board connected.
If the web flasher will not work, the docs list a command-line script and an external serial adapter as fallbacks. nRF52 boards (RAK4631, T114, T1000-E) flash differently from ESP32 boards; we did not source those steps, so follow Meshtastic's device page for your board.
Set the region to EU_868
Do this immediately after flashing, before you send anything over the air.
- Connect to the board with an app (see below).
- Open the LoRa settings and set Region to
EU_868. - Save and let the board reboot.
Connect and send a first message
There are three ways to connect. Meshtastic's apps are Android, Apple (iOS), a web client and a Python command-line tool.
| Method | Use it for | Notes |
|---|---|---|
| Bluetooth (BLE) | Phone app: everyday use | Pair in the Android or iOS app |
| USB serial | Laptop, first setup | Web client at client.meshtastic.org (Web Serial, Chromium); the least widely supported route |
| Wi-Fi / HTTP | Laptop or phone on the same network | ESP32 only; the hosted web client needs HTTPS, so you must trust the node's self-signed certificate |
A simple first run on a laptop:
- Open client.meshtastic.org in Chrome or Edge.
- Choose a USB serial connection and select the board.
- Set the region (above), then give the node a name if the app prompts you.
- Send a message on the default channel.
A single node cannot talk to anything. You need a second node in range, or another person's node, to see a reply. Use Find a local mesh to check what is near you. For app details see Clients and apps.
Next steps
- Mount the node high with a clear view: Antenna placement and Power.
- Understand what the mesh does with your messages: How mesh routing works.
- Know the limits: What you can actually do.
- Trying a different network instead? See Flash MeshCore or RNode and Reticulum setup.
Not covered
We have not confirmed the exact web flasher button labels, the Bluetooth pairing prompts, or the nRF52 flashing procedure. Meshtastic's public MQTT broker exists but needs a node with Wi-Fi or Ethernet, and traffic from it does not propagate through local meshes, so it is not a substitute for RF coverage.