Updating ComfyUI does not necessarily update its template library at the same time. ComfyUI documents comfyui-workflow-templates as a separate dependency, so a newly announced template may be missing until that package is updated. A workflow you have already loaded is a graph in the editor; the documentation does not promise that changes to the template source will flow into that graph, or that your edits will be merged into a newer template. Treat the template as a starting point and save your edited graph as its own workflow.
Separate the application update from the template update
The Templates browser lists workflows supported by ComfyUI as well as examples supplied by custom nodes. Its contents therefore do not all necessarily come from one source. For official templates, the documented package to check is comfyui-workflow-templates. The Templates guide says that after updating ComfyUI, you may also need to update the corresponding dependency, and points to ComfyUI/requirements.txt for version information. ComfyUI’s Templates guide
Do not infer that the main application update failed just because a particular new template is absent. First establish whether the version of the template dependency in your installation has changed. The documentation does not specify that every installation updates this package automatically, nor does it give one update procedure for every installation type. Use the official ComfyUI update instructions for the installation you actually use; avoid applying commands for a different setup.
Check why the template is missing
Work through these checks in order:
- Open Templates from the sidebar or choose Workflow → Browse Workflow Templates. Confirm you are looking in the template browser, not the saved-workflows list. ComfyUI documents those as separate areas.
- Identify which template you expect and whether it is an official template or an example provided by a custom node. A missing custom-node example may have a different cause from a missing official template.
- Check the installed
comfyui-workflow-templatesversion in the current installation and compare it with the target version or update guidance. If you retained an earlierrequirements.txt, you can also compare the before-and-after versions. Note the frontend package and embedded-docs versions shown there: the documentation says these three dependencies may be upgraded together. - If the template dependency is behind, follow the update instructions for your install type. Then revisit the Templates browser and check whether the expected entry appears. The documented refresh button belongs to the Workflows panel and resynchronizes saved workflows from disk; it is not documented as a template-browser refresh control.
- If it is still absent, verify whether it belongs to a custom node and whether that node is installed. Record the template name, dependency versions, and where you looked before seeking help; this narrows the issue without treating a missing entry as proof that your graph or model files are broken.
Keep your edits in a separate workflow
Loading a template gives you a workflow to work with. The docs describe templates and persisted workflows as separate parts of the interface: templates are browsed separately, while saved workflows appear in the Workflows panel and can be opened, renamed, or duplicated. They do not describe automatic two-way synchronization between a template and a graph already open in the editor. ComfyUI’s Workflows guide
For a practical handoff, load the template, make your changes, and save the result as a distinct workflow with a name that identifies your project or purpose. Confirm that the copy appears under persisted workflows in Workflows, close the current graph, and reopen that saved copy before checking the specific prompt fields and node connections you changed. If a suitable saved workflow already exists, the Workflows panel documents a Duplicate action; use that when you want a separate copy before editing. Keep a short source note alongside the workflow name or in your own project records, such as the template title and the template-package version you checked. That note is a tracking practice, not a ComfyUI feature required by the documentation.
Do not rely on reopening the template later to preserve edits made to an unsaved graph. The Workflows panel marks modified or unsaved open graphs with *, and its saved-workflow list is distinct from the Templates browser. A graph being open, or a template entry showing up again, is not evidence that your personal changes were persisted.
Diagnose with a small version record
The following is a hypothetical example, not a tested installation. Suppose a creator updates ComfyUI, expects an official template called “Example Image Workflow,” and finds no such entry. Their version record says the template package is still at 0.1.51, while the updated installation’s requirements.txt specifies 0.1.52. They update dependencies using the instructions for their installation, reopen the template browser, and find the entry. They then load it, change a prompt and a node connection, save it as Project Image Draft, close it, and reopen that saved workflow. The expected acceptance result is that the named workflow opens and both intended edits remain. This example illustrates a check; it does not establish that those version numbers apply to your installation.
| Check | Hypothetical observation | Next decision |
|---|---|---|
| Template location | Entry absent from Templates; do not treat its absence from Workflows alone as proof that the template is missing | Continue with dependency checks |
| Dependency version | Installed version 0.1.51; requirements specify 0.1.52 | Update according to installation instructions |
| Saved copy | Project Image Draft appears under persisted workflows | Reopen that copy for acceptance |
| Edit retention | Prompt and connection remain after reopening | Personal changes are saved in the copy |
| Entry still missing | Versions match, but expected entry is absent | Check whether it is a custom-node example; collect versions and seek installation-specific help |
If dependency versions appear current but the template is absent, check the custom-node category and installation state if applicable, then follow the official update guidance or report the exact versions and missing entry. The available documentation does not guarantee when every announced template becomes available, that template changes merge into open graphs, or that personal modifications are recoverable without saving. It also does not specify one universal refresh action for the template browser.
Common questions
Is a missing model the same problem as a missing template? No. A template not appearing concerns the template listing and its source or dependency. Missing model files are checked when loading a template and can be surfaced through affected loader nodes and the Errors panel.
What should I record when asking for installation-specific help? Record the template name, whether it is official or supplied by a custom node, the relevant dependency versions, and where you looked.
What if the saved copy is missing an edit after reopening? Confirm that you saved the graph and reopened the persisted copy rather than the original template, then report the exact missing field, node, or connection with the installation details.
Sources and next step
- Templates - ComfyUI Built-in Workflow Templates
- Workflows Sidebar - Saved and Open Graphs
- How to Update ComfyUI - ComfyUI
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the photo editor. The external software controls discussed above belong to their respective products.