Nodes/SD Slicer/SD Slicer — Save Model
ComfyUI Node

SD Slicer — Save Model

Turn that merged model into an actual checkpoint file

By kuschanow·Created about a month ago·Updated about a month ago· 0
SD Slicer — Save Model
  • model
  • clip
  • vae
  • clip_vision
    filename_prefixsd_slicer/model
    destination

    So you've built the perfect merge in your graph - per-block weights tuned, formula dialed, output looking exactly how you want. Now what? Keep the workflow around forever and hope you never reinstall? No. You write it to disk. SD Slicer - Save Model is the node that turns the merged MODEL into a real checkpoint file, using ComfyUI's own native writer so the output is byte-for-byte the same kind of file the built-in "Save Checkpoint" produces.

    This is the end of the line for the pack's Layer Merge, and it's deliberately boring in the best way: take a MODEL in, get a file out, no surprises. If a full checkpoint is more than you need - say you only want the diffusion weights, or you're saving a VAE or a merged LoRA instead - that's what the pack's other save node, Save (any), is for.

    Inputs and fields

    • model (required) - the merged MODEL, typically straight out of Layer Merge.
    • clip, vae, clip_vision (optional) - connect only what your model actually has. Omit all of them and you save the diffusion model on its own.
    • filename_prefix - default sd_slicer/model. ComfyUI appends a counter, so you won't overwrite earlier runs.
    • destination - one of three: output (safe - never touches your models list), models/checkpoints, or models/diffusion_models.

    The destination choice is the one that matters. output is the don't-break-anything default: your file lands in the output folder and stays out of the loaders' way. Pick models/checkpoints and the file shows up in your Checkpoint Loader dropdown immediately, which is usually what you actually want once you've confirmed the merge is good. models/diffusion_models is for when you're loading with a separate UNet loader (the SD3/Flux style) rather than a full checkpoint.

    How it works

    The node delegates to the same save_checkpoint helper that ComfyUI's own checkpoint-saving and model-merging nodes use, so there's no custom serialization to go wrong - the file is written exactly as ComfyUI would write it, prompt metadata and all. There's one honest caveat in the README: this is version-sensitive glue, so it depends on ComfyUI being reasonably current. If your install is ancient and the writer isn't found, the node errors cleanly instead of silently doing nothing.

    What to watch out for

    The classic beginner trap is saving a model with only some of its parts connected. If you're blending SDXL checkpoints and you connect just model, you get a diffusion-model-only file - which won't stand alone as a checkpoint. Connect the CLIP(s) and VAE too if you want a file you can drop into a stock Checkpoint Loader. And keep the merge's compatibility rules in mind even at save time: the file is only as good as the blend that made it. Same install as the rest of the pack - ComfyUI Manager (search "SD Slicer") or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/kuschanow/ComfyUI-SD-Slicer
    

    then restart. No extra dependencies, no model downloads. Save the file, delete the workflow, and the merge lives on as a normal checkpoint you can load like any other.

    CategorySD-Slicer

    Inputs (6)

    NameTypeDefaultDescription
    modelMODEL
    filename_prefixSTRINGsd_slicer/model
    destinationCOMBO3 options: output, models/checkpoints, models/diffusion_models
    clipoptCLIP
    vaeoptVAE
    clip_visionoptCLIP_VISION

    Outputs (0)

    No outputs