Markdown Presenter

This one does exactly one thing: you hand it a text string, it renders that string as formatted Markdown right on the canvas - headers, bold, tables, links - instead of you staring at a wall of unformatted text or a raw STRING output nobody wants to read. It ships in the same pack as CivitaiRecipeGallery, and that's not a coincidence: it exists specifically because that node (and its sibling, Model Analyzer) generate long Markdown reports, and dumping a Markdown report into a plain text box is worse than useless - you'd be reading ## and **bold** characters instead of an actual heading.

Where it fits

If you've used CivitaiRecipeGallery, its info_md output is a full write-up of a recipe - prompt, params, LoRA matches, missing-model warnings with links - built specifically to be read, not parsed. The README says as much: info_md is "recommended for MarkdownPresenter." Same story for the pack's Model Analyzer node and its full_report_md output. MarkdownPresenter is the render step for both. Wire either one in and what was a dense string becomes an actual readable report sitting in your graph.

There's nothing stopping you from feeding it anything else, either - any node that outputs a STRING, or text you type into it directly, since the field is multiline. It's a general-purpose Markdown viewer that happens to live in a Civitai-flavored pack.

The input that matters

There's exactly one: text - a multiline STRING, empty by default. That's the whole interface. No outputs come back out of it; this is a terminal node, a leaf, not something you keep wiring further downstream.

That last point trips people up who are used to every ComfyUI node having somewhere to plug into next. This one doesn't, and it's marked as an output node internally (is_output_node), which matters in a way that's easy to miss: ComfyUI executes output nodes as endpoints of the graph even when nothing downstream depends on them. You don't need to chain anything off a MarkdownPresenter for it to run - you just need something feeding text into it.

How to install it

It comes bundled with the same pack as CivitaiRecipeGallery - there's no separate install. Via ComfyUI Manager: search Civitai Toolkit (the pack's current name; the repo and class names still say "Civitai Recipe" from before the October 2025 rename) and install. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/BAIKEMARK/ComfyUI-Civitai-Recipe
pip install -r requirements.txt

Restart, and you'll find it filed under the Display category rather than Civitai - the README flags this explicitly, since it's the one node in the pack that isn't Civitai-specific.

Common issues & troubleshooting

It's showing raw # and ** characters instead of formatted text. That means the string reaching it isn't actually Markdown, or something upstream returned it as an escaped/plain string rather than the report text itself - check what's actually flowing into text before assuming the node is broken.

The node looks empty. If you're feeding it CivitaiRecipeGallery's info_md, remember that output only has real content after that node has finished its (sometimes slow, first-run) fetch and hash cycle - an empty MarkdownPresenter downstream of a gallery node that's still working through its first run is expected, not a bug in this node.

You're trying to send its output somewhere else and there's no port for it. There isn't one, by design - this is a display sink, not a transform. If you need the text itself for something else in the graph, tap it from whatever node produced it in the first place, before it reaches MarkdownPresenter.