[{"data":1,"prerenderedAt":782},["ShallowReactive",2],{"post-esp-web-tools-flash-esp32-from-browser-en":3,"related-posts-esp-web-tools-flash-esp32-from-browser-en":726,"related-categories-esp-web-tools-flash-esp32-from-browser-en":754,"blog-project-detail-card-gizmo-ticker-en":773},{"id":4,"title":5,"author":6,"authorImageUrl":7,"authorUrl":8,"body":9,"categorySlug":686,"categoryText":687,"dateModified":688,"datePublished":688,"description":689,"extension":690,"faqs":691,"image":710,"imageAlt":711,"language":712,"meta":713,"navigation":714,"path":715,"seo":716,"sitemap":717,"stem":718,"summary":719,"tags":720,"__hash__":725},"blog\u002Fblog\u002Fesp-web-tools-flash-esp32-from-browser.md","ESP Web Tools: Flash an ESP32 From Your Browser","Mauro Brambilla","\u002Fimages\u002Fauthors\u002Fbruma.jpg","\u002Fabout",{"type":10,"value":11,"toc":673},"minimark",[12,16,30,37,42,57,60,63,79,94,102,113,117,120,125,138,151,155,163,171,174,178,193,197,204,209,251,255,273,277,289,295,312,323,331,386,389,423,436,442,446,449,476,480,491,516,520,532,538,578,581,622,635,639,642,646,654,658,661],[13,14,15],"p",{},"Yes, you can flash an ESP32 from a web browser. ESP Web Tools, or any page built on Espressif's esptool-js, talks to the board through the Web Serial API: you open an HTTPS page in Chrome or Edge on a desktop, plug in a USB data cable, pick the serial port and press a button.",[13,17,18,19,23,24,29],{},"This guide explains how ESP Web Tools works (Web Serial, the ",[20,21,22],"code",{},"manifest.json",", the offsets), then shows how the three ",[25,26,28],"a",{"href":27},"\u002Fblog\u002Fwhat-is-opengizmo","OpenGizmo"," devices use the same idea with a real manifest, hosted on a CDN. One detail first: OpenGizmo's site does not embed the ESP Web Tools button. It runs esptool-js directly, and I will show why.",[13,31,32],{},[33,34],"img",{"alt":35,"src":36},"The four steps of browser flashing: pick the USB port with Web Serial, identify the chip, choose its build in the manifest, write the parts at their offsets","\u002Fimages\u002Fblog\u002Fesp-web-tools-flash-esp32-from-browser-steps.webp",[38,39,41],"h2",{"id":40},"how-does-esp-web-tools-work","How does ESP Web Tools work?",[13,43,44,50,51,56],{},[25,45,49],{"href":46,"rel":47},"https:\u002F\u002Fesphome.github.io\u002Fesp-web-tools\u002F",[48],"nofollow","ESP Web Tools"," is an open-source web component from the ESPHome project (Open Home Foundation) that adds an install button for ESP8266 and ESP32 firmware to any web page. Its own site says it works by combining ",[25,52,55],{"href":53,"rel":54},"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FAPI\u002FWeb_Serial_API",[48],"Web Serial",", Improv Wi-Fi (optional) and a manifest that describes the firmware.",[13,58,59],{},"Wait, what is Web Serial? It is a browser API that lets a page read from and write to serial devices, including USB devices that expose a virtual serial port, which is what an ESP32 dev board does. The browser shows a port picker and you choose the port yourself, so a page cannot open a device behind your back.",[13,61,62],{},"Here is what happens when someone presses the button:",[64,65,66,70,73,76],"ol",{},[67,68,69],"li",{},"The browser asks the user to pick a serial port.",[67,71,72],{},"The tool connects to the chip's ROM bootloader and detects the chip. Per the docs, it then selects the right firmware variant from the manifest automatically.",[67,74,75],{},"It downloads the parts of that build and writes each one at its offset.",[67,77,78],{},"Optionally, it waits for Improv Serial to learn the device's state and offer Wi-Fi setup.",[13,80,81,82,87,88,93],{},"The flashing itself is not reinvented. As of November 2026, the ",[25,83,86],{"href":84,"rel":85},"https:\u002F\u002Fgithub.com\u002Fesphome\u002Fesp-web-tools\u002Fblob\u002Fmain\u002Fpackage.json",[48],"ESP Web Tools package"," (version 10.5.x) depends on ",[25,89,92],{"href":90,"rel":91},"https:\u002F\u002Fgithub.com\u002Fespressif\u002Fesptool-js",[48],"esptool-js",", Espressif's JavaScript port of the esptool flasher, along with the Improv serial SDK. That is why the two tools behave alike.",[13,95,96,97,101],{},"Adding the button to your page takes two snippets, both from the ",[25,98,100],{"href":46,"rel":99},[48],"official instructions",": load the script, then place the element and point it at your manifest.",[103,104,111],"pre",{"className":105,"code":107,"filename":108,"language":109,"meta":110},[106],"language-html","\u003Cscript type=\"module\" src=\"https:\u002F\u002Funpkg.com\u002Fesp-web-tools@10\u002Fdist\u002Fweb\u002Finstall-button.js?module\">\u003C\u002Fscript>\n\n\u003Cesp-web-install-button manifest=\"https:\u002F\u002Fexample.com\u002Ffirmware\u002Fmanifest.json\">\u003C\u002Fesp-web-install-button>\n","index.html","html","",[20,112,107],{"__ignoreMap":110},[38,114,116],{"id":115},"which-browsers-support-it-and-why-https","Which browsers support it, and why HTTPS?",[13,118,119],{},"Web Serial only exists in secure contexts, so the page with the button must be served over HTTPS. ESP Web Tools states this as a Web Serial requirement. The browser also has to implement the API, and that is the real limit.",[121,122],"blog-table",{":headers":123,":rows":124},"[\"Browser\",\"Web Serial\",\"Note\"]","[[\"Chrome (desktop)\",\"Yes, from version 89\",\"esptool-js documents Chrome and Edge 89 or later\"],[\"Edge (desktop)\",\"Yes, from version 89\",\"Mirrors Chrome in MDN's compatibility data\"],[\"Chrome on Android\",\"Yes, from version 148\",\"Versions 138 to 147 only saw Bluetooth serial ports\"],[\"Firefox (desktop)\",\"Yes, from version 151\",\"MDN data. I have not tested it\"],[\"Firefox on Android\",\"No\",\"MDN data\"],[\"Safari, any iOS browser\",\"No\",\"MDN data. ESP Web Tools also says not iOS\"]]",[13,126,127,128,133,134,137],{},"The versions come from ",[25,129,132],{"href":130,"rel":131},"https:\u002F\u002Fgithub.com\u002Fmdn\u002Fbrowser-compat-data\u002Fblob\u002Fmain\u002Fapi\u002FSerial.json",[48],"MDN's browser compatibility data"," as of November 2026, and MDN itself marks the feature as not Baseline. I only checked the OpenGizmo flasher's behavior in code, not in each browser. Its card shows \"Cannot flash from this browser\" when ",[20,135,136],{},"navigator.serial"," is missing or the page is not a secure context.",[13,139,140,141,145,146,150],{},"If you are on Safari or a phone, flash once with a tool installed on a computer: see ",[25,142,144],{"href":143},"\u002Fblog\u002Farduino-ide-vs-platformio-for-esp32","Arduino IDE vs PlatformIO for ESP32",", or for the ESP32-CAM, the ",[25,147,149],{"href":148},"\u002Fblog\u002Fesp32-cam-mb-usb-programmer-guide","ESP32-CAM-MB programmer guide",".",[38,152,154],{"id":153},"how-do-you-write-the-manifest-and-pick-the-offsets","How do you write the manifest and pick the offsets?",[13,156,157,158,162],{},"A manifest is a small JSON file that tells the flasher which firmware to install on which chip. Each build lists the files (parts) to write and the flash offset of each one. This is the smallest useful one, in the format from the ",[25,159,161],{"href":46,"rel":160},[48],"ESP Web Tools docs",":",[103,164,169],{"className":165,"code":167,"filename":22,"language":168,"meta":110},[166],"language-json","{\n  \"name\": \"My Firmware\",\n  \"version\": \"1.0.0\",\n  \"builds\": [\n    {\n      \"chipFamily\": \"ESP32-S3\",\n      \"parts\": [{ \"path\": \"merged-firmware.bin\", \"offset\": 0 }]\n    }\n  ]\n}\n","json",[20,170,167],{"__ignoreMap":110},[13,172,173],{},"Part paths are resolved relative to the manifest, and can also be full URLs on other hosts. The fields you are likely to meet:",[121,175],{":headers":176,":rows":177},"[\"Key\",\"Where\",\"What it does\"]","[[\"name, version\",\"top level\",\"Shown in the UI. The name is compared with the firmware the device reports through Improv\"],[\"builds[].chipFamily\",\"build\",\"ESP8266, ESP32, ESP32-C2, ESP32-C3, ESP32-C5, ESP32-C6, ESP32-C61, ESP32-H2, ESP32-P4, ESP32-S2 or ESP32-S3\"],[\"builds[].parts[]\",\"build\",\"A file path and the integer flash offset to write it at\"],[\"builds[].serialType\",\"build\",\"cdc or uart: a separate build for native USB or a USB-UART bridge\"],[\"new_install_prompt_erase\",\"top level\",\"true lets the user choose to erase everything on a new installation\"],[\"new_install_improv_wait_time\",\"top level\",\"Seconds to wait for an Improv response after install (10 by default, 0 turns Improv off)\"],[\"home_assistant_domain, funding_url\",\"top level\",\"Optional links shown after the install\"]]",[13,179,180,181,186,187,192],{},"The offsets depend on the chip and on how you built the firmware. For a firmware split into four files, the ESP-IDF documentation puts the ",[25,182,185],{"href":183,"rel":184},"https:\u002F\u002Fdocs.espressif.com\u002Fprojects\u002Fesp-idf\u002Fen\u002Fstable\u002Fesp32\u002Fapi-guides\u002Fbootloader.html",[48],"second-stage bootloader at 0x1000 on the ESP32"," and ",[25,188,191],{"href":189,"rel":190},"https:\u002F\u002Fdocs.espressif.com\u002Fprojects\u002Fesp-idf\u002Fen\u002Fstable\u002Fesp32s3\u002Fapi-guides\u002Fbootloader.html",[48],"at 0x0 on the ESP32-S3",". The S3 page also puts the partition table at 0x8000 by default. In the PlatformIO builds I ship, the boot_app0 image goes at 0xE000 and the app at 0x10000. Never guess: read them from your build, as the next section does.",[38,194,196],{"id":195},"do-you-need-a-merged-firmware-file","Do you need a merged firmware file?",[13,198,199,200,203],{},"For an ESP32 built with ESP-IDF 4 or later, the ESP Web Tools docs say you do. The reason they give: when the four files are installed with the esptool command, esptool patches the flash frequency, size and mode to match the target device, and ESP Web Tools cannot do that on the fly. So you build one image with ",[20,201,202],{},"merge_bin"," and list it at offset 0.",[205,206],"terminal",{":commands":207,"title":208},"[\"esptool --chip esp32 merge_bin -o merged-firmware.bin --flash_mode dio --flash_freq 40m --flash_size 4MB 0x1000 bootloader.bin 0x8000 partitions.bin 0xe000 boot.bin 0x10000 your_app.bin\"]","Merge the four parts (command from the ESP Web Tools docs)",[13,210,211,212,217,218,221,222,225,226,229,230,233,234,229,237,240,241,244,245,250],{},"Separate parts can also work: the example manifest in the ",[25,213,216],{"href":214,"rel":215},"https:\u002F\u002Fgithub.com\u002Fesphome\u002Fesp-web-tools\u002Fblob\u002Fmain\u002FREADME.md",[48],"ESP Web Tools README"," lists four files, with a bootloader named ",[20,219,220],{},"bootloader_dout_40m.bin"," whose flash settings were already chosen at build time. The merge is the documented route when you start from a normal build. The docs add two caveats: use ",[20,223,224],{},"dout"," when your memory type is ",[20,227,228],{},"opi_opi"," or ",[20,231,232],{},"opi_qspi",", and override ",[20,235,236],{},"qio",[20,238,239],{},"qout"," to ",[20,242,243],{},"dio",". The merged file has a price worth knowing about. The ",[25,246,249],{"href":247,"rel":248},"https:\u002F\u002Fdocs.espressif.com\u002Fprojects\u002Fesptool\u002Fen\u002Flatest\u002Fesp32\u002Fesptool\u002Fbasic-commands.html",[48],"esptool documentation"," says that in the raw format the gaps between files are filled with 0xFF bytes, the value of erased flash. A merged image therefore covers the whole range from the bootloader to the app, including the settings area between the partition table and boot_app0. Keep that in mind for the update section.",[38,252,254],{"id":253},"how-does-opengizmo-flash-from-the-browser-without-the-web-component","How does OpenGizmo flash from the browser without the web component?",[13,256,257,258,261,262,186,265,268,269,272],{},"Each OpenGizmo project page has a firmware card that is not the ESP Web Tools element. It is the component ",[20,259,260],{},"app\u002Fcomponents\u002Fprojects\u002FFlashFirmware.vue"," in the site's source, which imports ",[20,263,264],{},"ESPLoader",[20,266,267],{},"Transport"," from esptool-js (version 0.7.1 in the site's ",[20,270,271],{},"package.json",") and reads a manifest in the ESP Web Tools format. So the format is shared, and only the front end differs.",[274,275],"project-detail-card",{"project-slug":276},"gizmo-ticker",[13,278,279,280,284,285,288],{},"Here is the real manifest the ",[25,281,283],{"href":282},"\u002Fprojects\u002Fgizmo-ticker","Gizmo Ticker"," card reads, at ",[20,286,287],{},"https:\u002F\u002Fcdn.opengizmo.dev\u002Fgizmo-ticker\u002Fmanifest.json"," (fetched on November 14, 2026):",[103,290,293],{"className":291,"code":292,"filename":22,"language":168,"meta":110},[166],"{\n  \"name\": \"Gizmo Ticker\",\n  \"version\": \"v1.2.0\",\n  \"new_install_prompt_erase\": false,\n  \"builds\": [\n    {\n      \"chipFamily\": \"ESP32-S3\",\n      \"parts\": [\n        { \"path\": \"v1.2.0\u002Frelease-bootloader.bin\", \"offset\": 0 },\n        { \"path\": \"v1.2.0\u002Frelease-partitions.bin\", \"offset\": 32768 },\n        { \"path\": \"v1.2.0\u002Frelease-boot_app0.bin\", \"offset\": 57344 },\n        { \"path\": \"v1.2.0\u002Frelease-firmware.bin\", \"offset\": 65536 }\n      ]\n    }\n  ]\n}\n",[20,294,292],{"__ignoreMap":110},[13,296,297,298,302,303,307,308,311],{},"The offsets are decimal, as JSON requires: 32768 is 0x8000, 57344 is 0xE000, 65536 is 0x10000. The ",[25,299,301],{"href":300},"\u002Fprojects\u002Fgizmo-reolink-switch","Gizmo Reolink Switch"," manifest has the same four parts on the same chip. The ",[25,304,306],{"href":305},"\u002Fprojects\u002Fgizmo-camera","Gizmo Camera"," manifest has ",[20,309,310],{},"\"chipFamily\": \"ESP32\""," and its bootloader at 4096 (0x1000), matching the ESP-IDF page above. The other offsets are the same.",[13,313,314,315,318,319,322],{},"One key in these manifests is for the official component only: ",[20,316,317],{},"new_install_prompt_erase: false",". The OpenGizmo card never reads it. ESP Web Tools would treat ",[20,320,321],{},"false"," as its default, which is to erase all data on a new installation.",[13,324,325,326,330],{},"When you press ",[327,328,329],"strong",{},"Flash firmware",", the card does this, in this order:",[64,332,333,340,347,354,357,383],{},[67,334,335,336,339],{},"Calls ",[20,337,338],{},"navigator.serial.requestPort()"," and connects with esptool-js at 115200 baud, which identifies the chip.",[67,341,342,343,346],{},"Downloads the manifest with ",[20,344,345],{},"cache: 'no-store'",", so a new release shows up at once.",[67,348,349,350,353],{},"Looks for the build whose ",[20,351,352],{},"chipFamily"," equals the detected chip name. If there is none, it stops with \"This firmware is not built for the connected chip\", so an ESP32 image never lands on an ESP32-S3.",[67,355,356],{},"Downloads the four parts one by one, resolving each path against the manifest URL.",[67,358,335,359,362,363,366,367,186,370,373,374,366,377,186,380,150],{},[20,360,361],{},"writeFlash"," with ",[20,364,365],{},"flashMode",", ",[20,368,369],{},"flashFreq",[20,371,372],{},"flashSize"," set to ",[20,375,376],{},"'keep'",[20,378,379],{},"eraseAll: false",[20,381,382],{},"compress: true",[67,384,385],{},"Resets the board.",[13,387,388],{},"Why not use the web component? I can point to three things in the code, and I did not try the official button with these manifests, so I can't say how it would behave:",[390,391,392,407,417],"ul",{},[67,393,394,397,398,400,401,406],{},[327,395,396],{},"The four parts stay separate."," With ",[20,399,376],{},", esptool-js ",[25,402,405],{"href":403,"rel":404},"https:\u002F\u002Fgithub.com\u002Fespressif\u002Fesptool-js\u002Fblob\u002Fmain\u002Fsrc\u002Fesploader.ts",[48],"leaves the bootloader's header as the build made it",", so no merge step is needed. And the parts skip the settings area, which a merged file would overwrite.",[67,408,409,412,413,416],{},[327,410,411],{},"A reset fix."," A comment in the site's ",[20,414,415],{},"app\u002Futils\u002FhardReset.js"," says esptool-js only releases RTS, which does nothing when the line is already released, as it is over the chip's own USB on the ESP32-S3. The board then stayed in the bootloader until unplugged. The site passes its own reset: DTR released, RTS held for 100 ms, then released.",[67,418,419,422],{},[327,420,421],{},"A tailored card."," It shows the version before flashing, four stages (connect, download, flash, reboot), a log, the release notes of the version it installs, and translated messages.",[13,424,425,426,430,431,435],{},"The firmware has no Improv support: I found no Improv code in the three repositories. The first Wi-Fi setup goes through a captive portal instead. The ",[25,427,429],{"href":428},"\u002Fblog\u002Fesp32-wifi-provisioning-methods-compared","Wi-Fi provisioning comparison"," covers Improv against the alternatives, and ",[25,432,434],{"href":433},"\u002Fblog\u002Fesp32-captive-portal-not-working-fix","the captive portal fix guide"," covers the portal.",[13,437,438],{},[33,439],{"alt":440,"src":441},"The Gizmo Ticker's four flash parts and their offsets, with the settings area at 0x9000 left alone","\u002Fimages\u002Fblog\u002Fesp-web-tools-flash-esp32-from-browser-flash-map.webp",[38,443,445],{"id":444},"what-is-the-shortest-path-to-your-own-install-page","What is the shortest path to your own install page?",[13,447,448],{},"Here is the whole job in order, for your own firmware:",[64,450,451,454,460,470,473],{},[67,452,453],{},"Build the firmware and collect its parts with their offsets (or one merged file at offset 0 for ESP Web Tools).",[67,455,456,457,459],{},"Upload the parts and a ",[20,458,22],{}," that lists them to an HTTPS host, with CORS headers if it is not the page's own site.",[67,461,462,463,186,466,469],{},"Add the ",[20,464,465],{},"\u003Cscript>",[20,467,468],{},"\u003Cesp-web-install-button>"," snippet above to an HTTPS page, with the manifest URL.",[67,471,472],{},"Open the page in Chrome or Edge on a desktop, plug in the board with a data cable, press the button and pick the port.",[67,474,475],{},"Check that the board boots your firmware and that the page offers the right build for each chip you list.",[38,477,479],{"id":478},"where-do-you-host-the-firmware-and-what-about-cors","Where do you host the firmware, and what about CORS?",[13,481,482,483,486,487,490],{},"You can host the manifest and the parts on the same site as the install page, which needs no CORS setup. OpenGizmo keeps them on a CDN (",[20,484,485],{},"cdn.opengizmo.dev",", backed by a Cloudflare R2 bucket in the release workflow), so the browser makes cross-origin requests. ESP Web Tools tells you to send ",[20,488,489],{},"Access-Control-Allow-Origin: https:\u002F\u002Fdomain-of-your-website.com"," in that case.",[13,492,493,494,497,498,186,501,504,505,508,509,512,513,150],{},"I checked it on November 14, 2026 by requesting the Ticker manifest with ",[20,495,496],{},"Origin: https:\u002F\u002Fopengizmo.dev",": the response carried ",[20,499,500],{},"access-control-allow-origin: https:\u002F\u002Fopengizmo.dev",[20,502,503],{},"vary: Origin",", and a preflight request returned 204 with ",[20,506,507],{},"access-control-allow-methods: GET",". The CDN allows only the site's origin, not ",[20,510,511],{},"*",". Test your own with ",[20,514,515],{},"curl -I -H \"Origin: https:\u002F\u002Fyour.site\" \u003Cmanifest-url>",[38,517,519],{"id":518},"how-do-you-release-a-new-version-without-losing-wi-fi-settings","How do you release a new version without losing Wi-Fi settings?",[13,521,522,523,528,529,162],{},"Keep each version's files in their own folder, never change them, and move the manifest last. OpenGizmo's ",[25,524,527],{"href":525,"rel":526},"https:\u002F\u002Fgithub.com\u002Fopen-gizmo\u002Fgizmo-ticker\u002Fblob\u002Fmain\u002F.github\u002Fworkflows\u002Fbuild_and_release.yml",[48],"release workflow"," does this on a manual run from ",[20,530,531],{},"main",[13,533,534],{},[33,535],{"alt":536,"src":537},"A browser shows the flash memory being written in four orange parts while one grey part stays locked and untouched, with a XIAO board on USB-C","\u002Fimages\u002Fblog\u002Fesp-web-tools-flash-esp32-from-browser-illustration.webp",[64,539,540,547,550,565,568],{},[67,541,542,543,546],{},"Reads ",[20,544,545],{},"VERSION"," and stops if the tag exists or the web app version differs.",[67,548,549],{},"Runs the web app tests and the native firmware tests, then builds the firmware.",[67,551,552,553,558,559,562,563,150],{},"Runs ",[25,554,557],{"href":555,"rel":556},"https:\u002F\u002Fgithub.com\u002Fopen-gizmo\u002Fgizmo-ticker\u002Fblob\u002Fmain\u002F.github\u002Fscripts\u002Fpackage_firmware.py",[48],"package_firmware.py",", which asks PlatformIO for the flash images and their offsets (",[20,560,561],{},"pio project metadata",") and writes ",[20,564,22],{},[67,566,567],{},"Creates a GitHub release with the parts, whose notes give an esptool command for flashing over USB.",[67,569,570,571,574,575,150],{},"Uploads the parts with ",[20,572,573],{},"Cache-Control: public, max-age=31536000, immutable",", then the manifest with ",[20,576,577],{},"max-age=60",[13,579,580],{},"Uploading the manifest last means the website only offers a version that is fully uploaded, and a one-minute cache means a release shows up within a minute. The headers I saw on November 14, 2026 match this.",[13,582,583,584,587,588,593,594,597,598,601,602,604,605,608,609,611,612,616,617,621],{},"The settings survive because of what is not written. The projects use the ",[20,585,586],{},"huge_app.csv"," partition table, in which the ",[25,589,592],{"href":590,"rel":591},"https:\u002F\u002Fgithub.com\u002Fespressif\u002Farduino-esp32\u002Fblob\u002Fmaster\u002Ftools\u002Fpartitions\u002Fhuge_app.csv",[48],"Arduino core defines"," ",[20,595,596],{},"nvs"," at 0x9000 (0x5000 bytes) and ",[20,599,600],{},"otadata"," at 0xE000. The four parts do not cover the ",[20,603,596],{}," region (0x9000 to 0xDFFF), and ",[20,606,607],{},"eraseAll"," is ",[20,610,321],{},", so the Preferences data lives on. That follows from the offsets and the code. I did not measure a flash before and after. The ",[25,613,615],{"href":614},"\u002Fblog\u002Fesp32-partition-table-explained","partition table guide"," explains the layout, and the ",[25,618,620],{"href":619},"\u002Fblog\u002Fesp32-ota-update-methods-compared","OTA comparison"," explains why these devices update over USB, as they have no second app slot.",[13,623,624,625,608,628,631,632,150],{},"With the official component, read the erase rule: ESP Web Tools erases all data on a new installation unless ",[20,626,627],{},"new_install_prompt_erase",[20,629,630],{},"true"," and the user declines. It offers a new installation when it cannot detect the device's current firmware, or when the detected firmware does not match the manifest ",[20,633,634],{},"name",[38,636,638],{"id":637},"what-breaks-most-often","What breaks most often?",[13,640,641],{},"Most failures are the cable, the port or the browser, not the firmware. Work down this table, changing one thing at a time.",[121,643],{":headers":644,":rows":645},"[\"What you see\",\"Likely cause\",\"What to try\"]","[[\"Button disabled, or 'Cannot flash from this browser'\",\"Browser without Web Serial, or the page is not HTTPS\",\"Use Chrome or Edge on a desktop, over HTTPS or localhost\"],[\"Port picker shows no device\",\"Charge-only USB cable, or the board is not detected\",\"Use a data cable and another USB port, then reload the page\"],[\"Connecting fails, no serial data received\",\"The chip is not in download mode, or the USB link is flaky\",\"See the 'Failed to connect' guide\"],[\"'This firmware is not built for the connected chip'\",\"The manifest has no build for that chip family\",\"Add a build for it, or use the right board\"],[\"'Firmware download failed with status 404'\",\"A part path in the manifest is wrong\",\"Open each part URL in a tab\"],[\"Manifest cannot be read, with a CORS error in the console\",\"The CDN does not allow your page's origin\",\"Send Access-Control-Allow-Origin for your domain\"],[\"Flash finishes but the board sits in the bootloader\",\"No real reset pulse after flashing\",\"Unplug and replug; a custom hard reset like the one above fixes it\"]]",[13,647,648,649,653],{},"For the third row, ",[25,650,652],{"href":651},"\u002Fblog\u002Fesp32-failed-to-connect-no-serial-data-received","Failed to Connect to ESP32: No Serial Data Received"," walks through boot mode, cables and drivers. The error texts in the table are the ones in the OpenGizmo card's translation file, and your own page will say something else.",[38,655,657],{"id":656},"where-does-browser-flashing-stop","Where does browser flashing stop?",[13,659,660],{},"Browser flashing gives you a page where anyone with Chrome or Edge, a cable and a board can install your firmware in a minute, with the settings kept and a version number on screen. We covered the pieces: Web Serial over HTTPS, a manifest of parts and offsets (merged for ESP Web Tools, or four parts with esptool-js), CORS if the files live elsewhere, and a release that uploads the manifest last.",[13,662,663,664,667,668,672],{},"Three limits remain. It only covers wired flashing; for updates over Wi-Fi see the ",[25,665,666],{"href":619},"OTA methods comparison",". Browser support outside Chrome and Edge is thin as of November 2026, and I tested none of it. And I only described the official component from its docs and source, not from my own use. If you want to see the whole thing working, the ",[25,669,671],{"href":670},"\u002Fblog\u002Fhow-to-build-a-crypto-ticker-with-esp32-and-max7219","Gizmo Ticker build guide"," flashes a board from start to finish, and the three project pages each have the card.",{"title":110,"searchDepth":674,"depth":674,"links":675},2,[676,677,678,679,680,681,682,683,684,685],{"id":40,"depth":674,"text":41},{"id":115,"depth":674,"text":116},{"id":153,"depth":674,"text":154},{"id":195,"depth":674,"text":196},{"id":253,"depth":674,"text":254},{"id":444,"depth":674,"text":445},{"id":478,"depth":674,"text":479},{"id":518,"depth":674,"text":519},{"id":637,"depth":674,"text":638},{"id":656,"depth":674,"text":657},"guides","Guides","2026-11-14T00:00:00Z","Flash an ESP32 from the browser with ESP Web Tools or esptool-js: how Web Serial, the manifest and the flash offsets work, with a real OpenGizmo manifest.","md",[692,695,698,701,704,707],{"question":693,"answer":694},"Can I flash an ESP32 from a browser without installing anything?","Yes. A page that uses ESP Web Tools or esptool-js talks to the board through the Web Serial API, so you only need a data USB cable and Chrome or Edge on a desktop. The page must be served over HTTPS. You pick the serial port, and the firmware is written from the browser.",{"question":696,"answer":697},"Does ESP Web Tools work in Firefox or Safari?","ESP Web Tools lists Firefox, Chrome, Edge and Chrome on Android as supported, but not iOS. MDN's compatibility data shows Web Serial in Firefox from version 151 on desktop, and not in Safari at all. Chrome and Edge remain the safe choice, and I have not tested the others.",{"question":699,"answer":700},"Do I need a merged firmware file for ESP Web Tools?","ESP Web Tools documents that ESP32 firmware built with ESP-IDF 4 or later must be merged into one file, because the tool cannot patch the flash mode, frequency and size the way esptool does. You create it with esptool merge_bin and list it as one part at offset 0 in the manifest.",{"question":702,"answer":703},"Does flashing from the browser erase my Wi-Fi settings?","Only if the flasher erases them. ESP Web Tools erases all data on a new installation unless the manifest sets new_install_prompt_erase to true and you decline. The OpenGizmo flasher writes four parts and never erases the whole chip, so the settings stored in the NVS partition survive an update.",{"question":705,"answer":706},"What is Improv Wi-Fi?","Improv Wi-Fi is an open standard for sending Wi-Fi credentials to a device over its serial port. If the firmware supports it, ESP Web Tools asks the user to connect the device to a network right after installing. Firmware without Improv, such as OpenGizmo's, uses a captive portal for that step instead.",{"question":708,"answer":709},"Why does browser flashing need HTTPS?","The Web Serial API is only available in secure contexts, so the page that holds the install button must be served over HTTPS (localhost also counts as secure). A plain HTTP page cannot open a serial port. If the manifest and firmware are on another host, that host must also send CORS headers.","\u002Fimages\u002Fblog\u002Fesp-web-tools-flash-esp32-from-browser.jpg","A bearded man in a blue hoodie sits by a laptop whose browser shows an orange Install button and a 68% progress bar, with a USB cable running to an ESP32 board.","en",{},true,"\u002Fblog\u002Fesp-web-tools-flash-esp32-from-browser",{"title":5,"description":689},{"loc":715},"blog\u002Fesp-web-tools-flash-esp32-from-browser","ESP Web Tools flashes an ESP32 over Web Serial, in Chrome or Edge on an HTTPS page, from a manifest.json that lists each firmware part and its flash offset. OpenGizmo does the same with esptool-js.",[721,722,723,28,724],"ESP32","Firmware","Development Tools","Embedded Systems","F7S1n2hNut2ESzIdOvKEWN8NvyWu4p7wr1QgNn0QcOo",[727,733,739,747],{"title":728,"description":729,"image":730,"categoryText":687,"categorySlug":686,"tags":731,"path":614},"ESP32 Partition Table Explained: Flash Layout and OTA","What the ESP32 partition table is, how the partitions.csv columns work, the Arduino-ESP32 schemes with sizes, flash offsets by chip, and what N16R8 means.","\u002Fimages\u002Fblog\u002Fesp32-partition-table-explained.jpg",[721,722,724,732,28],"PlatformIO",{"title":734,"description":735,"image":736,"categoryText":687,"categorySlug":686,"tags":737,"path":148},"ESP32-CAM-MB: Program the ESP32-CAM Over USB","How to program an ESP32-CAM with the ESP32-CAM-MB USB board: what it contains, the IO0 and RST button sequence, flashing from Chrome, and what fails.","\u002Fimages\u002Fblog\u002Fesp32-cam-mb-usb-programmer-guide.jpg",[738,721,722,723,28],"ESP32-CAM",{"title":740,"description":741,"image":742,"categoryText":687,"categorySlug":686,"tags":743,"path":746},"CoinGecko API on ESP32: Free Limits and Polling Rate","CoinGecko's free Demo plan allows 100 calls a minute and 10,000 a month. The polling math for an ESP32, how to send the key, and what HTTP 429 means.","\u002Fimages\u002Fblog\u002Fcoingecko-api-esp32-rate-limits.jpg",[721,744,722,28,745],"IoT","MAX7219","\u002Fblog\u002Fcoingecko-api-esp32-rate-limits",{"title":748,"description":749,"image":750,"categoryText":687,"categorySlug":686,"tags":751,"path":27},"What Is OpenGizmo? Open-Source ESP32 Gadgets You Can Flash","OpenGizmo is a set of MIT-licensed ESP32 gadgets by Mauro Brambilla: a crypto LED ticker, a Reolink NVR switch and an ESP32-CAM, each flashed from the browser.","\u002Fimages\u002Fblog\u002Fwhat-is-open-gizmo.png",[28,752,721,722,753],"Open Source","3D Printing",[755,761,767],{"name":756,"slug":757,"path":758,"count":759,"image":760},"Troubleshooting","troubleshooting","\u002Fblog\u002Fcategories\u002Ftroubleshooting",5,"\u002Fimages\u002Fblog\u002Fesp32-brownout-detector-was-triggered.jpg",{"name":762,"slug":763,"path":764,"count":765,"image":766},"Builds","builds","\u002Fblog\u002Fcategories\u002Fbuilds",6,"\u002Fimages\u002Fblog\u002F3d-printed-esp32-enclosure-design-guide.jpg",{"name":768,"slug":769,"path":770,"count":771,"image":772},"Comparisons","comparisons","\u002Fblog\u002Fcategories\u002Fcomparisons",8,"\u002Fimages\u002Fblog\u002Fesp32-ota-update-methods-compared.jpg",{"title":283,"badge":774,"description":775,"path":282,"image":776,"cardIcon":777,"highlights":778},"Open-source ESP32 + MAX7219 project","A WiFi-connected crypto display built with an ESP32, a MAX7219 LED matrix, and a Nuxt 4 web app for browser-based setup and configuration.","\u002Fimages\u002Fprojects\u002Fgizmo-ticker\u002Fcover.webp","BitcoinIcon",[779,780,781],"Live crypto ticker","MAX7219 LED matrix","Web-based setup",1795018235839]