Show Path

Once you've chained a few Add Folder nodes together, you can't actually see what path you've built - the PATH type doesn't render anything on its own. Show Path exists to fix that: drop it anywhere in the chain and it renders the resolved path as text right on the node, so you can sanity-check your folder structure before you burn GPU time generating a batch into the wrong place.

What it's really for

This is a debug node, not a functional one - it doesn't transform the path, it just displays it. Wire it as a spur off any point in your Create Project Root → Add Folder chain to confirm what's actually being built. It's the fastest way to catch a typo'd folder name or a wrong output_path_generation choice (relative vs. absolute) before it produces a surprise folder structure on disk.

The inputs and outputs that matter

Just one required input:

• path - the PATH value you want to inspect.

And one output, a STRING - the same text rendered on the node is also passed through as an output, so you can technically use Show Path mid-chain without dead-ending your graph, though most people use it as a spur for inspection rather than a pass-through link. It's also flagged as an output node in the pack's own schema, meaning it's meant to be an endpoint you look at, not something you're required to route further.

A known bug worth knowing about before you rely on it

The pack's own README flags this directly, and it's worth quoting because it'll save you a confused ten minutes: "Show Path seems to always hold first value it receives and then will render a second text window with any updated values. Not sure why this is happening. Appears to be something related to PATH being a custom type." In practice, that means: the first time you run your workflow, Show Path displays correctly. Change something upstream and re-run, and instead of updating cleanly, it can end up showing you the old value alongside a second text box with the new one - or otherwise behaving like it's stuck. This is an open, acknowledged issue in the pack, not something you're doing wrong.

The practical workaround: don't trust Show Path as your only signal on a re-run. If a path looks stale after you've changed an upstream node, queue the run again, or reload the workflow, before assuming your path logic is broken.

How to install it

ComfyUI Manager: search ComfyUI-Path-Helper, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/Billius-AI/ComfyUI-Path-Helper

Restart ComfyUI. Nothing to configure, no pip requirements, no models - the whole pack is Python standard library.

Common issues & troubleshooting

The displayed path doesn't match what I expected after changing an upstream node. This is very likely the known first-value-sticks bug described above, not a mistake in your path logic. Re-run the workflow (or reload it) before you go hunting through your Add Folder chain for a bug that isn't there.

Nothing displays at all. Confirm the path input is actually wired to a real PATH output - Create Project Root or an Add Folder node - and not left dangling. Show Path has nothing to render if it's not receiving a value.

I want to check a plain string, not a path. Show Path only accepts the PATH type. For a regular STRING - say, the output of Add File Name Prefix, or any other string value in your graph - use the sibling node Show String instead, which does the same on-canvas preview job for plain text.