SpectralVAEDetailer (alias)

Short version: SpectralVAEDetailer and LatentDetailer are the same node, and you'll see both in your node menu. If you came here from a saved workflow, nothing is wrong with your graph. Pick whichever name you like - the behavior is identical.

Here's why the confusion exists. This pack started life in December 2025 as ComfyUI-SpectralVAEDetailer, and the node's original name was SpectralVAEDetailer. In v0.3.0 (late December 2025) the author renamed the whole project to ComfyUI-LatentDetailer and gave the node the clearer name LatentDetailer - but kept the old name registered as an alias so nobody's existing workflows broke. In the actual source, SpectralVAEDetailer is the base class that contains all the logic, and LatentDetailer is a one-line subclass that inherits it. ComfyUI's node mapping points both names at the same implementation, with the old one displayed as "SpectralVAEDetailer (alias)".

What it does

A latent-space detail pass that slots between your KSampler and the VAE Decode. It runs your UNet one or more times at a chosen point in the denoise schedule (the sigmas input, default 0.40), computes the denoised estimate, extracts its high-frequency structure, and reinjects it into the latent - plus optional micrograin, bloom, color drift, and chromatic aberration. All in latent space, never decoded to pixels, so it's fast. It's aimed at SDXL photoreal work and the "everything looks too plastic" problem, though the author says it's model-agnostic if you re-tune the starting parameters.

The inputs and outputs are exactly the ones documented for LatentDetailer: model, latent, positive, negative, sigmas, detail_strength, hires_scale, noise_scale, bloom_strength, and about thirty more optional knobs; one LATENT output that feeds your VAE Decode. See the LatentDetailer writeup for the full mechanism, the inputs that matter, and the troubleshooting section - all of it applies here verbatim.

Install

Since both names ship in the same pack, installing either one gives you both. ComfyUI Manager, search "LatentDetailer", or:

cd ComfyUI/custom_nodes
git clone https://github.com/SparknightLLC/ComfyUI-SpectralVAEDetailer

Then restart ComfyUI. No dependencies, no model downloads, no requirements.txt - the only thing it needs is the same checkpoint and conditioning you're already feeding your sampler.

The one thing to watch

Old tutorials and Reddit posts from the original launch will say "SpectralVAEDetailer" and point at the old repo URL. Both still work: the clone command above is the old repo name and it's still the URL ComfyUI tracks, while the README and Registry entry now live under "LatentDetailer." If you're ever confused about whether a saved workflow is using the right node, the answer is yes - they're the same code.