# ESP-BOX: Espressif's voice and touch development board family > ESP-BOX is the Espressif repository for a family of development boards built on the ESP32-S3, covering offline voice assistants, LLM chatbots, Matter devices and USB hosts and devices, with the hardware design, the factory firmware source and a set of ready made examples published under Apache-2.0. Two of the three boards are marked end of life, so the framework now effectively means the ESP32-S3-BOX-3. **espressif/esp-box** — The ESP-BOX is a new generation AIoT development platform released by Espressif Systems. - Repository: https://github.com/espressif/esp-box - Stars: 1,339 · Forks: 287 - Language: HTML - License: Apache-2.0 - Published: 2026-10-19 · Updated: 2026-10-19 · Language: en - Canonical page: https://hysenlabs.com/projects/espressif-esp-box ## Three boards, two of them retired The ESP-BOX repository documents a board family rather than a single product, and the marketing status table is the first thing worth reading. The ESP32-S3-BOX and the ESP32-S3-BOX-Lite are both marked End of Life, with their user guides pointing at the v0.5.0 tag, while the ESP32-S3-BOX-3 is the one marked Active, with its user guide on the master branch. The README says the two older boards should have their built-in factory firmware updated on arrival so you get the latest bug fixes, and that support for them in the master branch will be gradually reduced, with the examples README holding the detail. The physical differences matter when you pick a board. The ESP32-S3-BOX-3 comes in two variants, the standard edition with four blue accessories and the ESP32-S3-BOX-3B, which ships fewer accessories for people who do not need the extra hardware, and the distinction is spelled out in the variant description section of the getting started document. The boards are built on the ESP32-S3 Wi-Fi plus Bluetooth 5 LE SoC and come in compact enclosures, and the stated role of the family is prototyping new projects and building complete IoT systems rather than bare development. ## The version table is the compatibility map Because this is firmware that has moved with the underlying ESP-IDF, the repository ships a table that pairs each branch or tag with the toolchain it needs, and this is the single most useful page for a new user. The master branch depends on ESP-IDF release/v5.1 at commit 22cfbf30c3, carries the latest developing firmware, and uses esp-sr components version v1.4.1, with partial support for all three boards and a note to use menuconfig to select the board. Tag 0.5.0 uses the same ESP-IDF release/v5.1 commit but esp-sr v1.3.4 and is compatible with the ESP32-S3-BOX and the Lite. Tag 0.3.0 moves back to release/v4.4 at commit 2bdea81b2a with esp-sr on dev/v2.0. The two earliest tags, 0.2.1 and 0.1.1, use release/v4.4 with a patch directory and support the ESP32-S3-BOX only. The practical reading is that if you are on the BOX-3 you should follow master, and if you have an older BOX or Lite the v0.5.0 tag is the safe point, because the master branch is where the older boards lose support. ## Voice interaction is the reason the board exists The feature list describes the device as a four in one voice interaction panel on FreeRTOS, combining offline voice recognition, network communication, screen display and peripheral control. The audio hardware is a two microphone far field array, and the recognition side supports offline wake-up, command recognition, continuous recognition, wake-up interrupt and more than 200 customizable command words. The offline path is the interesting part, because it runs on the device rather than depending on a cloud service, which is what makes it usable as a local assistant and what makes wake-up rate a stated feature. The board also carries a display and touch, so the human machine interaction story is the display and the GUI rather than voice alone. For the GUI, the documentation points at drag-and-drop tools such as LVGL SquareLine Studio and Embedded Wizard, and for the software side it lists ESP-IDF, Arduino, PlatformIO and Circuit Python among the supported frameworks. That combination, a fixed accessory set and several toolchains, is the reason the box is a platform rather than a board you wire up yourself. ## What is actually published in the repository The open source content is more than example code. The hardware directory holds the schematic and the PCB source file, and the Shell 3D print source file, so the enclosure is reproducible rather than a black box. The built-in firmware source code lives in examples/factory_demo, which is the piece most people would not expect to find published: the factory firmware that ships on the device is available to read and modify, and the firmware update documentation tells you how to flash a newer version. The examples/ directory is the working part of the repository, and the named example projects indicate the intended use cases. There is a chatgpt_demo for the LLM chatbot direction, an esp_joystick example, factory_demo itself, image_display, a set of lv_demos for the GUI, matter_switch for the Matter device path, mp3_demo, usb_camera_lcd_display, usb_headset, and watering_demo, which reads like a home automation sensor node. The top level also carries components/, tools/, a bin/ directory, a .gitmodules file, a .pre-commit-config.yaml, a .gitlab-ci.yml alongside the .github/ workflows, and a codespell-ignore-list. The license is Apache 2.0, and the README states plainly that you can modify, develop or distribute the contents freely. ## The example set maps onto the application domains The README lists the application domains the platform is meant to cover, and the example directory is a fair proxy for how wide that is. Offline voice assistants are the core case. Online AI chatbots, developed using OpenAI and other large language model platforms, are covered by the chatgpt_demo example. Matter device and controller work is represented by matter_switch, and the feature list adds Matter, Home Assistant and ESP-RainMaker as the home automation angle. Robot controller is listed as a domain, USB device and host is a domain with two dedicated examples in usb_camera_lcd_display and usb_headset, and wireless sensor applications are represented by watering_demo, which is a device that has to act on a physical plant. That breadth is the point of the platform framing. Rather than a single demo, you get a set of reference applications that each show a different way to use the accessory set, and the watering demo in particular is the shape of a real deployment. ## Flashing and the ESP Launchpad path The onboarding path is documented through Espressif's online flashing tool. The README links to ESP Launchpad with a flash configuration URL pointing at a launchpad.toml file hosted in this repository, and the badge invites you to try the project from there. The key operational step is the factory firmware update, which the documentation asks you to perform on receipt of the board, because the shipped firmware may predate the current bug fixes. The current version is named as ESP-BOX-3_Demo_V1.2.4, and the way to confirm what is actually running is the About Us page on the device itself. That is worth knowing, because the difference between a board running an old factory image and one running the current one is a class of problems that otherwise looks like a hardware fault. The hardware overview for the specific board is the recommended first read, and the getting started document comes next, which is a sensible order since the accessories and their wiring determine what the example code can assume. ## Where ESP-BOX is the wrong choice The clearest case is the retired hardware. If you are buying a board today, the original ESP32-S3-BOX and the Lite are end of life, they are no longer sold, and the framework support for them is being reduced on master, so a new project on those boards starts with a legacy branch and a v0.5.0 tag. The second case is expectation setting around the platform. This is a vendor framework for a specific board family with a specific accessory set, so the value comes from the microphone array, the display, the touch and the bundled examples, and if your project needs a different sensor set or a different form factor the accessory argument weakens considerably. The third case is the firmware dependency. Building on master means tracking the ESP-IDF release branch, the esp-sr component version and the tag structure at the same time, and the version table shows how those three move together, so an upgrade is a coordinated operation rather than a pull. The fourth is the gap between the source and the releases. The newest tagged release is v0.5.0 from 2023-08-21, and the last push to master was on 2026-06-01, so the published releases are far behind the branch where the BOX-3 work actually lives, and anyone who needs a reproducible artifact has to build it themselves from a specific commit. ## Conclusion ESP-BOX suits an embedded developer who wants a ready made ESP32-S3 board with a microphone array, a display and touch, and who wants the hardware files and the factory firmware source to build on. It does not suit you if you need the original ESP32-S3-BOX or the Lite, since both are listed as end of life, and it does not suit you if you expect a general purpose single board computer, because the value is in the accessories and the examples rather than the SoC. Before you start, read the hardware overview for the ESP32-S3-BOX-3 and check the version table for the ESP-IDF branch and the esp-sr component version that matches your board, and note that the last push was on 2026-06-01 while the newest tagged release is v0.5.0 from 2023-08-21. ## FAQ ### Which ESP-BOX boards are still supported? The ESP32-S3-BOX and the ESP32-S3-BOX-Lite are listed as End of Life with their user guides on the v0.5.0 tag, while the ESP32-S3-BOX-3 is marked Active. The README says support for the two older boards on the master branch will be gradually reduced. ### What should I do when I first receive an ESP32-S3-BOX-3? Update the built-in factory firmware using Espressif's online flashing tool ESP Launchpad. The version named in the documentation is ESP-BOX-3_Demo_V1.2.4, and you can confirm what is running on the About Us page. ### What open source files does the ESP-BOX repository publish? The hardware directory holds the schematic and the PCB source file along with the Shell 3D print source file, the built-in firmware source code is in examples/factory_demo, and the other examples live in examples/. ### Which ESP-IDF version does the master branch need? The version table lists master as depending on ESP-IDF release/v5.1 at commit 22cfbf30c3 with esp-sr components version v1.4.1, and it says to use menuconfig to select the board. ## Sources - [espressif/esp-box on GitHub](https://github.com/espressif/esp-box) - [Issues](https://github.com/espressif/esp-box/issues) - [License: Apache-2.0](https://github.com/espressif/esp-box/blob/master/LICENSE) - [README](https://github.com/espressif/esp-box/blob/master/README.md) - [Releases](https://github.com/espressif/esp-box/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/espressif-esp-box