MiniMax H3 Reference Sheet Visual Reference (Legacy)

A Reference Sheet is a library; this node is the checkout counter. It grabs the image currently selected in a Reference Sheet's gallery, assigns it a workflow-specific role, retention, and shot scope, and drops it into the same reference_context chain used by the ordinary Visual Reference nodes. The sheet stays pristine - the role you choose here is about this workflow, and it's never written back into the saved library.

That separation is the design's quiet strength. You can save one photo of your character once, then use it as an exact first frame in one project and as reusable identity in the next, without maintaining two library entries.

What you set

• reference_sheet - connect the Reference Sheet node's reference_sheet output; its gallery selection is used automatically.
• reference_role - the job, from the same 14 choices as the standalone Visual Reference Role node: exact first/last frame, identity, object, scene, style, keyframe, storyboard, motion, camera, edit source, and more. Endpoint roles route to Image to Video; reusable roles route to Ref2VA.
• retention - Auto, fully_preserved, partially_preserved, attribute_transfer, or weak_reference. Auto picks conservatively per role.
• content_group - optional; blank uses a stable sheet/group-derived key for reusable Subject roles. Give related roles on different assets the same value to merge them into one <Subject N>.
• transfer_target - destination content group, only for attribute_transfer.
• shot_scope - workflow-only; intentionally not saved in the sheet.
• notes - workflow-specific instructions about what to preserve, transfer, ignore, or change.
• analysis_long_edge - the max long edge of the private Qwen analysis copy (768 default). H3 always receives the original saved image; this only bounds what the LLM looks at.

The optional previous_context chains from a preceding sheet/Visual Reference node to preserve native order. The optional role_bindings input accepts a finished Visual Reference Role chain when this saved image has multiple jobs - it replaces the single role/retention/group/scope widgets above.

Outputs

reference_context chains to the next sheet or ordinary Visual Reference; the final context fans out to both the Prompt Guide and the Prompt Enhancer. h3_media is the original saved image for the native H3 socket named in routing_report. routing_report tells you the sheet asset, the resolved role, the semantic H3 label, and the exact socket route - read it once before queueing a reference-heavy render.

Installing

cd ComfyUI/custom_nodes
git clone https://github.com/ethanfel/ComfyUI-MiniMax-H3-Guide

Restart ComfyUI; it appears under MiniMax H3/Reference Sheets. No Python dependencies. You need ComfyUI with native MiniMax H3 support, and the sheet's gallery relies on the pack's bundled web assets, so don't strip those out.

Where people get burned

The usual mistake is treating analysis_long_edge like an output resolution. It isn't - the H3 generator gets the original pixels; you're only capping what Qwen sees for its description. Crank it down if you want faster enhancement, not better output. The bigger one is forgetting that retention/transfer relationships must resolve inside the final context: an attribute_transfer with no visible non-transfer binding carrying the destination group leaves the transfer hanging. And if you load a sheet and nothing happens, check the gallery selection - the node consumes whatever is selected at queue time, not whatever you think you clicked.