Open-source project
thedmd/imgui-node-editor avatar
thedmd/imgui-node-editor

imgui-node-editor: you copy the sources, the layout lives in JSON

Node Editor built using Dear ImGui

4,550 stars711 forksC++MIT

At a glance

What is it?
A node editor for Dear ImGui with an ImGui-like API, installed by pasting its sources into your project. It keeps your graph layout in a JSON file and asks you to own every upgrade from there.
Who is it for?
imgui-node-editor suits a C++ application that already draws with Dear ImGui and wants a blueprint style canvas without building an editor from scratch, since it handles placement, dragging, zoom, selection, and the interaction events while you keep the drawing of node content.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 20 days ago.
What is it written in?
Mainly C++, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • thedmd/imgui-node-editor4,550 ★ · +39
Star history
Repository2026-09-232026-11-15
thedmd/imgui-node-editor4.5k4.6k

39 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Installation is a file copy, not a dependency

Node Editor has no package manager entry. The sources sit in the root project directory and the instruction is to copy and paste them into your own project, exactly the way you would with ImGui itself. Nothing is fetched at build time and nothing is versioned on your behalf.

That instruction turns the root listing into your checklist. imgui_node_editor.h is the main header, imgui_node_editor.cpp and imgui_node_editor_api.cpp carry the implementation, imgui_node_editor_internal.h with imgui_node_editor_internal.inl hold the internals, imgui_bezier_math.h and imgui_bezier_math.inl do the curve work, imgui_extra_math.h and imgui_extra_math.inl add math helpers, imgui_canvas.cpp and imgui_canvas.h are the canvas, and crude_json.cpp with crude_json.h are a hand written JSON parser. Two requirements come with them: Dear ImGui 1.80 or newer, and C++14.

The cost of that model is yours to carry. There is no version to pin and no upgrade path. When the upstream files change, the diff lands in your repository and nobody but you decides when to take it. Directories such as docs/, examples/, misc/, and tests/ stay behind unless you have a reason to want them.

SettingsFile is the one config field the quick start shows

The editor is created through a config struct rather than a bare call, and the sample shows the whole lifecycle:

cpp
# include
# include
# include <application.h>

namespace ed = ax::NodeEditor;

struct Example:
    public Application
{
    using Application::Application;

    void OnStart() override
    {
        m_SettingsFile = ResolvePath("Simple.json");

        ed::Config config;
        config.SettingsFile = m_SettingsFile.c_str();
        m_Context = ed::CreateEditor(&config);
    }

    void OnStop() override
    {
        ed::DestroyEditor(m_Context);
    }

    void OnFrame(float deltaTime) override
    {
        IM_UNUSED(deltaTime);

        auto& io = ImGui::GetIO();

Node state can be saved in user context so a layout does not break, and Simple.json is the file named in the sample, passed through ResolvePath before it reaches SettingsFile.

Two more things are visible in the snippet. It ends partway through OnFrame, before anything queries nodes or draws the editor, so it is the scaffold rather than a working frame body. Its include block names two headers only as # include, and the third one pulls in application.h, which lives in the examples/application folder instead of with the editor sources.

An empty grid means the camera is not pointed at your nodes

Press F to focus on the editor content if you see only the grid. That one key is the first thing to know about the view, and it exists because the editor owns the camera rather than the host application.

The editor takes care of placing your node in the world, dragging nodes, zoom and scrolling, and selection. Smooth navigation and selection are listed as highlights, together with selection rectangles and group dragging. imgui_canvas.cpp and imgui_canvas.h are where that surface lives, and canvas-example in the examples directory is the place to see it on its own.

The division of labour is stated as draw your content, we do the rest: interactions are handled by the editor, content rendering is handled by the user. You query the editor for what just happened and you draw the node body yourself. Node and pin contents are fully customizable, and the default theme is modeled after UE4 blueprints, which is a starting look rather than a constraint, since the editor is drawn through the ImGui style API.

Link curves live in their own header pair

Customizable links based on Bezier curves are one of the listed highlights, and the curve code is not buried inside the editor implementation. imgui_bezier_math.h with imgui_bezier_math.inl sits at the root as its own pair, next to imgui_extra_math.h and imgui_extra_math.inl, so a host project can reach the geometry without dragging in the editor API.

Automatic highlights for nodes, pins, and links are called out as well, and that pairs with the way the editor reports itself: creation, deletion, and selection changes are interactions the editor handles and that the API can be queried about, so your code does not have to reconstruct hover or selection state.

One rendering fix is marked as no longer needed. The optional branch thedmd/imgui draw-list-fringe-scale, offered for sharp rendering while zooming, is struck through with a note that it has been part of ImGui since the 1.80 release. Since the stated floor is now Dear ImGui 1.80, every supported ImGui version already includes it.

Shortcuts stop at cut, copy, paste, and delete

Basic shortcuts support is listed as cut, copy, paste, and delete, and that is the whole documented keyboard surface. One of the optional branches exists precisely because the list is thin: the thedmd/imgui extra-keys branch, described as being for extra shortcuts.

Context menu support and the ImGui style API appear in the same list, alongside the promise that node movement and selection are handled internally, so dragging is not yours to implement.

What none of it tells you is which keys are bound beyond those four, whether any of them can be remapped, or how a paste lands on an existing selection.

CMake generators are listed per platform, the output path is not

The examples build with CMake 3.24 or newer using the platform's default generator; `-G Ninja` or `-G Xcode` picks another:

shell
cmake -S examples -B build
cmake --build build --config Release

The README says the executables are in `build/bin` and find their data next to them, so they can be started from any directory. The examples are one directory per topic: basic-interaction-example, canvas-example, widgets-example, simple-example, blueprints-example, and data, all wired through examples/CMakeLists.txt.

The blueprints sample needs a forked ImGui, the rest do not

Example dependencies are not uniform. One of them is a fork of ImGui itself: the thedmd/imgui tree on the feature/layout-external branch, Dear ImGui 1.93.0 WIP with Stack Layout, marked as used in the blueprints sample. Dear ImGui 1.80 or newer is the requirement for the editor itself.

That split has a direct consequence for you. The basic interaction, canvas, widgets, and simple examples can be built against a stock ImGui, but the blueprints sample expects an ImGui built from that branch, which CMake fetches, together with stb and GLFW, at revisions pinned in examples/cmake. On a project running stock ImGui, that sample is not something you can drop in to sanity-check your integration; it is the reference for what the forked layout looks like.

The newest tag is from 2023 while commits landed in 2026

The three most recent releases are v0.9.2, labelled a stable branch release, from 2023-09-01; v0.9.3, a bugfix release, from 2023-10-14; and v0.9.4, labelled final v9 branch, from 2026-10-14. The last push is dated 2026-10-23.

So the newest release, v0.9.4, trails the last push by about nine days.

The project's own account of itself is more cautious than the commit dates would suggest. It describes itself as a basis for more complex solutions such as blueprint editors, notes that it was used to implement the blueprint editor in the Spark CE engine, and says it is slowly moving into a stable state from having been a prototype. Plan your integration around that: since you copy the source into your own tree and maintain it yourself, the real decision is which commit you copy, not which release you install. A build workflow under .github shows what gets compiled.

Editorial conclusion

imgui-node-editor suits a C++ application that already draws with Dear ImGui and wants a blueprint style canvas without building an editor from scratch, since it handles placement, dragging, zoom, selection, and the interaction events while you keep the drawing of node content. It does not suit a team that wants a versioned dependency, because the install path is a file copy with no upgrade story, and the node layout is saved to a JSON settings file whose path you set yourself. Before you commit, decide which commit of master you copy, since the newest release, v0.9.4, dates from 2026-10-14 while the last push is dated 2026-10-23, and check that your ImGui is 1.80 or newer; the blueprints sample uses the feature/layout-external branch of thedmd/imgui.

Frequently asked questions

What does imgui-node-editor depend on?

Dear ImGui 1.80 or newer, and C++14. The blueprints example additionally needs the thedmd/imgui fork on its feature/layout-external branch, and an optional extra-keys branch of that fork is offered for extra shortcuts.

How do I build the imgui-node-editor examples?

Configure with cmake -S examples -B build, which uses the platform's default generator; -G Ninja or -G Xcode picks another. Then run cmake --build build --config Release. The executables end up in a bin folder under the build directory.

Why does my imgui-node-editor window show only a grid?

Press F to focus on the editor content. The editor owns the camera and handles zoom, scrolling, and panning itself, so a fresh window can start looking away from where your nodes are placed.

Where does imgui-node-editor save my node layout?

In the file named by the SettingsFile field of ed::Config, set in the quick start sample to the result of ResolvePath("Simple.json"), so node positions survive a restart. The docs do not say which directory that path resolves against.

Which imgui-node-editor version should I copy into my project?

The newest release is v0.9.4, labelled final v9 branch, from 2026-10-14, while the last push is dated 2026-10-23 and the project was restructured to mimic the ImGui layout. The docs do not say whether to build against the tag or the branch tip.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. thedmd/imgui-node-editor on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/thedmd-imgui-node-editor.svg)](https://hysenlabs.com/projects/thedmd-imgui-node-editor)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/thedmd-imgui-node-editor.svg)](https://hysenlabs.com/projects/thedmd-imgui-node-editor)

Was this useful?