SeedVR2 Tile Splitter (Upscale Factor)

Here's the thing about the base SeedVR2TileSplitter: it makes you think in megapixels, which is exactly how the model thinks but not how people think. When you want an image to come out twice as big, you say "2x," not "set tile_upscale_mp to four and hope." SeedVR2TileSplitterByFactor is the version of that splitter that takes the input you actually have in your head.

It's one of the three alternative splitters BacoHubo added in v1.1.0 after the community asked for a way to specify a concrete final output size - the author's "I added 3 new nodes based on y'alls feedback" release thread was the second-highest upvoted thing he'd published. Same tiling machinery as the base node, same outputs, one swapped parameter.

The one parameter that matters

• upscale_factor - the multiplier. 2.0 doubles width and height (so 4× the pixels); 1.5 gives a 1.5× output; maxes at 16. Default 2.0.

Everything else is the shared splitter set: tile_size_mp (0.5–1.0 on 8GB), overlap_percent (10 default), feather_blend (1.0 smooth). The node computes the upscale target from your factor instead of from a megapixel figure, and - the part that makes the factor real - it stamps exact target output dimensions into the metadata, so the stitcher does a final resize to land precisely on your multiplier. The base MP node returns whatever SeedVR2 happens to produce; this one guarantees the 2× you asked for.

How it slots in

Outputs are tiles, tile_metadata, and resolution - wire them exactly like the base splitter: tiles to SeedVR2's image input, resolution to SeedVR2's resolution input, tile_metadata to the stitcher. Set max_resolution to 0 on the SeedVR2 node so it stops second-guessing your target. Swap this node in for the base one and you're done; the pack's own docs literally say the alternative splitters are drop-in replacements.

Install and requirements

ComfyUI Manager (search SeedVR2 Tiler) or:

cd ComfyUI/custom_nodes
git clone https://github.com/BacoHubo/ComfyUI_SeedVR2_Tiler

No dependencies beyond what ComfyUI ships, but the numz SeedVR2 node and its weights are required - run FP16. The pack adds no models of its own.

When to grab it (and when not to)

Reach for this when you think in ratios - "make it 1.5× for the header," "2× for the print" - or when you're stacking multi-pass runs and want each pass's factor explicit. Skip it in favor of the base node for fully automated pipelines: the author's own take is that the base node stays best for automation and for making sure you never hit an OOM, since it's the simplest thing to script. And if your final size is a hard requirement like "4K wide," the Longest Edge or Shortest Edge splitters are the better fit - a factor only gives you a ratio, not a resolution.