ComfyUI Node

HT Layer Export

Write your layer stack to a real PSD (or multi-page TIFF)

By ArtHommage·Created 2 years ago·Updated about a year ago· 4
HT Layer Export
  • layer_stack
    output_pathoutput.psd
    formatpsd

    The companion to HT Layer Collector, and the node that makes the whole layer-stack idea real. Collector builds the stack in memory; this node writes it to disk as a genuine layered file - PSD by default, or a multi-page TIFF - with layer names and alpha preserved. When you open the result in Photoshop, Krita, or Clip Studio, your separate layers are still separate. That's the payoff: a compositing workflow that ends in an editable file instead of a flattened image.

    How it works

    It takes a LAYER_STACK (which you only get from the collector), an output_path (default "output.psd"), and a format choice of psd or tiff. It's an output node - is_output_node is true, so it's a terminal in the graph - and it returns nothing; the file just appears where you told it to.

    • PSD uses psd-tools to build a proper Photoshop document: one layer per stack entry, names intact, RGB color mode, and an alpha channel attached when the collector recorded a mask for that layer.
    • TIFF uses tifffile to write a multi-page TIFF with the layers as pages - a format some pipelines and print workflows prefer over PSD.

    Both branches do the BHWC → PIL conversion the pack standardizes on. Since it's an output node, you should set output_path to an absolute path or a folder you know exists; the node won't necessarily create parent directories for you, and "output.psd" lands wherever ComfyUI's working directory points unless you say otherwise.

    The workflow shape

    Background collector → Subject collector → HT Layer Export → /path/to/art.psd
    

    A few things to know before you wire this up:

    • Your layers won't auto-align. Whatever sizes you fed the collectors is what lands in the PSD. If the subject layer is a different resolution than the background, that's what you get - normalize sizes upstream.
    • The stack is single-purpose. Only collector output feeds this node, so the pair is self-contained. That's a feature (no version skew with other packs' types) and a limitation (nothing else can feed it).
    • psd-tools matters. If the import fails at ComfyUI startup, the pack's dependency check will warn you; make sure pip install -r requirements.txt actually ran, since psd-tools>=1.9.24 and tifffile live there.

    Installing

    Standard HommageTools install:

    cd ComfyUI/custom_nodes
    git clone https://github.com/ArtHommage/HommageTools.git
    cd HommageTools && pip install -r requirements.txt
    

    restart, or Manager → "HommageTools for ComfyUI". No model downloads.

    The honest take

    If you're doing serious multi-layer compositing in ComfyUI, this pair is quietly one of the best things in the pack - it's the difference between "export PNG, reassemble in an editor" and "open the PSD, everything's already there." If your output is usually a finished image, you'll never touch it. One production note: the pack is "perpetually in alpha," so if a workflow you love depends on this export path, re-verify it after updates - and keep the source images around, because a layered file is only as durable as the software that writes it.

    CategoryHommageTools/Layers

    Inputs (3)

    NameTypeDefaultDescription
    layer_stackLAYER_STACK
    output_pathSTRINGoutput.psd
    formatCOMBOpsd2 options: psd, tiff

    Outputs (0)

    No outputs