What Is Phoenix Code and How Does It Relate to Brackets?

Updated

Phoenix Code is the next generation of Brackets, the open-source code editor that Adobe founded and the brackets.io community maintained. If you still use Brackets, the official site now recommends upgrading to Phoenix Code, which runs on Windows, macOS, Linux, and web browsers. The relationship is a continuation, not a fork: the same community carries the project forward under a new name, and the Brackets site provides a migration path for existing users.

The short version

  • Brackets was a lightweight, open-source code editor built with HTML, CSS, and JavaScript, known for inline editors and live preview.
  • Phoenix Code is described on brackets.io as "the next generation of Brackets," built for the same audience and maintained by the same community.
  • The Brackets homepage now leads with "Introducing Phoenix Code Editor" and states plainly that Brackets recommends users upgrade.
  • Phoenix Code keeps the live preview workflow for HTML, CSS, and JavaScript that defined Brackets.

What carried over from Brackets

The features that made Brackets distinctive are the ones Phoenix Code inherits:

Feature What it does
Inline Editors Opens a window into related code (for example, a rule from a CSS file) instead of making you jump between file tabs
Live Preview Maintains a real-time connection to the browser, so CSS and HTML edits appear on screen instantly
Preprocessor Support Lets you work with preprocessors as part of the normal editing workflow
Extension ecosystem Brackets extensions such as Git, Emmet, Beautify, Markdown Preview, File Icons, Indent Guides, Autoprefixer, and W3C Validation shaped how users customized the editor

If your daily work depends on inline editing or live preview, that is the continuity argument for moving to Phoenix Code rather than switching to an unrelated editor.

What changed

The most visible change is reach. Brackets was a desktop application; Phoenix Code runs on Windows, macOS, and Linux and in web browsers, so you can open the editor without installing anything locally. The project identity also shifted: Brackets was founded by Adobe as a community-guided open-source project, and it now continues as Phoenix Code under the brackets.io community.

How to move from Brackets to Phoenix Code

  1. Download Phoenix Code from phcode.dev, choosing the build for Windows, macOS, or Linux.
  2. Or launch the web editor if you want to try it in a browser before installing anything.
  3. Follow the migration guidance linked from brackets.io ("Migrate from Brackets to Phoenix Code") to carry your setup across.
  4. Reinstall the extensions you rely on. The Brackets site lists popular extensions like Git, Emmet, and Beautify; check that the ones in your workflow are available before you commit to the switch.

The expected result is the same editing experience you had in Brackets — inline editors, live preview, preprocessor support — running on a codebase that is actively maintained.

Who should care

  • Current Brackets users: the official recommendation is to upgrade, so treat Phoenix Code as the supported path forward rather than staying on an unmaintained editor.
  • New users evaluating a lightweight editor: Phoenix Code is free and open source, and the browser option lowers the cost of trying it.
  • Teams standardized on Brackets extensions: verify extension availability during migration, since that is the most likely friction point.

Where to go next

The Brackets site links to the Phoenix Code source on GitHub, API documentation, a blog, a troubleshooting help wiki, and community channels on Matrix, Discord, and Reddit. Those are the places to confirm current extension support and report issues after you migrate.