Kling 3.0 4K (BudgetPixel)

Kling 3.0 at native 4K is the node you reach for when the resolution is the deliverable. It's the top of the Kling 3.0 ladder on this pack's shelf, and its billing tells you exactly where it sits: 450 credits per second. A five-second 4K clip is over 2,000 credits. This is not an iteration node - it's a final-render node, the one you queue when the 720p draft was approved and the client wants pixels.

The feature set is the full Kling 3.0 package: text-to-video, image-to-video with a start frame and an optional end frame, any duration from 3 to 15 seconds, and optional audio that - unusual for the pack - has no price impact at 4K. So the audio toggle is genuinely free, which is a small mercy on a node this expensive. The two-frame support (start + end) is the same "choreograph a journey" control the older v2.6 Pro offered, which makes this the go-to when you need both high resolution and a pinned-down ending.

How it works

Standard BudgetPixel video flow: prompt, optional start/end frames, and the audio toggle go into the Kling 4K pipeline, the node polls until succeeded, and the finished MP4 downloads as a core VIDEO. The heavy lifting - and the heavy billing - happens server-side at 4K native resolution, so expect longer wall-clock times per job than the lower tiers alongside the bigger credit hit.

The inputs that matter

• prompt - required, multiline.
• image - optional start frame.
• end_image - optional end frame. Worth the extra thought at this price: a well-chosen end frame is the difference between a usable 4K shot and a 4K shot that goes somewhere useless.
• generate_audio - optional audio, free at this tier. The rare "why not" toggle.
• length_seconds - 3–15. The cost lever of levers at 450 credits/sec; a 15-second clip is 6,750 credits.
• aspect_ratio - framing.

Output is a single VIDEO.

Install

Manager (search "BudgetPixel") or:

cd ComfyUI/custom_nodes
git clone https://github.com/budgetpixel-ai/comfyui-budgetpixel.git
pip install -r comfyui-budgetpixel/requirements.txt

Restart, set BUDGETPIXEL_API_KEY or budgetpixel.json ({"api_key": "bpx_live_..."}) in the pack folder. No model files; requests is the only dependency.

Where people get burned

There is exactly one way to lose money on this node, and it's queueing it without checking the price first. The Cost Estimate node with {"length_seconds": N, "resolution": "4K"} should be mandatory before you queue anything here - the sticker price is 450 credits/second and the discounts on your plan are the only thing between you and sticker shock. Second, use the lower tiers for drafts: there's no reason to spend 4K money to test a motion concept when Standard or Turbo exists, and the two-frame + audio feature set is shared with cheaper siblings. Third, be realistic about wall-clock time - 4K native generation is slower server-side, so budget for the wait along with the credits. Save the node for the shot that has to be 4K, and it'll earn the premium.