Why not publish a dedicated project?

Frequent testing

Give prototype or beta testers one link to revisit after every release.

Teaching and workshops

Let a class or workshop flash the prepared firmware without distributing BIN files.

Small-batch updates

Update a handful of devices without walking each user through downloads and tools.

Sending files

Send a new BIN and instructions every time, then help each person confirm they chose the right version.

Sharing one link

Change the current release once. Everyone returns to the same page and flashes that version.

Simple workflow

Publish once, then keep the same link

  1. 01

    Create a public project

    Add a name, short description, and project URL.

  2. 02

    Upload the current firmware

    Upload a tested merged BIN and mark the ready version as current.

  3. 03

    Share the project link

    Future version changes appear at the same URL—no need to resend files.

Participant experience:Open link → connect USB → flash

What to know before registering

Note: This feature is best suited to testing, teaching, and small-scale projects, rather than long-term updates for large device fleets.

Only the publisher needs an account. The public flashing page remains open to participants.

  • Free Beta: 1 project, unlimited versions, and 100 MB total storage.
  • Firmware is shared publicly and each .bin file must be 16 MiB or smaller.
  • Use a tested merged BIN from 0x0000; flashing requires desktop Chrome or Edge.

Useful for your next test or class?

Create a publisher account when you are ready. For one-off local flashing, the homepage still works without registration.

Powered by esptool-js & WebSerial API v2.5.1