zhenzhen-upscaler-lowprice

Video upscaling is the least settled of the three upscaling jobs in the KB's framing - "more pixels over time," where every frame has to agree with its neighbors. Local video upscalers are either datacenter-grade VRAM hogs or per-frame traps that jitter on fine patterns. Comfly_zhenzhen_upscaler_lowprice sidesteps the whole question: you hand it a video (connected or by URL), pick a target from 720p to 4K, and a cloud model does the temporal upscaling and hands back a VIDEO. No 24GB card, no overnight render.

It's part of the domestic-storefront low-price family (it shipped in mid-July alongside a FlashVSR video-upscale node for the overseas tier - this one's the cheap path). Cloud inference, per-minute pricing, and your GPU stays idle.

How it works

Give the node a video and a target resolution, and it submits an upscale job, polls until it's done, and returns video, video_url, task_id, and response. Simple enough that it's almost anticlimactic.

Inputs:

• input_video (VIDEO) - connect any video output in your graph (another generation node, a loaded clip). This is the clean path.
• video_url - a public MP4 URL. The tooltip's advice: leave it empty when input_video is connected.
• resolution - 720p / 1080p / 2k / 4k. Upscaling to a lower resolution than the source makes no sense; this is a "give me bigger" dial, so start at 1080p and only push to 4K when the source deserves it.

Installing and setting up

Install through ComfyUI Manager (search Comfyui-zhenzhen) or:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/Comfyui-zhenzhen

Restart ComfyUI. No model downloads. Connect the Comfly Seedance2 Low Price Settings node's api_config, or set SEEDANCE_API_KEY - the standard family plumbing.

Troubleshooting

The family tripwire applies: no api_config, "empty api_key." Specific to upscaling, three things. First, garbage in, garbage out - a cloud upscaler can't invent detail that a soft 720p source never had; it smooths and hallucinates texture like any generative upscaler, so judge the output honestly rather than expecting miracles. Second, watch the length of your clip; the bill scales with duration as well as resolution, so upscale the final cut, not every draft. Third, if you connect both input_video and video_url, the connected video wins - clear the URL to avoid the "why did it upscale the old file" confusion. skip_error is available for batch runs.

This is one of those nodes that's quietly the pack's best value: video upscaling is exactly the job most people's hardware can't do well, and renting it by the minute beats buying a card for it.