WK Resolution Preset (Legacy)

Read the name first

The display name is WK Resolution Preset (Legacy), and that's not marketing modesty - it's a deprecation notice. The pack's own source comment says it exists so that "existing serialized workflows continue to load with their original widget layout." WorkspaceKit has a second resolution node, WK Video Resolution, which uses ComfyUI's official megapixel formula, and that's the one you should be building new graphs with. This one is here for the old graphs.

If you're here because a workflow you downloaded demands WKResolutionPreset, you're in the right place. If you're choosing a resolution node from scratch, skip to the other one and come back only if you like long edges.

How it works

Two numbers come out: width and height (INT), plus a resolution string like "1024 × 576" for slapping into a filename or a note.

The math is a long edge system, not a pixel budget. resolution_level picks a target for the longest side: 1K = 1024, 2K = 2048, 3K = 3072, 4K = 4096, 6K = 6144, 8K = 8192. aspect_ratio decides the other side:

• Square (■ 1:1) sets both sides to the long edge - 1K gives you 1024×1024.
• Portrait ratios (▯ 9:16, 4:5, 3:4, 2:3) put the long edge on the height.
• Landscape ratios (▭ 16:9, 3:2, 4:3, 5:4, 2:1) put it on the width.

The short side is then computed from the ratio and rounded to the nearest multiple of 8, floored at 8. So 1K at 16:9 is 1024×576 - 0.59 megapixels, roughly half of what most people assume "1K" means. 2K at 16:9 is 2048×1152, about 2.36 MP. The label describes the long edge; the pixel count swings with the ratio. That's the whole trap in one sentence.

use_custom bypasses all of it: flip it on and custom_width / custom_height are returned verbatim, each clamped to 1–16384 and validated as whole numbers. Both fields are always visible on the node, which is why people flip the boolean, leave 1024×1024 in the boxes, and wonder why their 16:9 preset produced a square. It does exactly what you told it to.

Aspect options are the ten you'd expect - 4:5 up through 2:1. There is no 21:9 here; that one only exists on the newer resolution node. Unknown values raise "Unknown aspect ratio" or "Unknown resolution level" rather than silently falling back, which is the right call for a legacy contract.

Picking a level without hurting yourself

The KB is blunt about native resolution: generating far off a model's trained size gives you duplicated anatomy and stretched limbs - "a model trained on 1024×1024 trying to make images at ridiculously different aspect ratios" is still the most-upvoted version of that complaint. What changed in 2026 is that most current models take any size in a one-or-two megapixel band and degrade softly instead of breaking. So:

• SDXL-era checkpoints want one of the trained ratios (1024×1024, 1152×896, 1216×832, 1344×768, 1536×640). This node gives you 1024×1024 and ▭ 3:2 at 1K for 1024×683, not 1152×896. If you're on SDXL, prefer custom values.
• Flux and friends want dimensions divisible by 64, not 8. Set custom or reach for WK Video Resolution and set multiple to 64.
• Don't generate at 1920×1080 just because the video you want is 1080p. Generate at a sane size and upscale.

2K at 16:9 (2048×1152) is a perfectly sane ~2.4 MP landscape target for a modern model. 4K and above are upscale-pass territory, not first-pass territory.

Install

Manager: search WorkspaceKit or comfyui-workspacekit, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/ZiYao00/ComfyUI-WorkspaceKit.git
cd ComfyUI-WorkspaceKit
python -m pip install -r requirements.txt

Windows portable, run from the ComfyUI root:

.\python_embeded\python.exe -m pip install -r .\ComfyUI\custom_nodes\ComfyUI-WorkspaceKit\requirements.txt

The pack's only listed dependency is send2trash, used by the sidebar's trash; there are no model files to download and nothing here touches torch. This particular node is pure arithmetic and has no frontend code of its own, so it works in both the legacy canvas and Nodes 2.0 - one less thing to worry about given how badly the frontend rewrite treated third-party packs.

Where it bites

• The output is square and you picked 16:9. use_custom is on. Turn it off.
• "Why is my 1K smaller than 1 megapixel?" Because 1K is the long edge. This is documented behaviour, not a bug.
• A workflow arrives with red widgets or a validation error. Someone saved a value the legacy contract doesn't accept, or a newer node got swapped in. Re-pick the aspect ratio and level manually.
• Beta context. WorkspaceKit is public beta and the README asks you to back up workflows, settings and templates before using it in a primary install. This node is a stable, isolated calculator; the sidebar around it is what's still in motion.