← All work

ComfyUI node set

A layer editor that runs inside ComfyUI

The edit loop was in the wrong app.

A layered image editor that runs inside ComfyUI. Built solo, with AI assistance. 183 stars on GitHub, MIT licensed.

Install

  1. Clone or copy this folder into ComfyUI/custom_nodes/comfy_canvas.
  2. Restart ComfyUI.
  3. Add Comfy Canvas to your graph.
  4. Optionally add Comfy Canvas Output so the right pane shows the latest result from the workflow.

No separate server, no second browser tab, no CDN. The frontend is self-contained in the repo, including a vendored PIXI runtime.

Two nodes, one session

Comfy Canvas opens the editor as an in-app overlay and outputs IMAGE, MASK, session_id and prompt. Sessions stay attached to the node through session_id, so the layer stack survives a reload and a workflow re-run.

Comfy Canvas Output closes the loop: it pushes the latest generated result back into the same session as a new layer, so you can keep editing the result instead of exporting it and starting again.

What is in the editor

How it compares to the built-in MaskEditor

The MaskEditor is a step, not a workspace. It gives you a mask for the node in front of you and forgets it when the node runs. Comfy Canvas keeps a document: the layers persist, the masks stay per-layer, and the prompt stays where you left it. The practical difference shows up on the third revision, when the layer you liked still exists.

Specs

Version1.0 (fully local)
NodesComfy Canvas, Comfy Canvas Output
LicenceMIT
RuntimeRuns inside ComfyUI; no server process
FrontendSelf-contained, vendored PIXI, no CDN
GitHub184 stars, 12 forks
Comfy Canvas editor open inside ComfyUI with the layer stack, paint tools and prompt dock visible
The editor as an in-app overlay: layer stack right, tools left, prompt dock along the bottom.
ComfyUI workflow graph showing Comfy Canvas feeding a sampler and Comfy Canvas Output returning the result
A real graph: the canvas node inline with the sampler, Output returning the result as a new layer.

Questions

Does Comfy Canvas need a separate server?

No. Since v1.0 it runs entirely inside the ComfyUI tab. Older builds needed a Flask server and a second browser tab; that is gone.

Does it work with any ComfyUI workflow?

Yes. The node sits in the graph like any other. Adding Comfy Canvas Output is optional and only controls whether the latest result is pushed back into the canvas.

Is the layer stack saved between sessions?

Yes. Sessions are keyed by session_id on the node, and layer data, prompts and editor state persist under ComfyUI user data. There is autosave during editing and a save on close.

Are the masks destructive?

No. Masks are per layer and non-destructive, and they are edited on layer thumbnails rather than by painting over the image.

What does it cost?

Nothing. MIT licence, source on GitHub.

Problem

ComfyUI generates fast and iterates slow. Repaint a hand and you export the image, open a paint app, re-import it, re-run. Every version you liked comes back flattened — the layer you actually wanted is gone.

What I did

Put the editor inside the tab. Two nodes, sessions bound to the node, a real layer stack, non-destructive per-layer masks, brush, bucket, marquee, blend modes, and a prompt dock that remembers what you typed. Output pushes back in as a new layer.

What happened

v1.0 went fully local — no Flask server, no second browser tab, no split workflow. It is in other people's pipelines now, and they file issues about it.

183GitHub stars
12forks
2ComfyUI nodes
v1.0fully local

Open on GitHub →