Espressif puts Eclipse-based IDE into maintenance and recommends VS Code

Espressif’s Eclipse-based IDE is now maintenance-only until October 2027; new ESP-IDF projects should use the VS Code extension.

Quick summary: Espressif announced on 12 November 2026 that Espressif-IDE 4.5.0 is the final feature release of its Eclipse-based development environment. The software is now in maintenance until 14 October 2027, with only high-severity bug and security fixes planned. New ESP-IDF projects should use Espressif’s Visual Studio Code extension instead.

Espressif is winding down feature development for Espressif-IDE and the separately installable ESP-IDF Eclipse Plugin. Existing users are not being cut off immediately, but the company’s new support policy gives teams an exact migration deadline and makes VS Code the recommended starting point for new work.

Laptop displaying code beside a monitor and phone, illustrating ESP-IDF software development
Illustrative coding workstation; the screen does not show Espressif-IDE, Eclipse or the ESP-IDF VS Code extension. Photo by Shamsudeen Adedokun on Unsplash, used under the Unsplash License.

This is a support change, not a new November release

The date distinction matters. Espressif-IDE 4.5.0 was released on 14 October 2026; Espressif published the maintenance announcement and migration guidance on 12 November. Version 4.5.0 is therefore not a newly launched build, but its status has now been formalised: it is the last version to receive features, releases before 4.5.0 receive no more updates, and any necessary maintenance builds will use the 4.5.x numbering.

Support ends on 14 October 2027. Until then, Espressif says it will address high-severity defects and security issues. After that date, the standalone IDE and Eclipse plugin reach end of life, with no further feature, bug-fix or security releases promised. This policy affects the development tools, not the ESP-IDF framework itself or the ESP32 chips and boards built with it.

What Espressif-IDE 4.5.0 contains

The final feature release moves the standalone application to Eclipse 2026-09, based on Eclipse Platform 4.41, and bundles OpenJDK 25.0.4. Developers installing the plugin into an existing Eclipse installation need Java 25 or later.

Workflow changes include unified launch and debug configurations, safer ESP-IDF target switching and a route into ESP-IDF Manager when required tools are missing. The generated .clangd configuration now uses the toolchain driver’s built-in headers through QueryDriver. The release also fixes custom build-folder resets and stops Kconfig notes being misread as errors.

Existing ESP32 projects do not need to be recreated

Espressif’s migration guide says source code, CMakeLists.txt, sdkconfig files, dependency locks, component manifests and local or managed components can normally be reused. In VS Code, developers select the ESP-IDF version, target and device through the ESP-IDF extension, then use its build, flash, monitor and debug commands.

The awkward part is IDE-specific state. Custom build directories, JTAG and OpenOCD board settings, adapter configuration, Eclipse .launch values and environment-specific caches may need manual recreation. Espressif specifically advises keeping the original Eclipse workspace, including its .metadata directory, until Build, Flash, Monitor and Debug have all been verified in VS Code.

For teams with a stable Eclipse-based production workflow, there is no requirement to switch today. The practical deadline is the end of security maintenance in October 2027. However, starting another long-lived product on Espressif-IDE 4.5 would create a known migration task before that product has necessarily reached the end of its own support life.

Why Espressif is concentrating on VS Code

Espressif says fewer developers are choosing its Eclipse environment for new projects, while AI-assisted editing has moved towards tools such as VS Code and Cursor. Development effort is shifting to the ESP-IDF extension for VS Code, ESP-IDF Installation Manager and a web IDE experience. That direction is consistent with the company’s recent push into coding-agent workflows, including the ESP-Mosaico development kit.

The VS Code extension covers the core embedded workflow: project creation, CMake configuration, target and serial-port selection, builds, flashing over UART, DFU or JTAG, serial monitoring, debugging, partition editing, size analysis, core-dump inspection, unit tests and QEMU support. That does not guarantee a one-click migration for every customised Eclipse workspace, which is why Espressif has published a separate checklist rather than presenting the switch as automatic.

Downloads and the sensible next step

Espressif-IDE 4.5.0 remains downloadable for Windows, macOS and Linux, and the Eclipse plugin remains available through the update site. Current Eclipse users should move to 4.5.x, record any workspace-only settings and plan a tested migration before 14 October 2027. New ESP-IDF projects have the clearer answer: begin with the official VS Code extension.

Sources

CONTINUE EXPLORING / ESP32 & ELECTRONICS

Read next

Practical guides related to this article.

Explore the topic →
HARDWARE DECISION GUIDEWhich ESP32 board should you use?

Compare practical options before you choose hardware.

Compare options →