ESPConnect, reviewed: the ESP32 toolbox that lives in a browser tab

Every board drags a toolchain behind it

Every ESP32 I’ve owned has eventually demanded a toolchain. esptool and its Python venv, PlatformIO and its bottomless cache, the Arduino IDE and its driver roulette, udev rules on Linux — and the worst case of all: the board that needs rescuing while you’re sitting at a machine with none of it installed. Half the friction of working with microcontrollers isn’t the hardware. It’s the software you’re expected to keep around for the ten minutes a month you actually need it.

ESPConnect collapses that pile into a browser tab. It’s an open-source control center for ESP32-class boards that runs entirely inside a Chromium browser — no installer, no account, no backend — using Web Serial to talk straight to the chip over USB. It grew out of Jason2866’s WebSerial ESPTool, which proved you could flash an ESP32 from a page; ESPConnect turns that trick into a whole maintenance workshop.

What you get without installing anything

Point a Chromium browser at version 89 or newer (Chrome, Edge, Brave, Arc) at the app, plug the board in with a data-capable USB cable, click Connect, and grant the browser permission to the serial port. After the handshake, a drawer of tools unlocks:

Device Info — chip family, revision, MAC, flash size, crystal. More useful than it sounds once your parts drawer fills with anonymous DevKit clones.
Partitions — a graphical map plus a table of every entry with offsets, sizes, and unused flash, so you can sanity-check a layout before you flash over it.
File system — browse, upload, back up, restore, and format SPIFFS, LittleFS, or FAT partitions, with inline preview for text, JSON, images, and audio, plus usage gauges.
Apps — your OTA slots: which one is active, what’s staged next, build metadata and sizes.
Flash — flash any .bin with common offset presets and an optional full chip erase.
Console — a real serial monitor: stream output, send commands, Ctrl+C, change baud rate, reset the board.
Integrity — MD5 over any offset and length, for verifying what’s actually on the chip.

That list reads like a desktop IDE’s debug menu. It’s a web page. Nothing to install is not a gimmick here — it’s the entire value proposition.

The feature that matters: back up before you break it

Flashing gets the screenshots, but backups are why I bookmarked this thing. ESPConnect can image individual partitions, the partition table, only the used regions of flash, or arbitrary address ranges you specify — and then MD5-check any of it against what’s on the device. That enables the workflow every firmware tinkerer learns the hard way:

Image the used flash of a working device before you touch anything.
Verify the MD5 so you know the backup isn’t a beautiful copy of nothing.
Experiment. Break it. You will.
Restore, and you’re back to known-good in minutes instead of spending an evening with a serial recovery guide.

It’s also the right move the day you buy a cheap pre-flashed board — a display module, a smart-home sensor — and want to replace its firmware with your own. Image the vendor’s flash first, and your curiosity stops being a one-way door.

Where it earns its keep day to day

Most ESP32 projects end up headless, with their configuration living in a file on the flash — config.json, calibration values, thresholds. The normal edit loop is miserable: change one number, rebuild, reflash the whole firmware, hope you didn’t typo. With ESPConnect you browse the file system, pull the file down, edit it, push it back — and the app stages edits locally, so you commit with Save to Flash only when you’re satisfied. Fixing a threshold on a shelf sensor stops being a compile job.

The OTA slot view deserves a mention too. If your devices update themselves, “did the update actually take?” is a question you’ll ask eventually, and the Apps tab answers it directly — which slot is live, what’s waiting in the other one — without breaking out a serial capture rig.

No backend is a feature — and a reason to self-host

Everything happens in the browser: no backend, no account, no telemetry, and your firmware images and backups stay on your machine unless you move them. For a tool that sees the entire contents of your flash, that’s the correct architecture.

Now sit with the flip side: you’re flashing firmware from a web page. That means trusting whatever is served at that URL, for eternity. The project is MIT-licensed and publishes two builds — a stable one cut from tagged releases, and a preview built from main — and the sane default is stable for anything that touches real devices. But if this becomes part of your maintenance routine, stop depending on someone else’s GitHub Pages hosting and run it yourself:

docker build -t espconnect .
docker run --rm -p 8080:80 espconnect

Now the toolbox lives on your LAN, next to the boards it manages. A hosting hiccup — or a lapsed domain — can’t quietly turn your flashing tool into someone else’s payload loader. It’s the same instinct as self-hosting anything a small business actually depends on: pin your tools where you can see them.

The honest limits

Chromium only. Web Serial is the engine, so Firefox and Safari users are out. Fine for a bench machine you control; a limitation everywhere else.
ESP8266 is a guest, not a citizen. It connects, but partition tables, file systems, and the advanced features are ESP32-only. Don’t retire your ESP8266 workflow for this.
The NVS inspector is experimental. Reading namespaces, keys, and decoded values from the non-volatile storage partition is genuinely neat for debugging — but it’s read-only, partly reverse-engineered, and the project itself says not to treat its output as authoritative.
Physics still applies. If your board lacks auto-reset wiring, you’ll still do the manual dance: hold BOOT, tap RESET, keep holding while you click Connect, release when the ESP-ROM banner appears.
One port, one owner. Close the Arduino IDE or PlatformIO before connecting; only one application can hold the serial bridge.

And keep esptool installed anyway. If a board won’t handshake — drop to 115200 baud and replug the cable before you panic — the old-school command line is still the tool of last resort. A browser tab that works 95% of the time doesn’t replace the tool that works the other 5%.

Verdict

An ESP32 is the cheapest pair of remote hands a home lab can buy. ESPConnect is the maintenance hatch for those hands: the first time you image a working device in under two minutes before a risky flash, or fix a config file on a headless sensor without opening an IDE, it earns its bookmark. Use the stable build, self-host it once headless boards become infrastructure rather than toys — and let it build the backup habit you always meant to have. The tool makes the habit nearly free, which is exactly the point.