Help center
Tutorial Intermediate

Clean screenshots and renders

Take crisp Studio shots and fix the usual render problems: hidden UI, F9 vs F11, depth of field, transparent backgrounds, SSR and SEGI.

A great pose and a great lighting setup can still end up looking flat or broken in the final image if you capture it the wrong way. Studio gives you two very different capture modes plus a handful of settings that only matter once you actually press the button, and most “why does my render look wrong” problems trace back to one of them.

1. Hide the interface first

Press Space to toggle the entire Studio UI on or off in one press. It hides every panel, not just the ones in your immediate view, so do it right before you frame the shot rather than trying to nudge windows out of the way.

The move/rotate axis gizmo on your selected object does not go away with Space. Press Q to toggle it separately. If you’ve hidden the UI and there’s still a colored cross sitting on your subject, that’s what you’re looking for.


2. Choose F9 or F11

F9 is a quick in-viewport screenshot. It captures exactly what you’re already seeing on screen, so lighting, depth of field, and anti-aliasing all match the live view by definition.

F11 triggers a full render at an upsampled resolution, which is what you want for a high-resolution export or a print-quality shot. It works with either DHH or Graphics mod driving your post-processing, and output is saved under UserData/cap by default.

The gotcha: an F11 render doesn't reuse what's already on screen, it recalculates every post-processing effect from scratch at the new resolution. That's why depth of field, bloom, and anti-aliasing can look weaker, sharper, or just different from what you saw live. The fix is to set your render/screenshot resolution to match your actual screen resolution before capturing, which keeps the recalculated effects lined up with what you expect.

3. Blur the background properly

Depth of field comes from the Depth of Field effect in Graphics mod, not from a Studio-native slider, so make sure Graphics mod is enabled before you look for it. See lighting with the Graphics plugin if you haven’t set it up yet.

Don’t chase focus by sliding numbers around blindly. Instead, use the focus marker: uncheck auto-focus, select the object or character you actually want sharp, then re-check auto-focus so it locks onto that target instead of whatever it defaulted to. From there, adjust the aperture and focal length sliders to control how strong and how wide the blur is.

Your depth of field setup is saved inside the scene as part of the graphics preset, so it travels with the scene file, you don’t need to redo it every time you reload.


4. Export a transparent PNG

Open the Screenshot Manager (F1) and enable the Alpha option before capturing. This works for both a quick F9 shot and a full F11 render.

Set the background color to black before you export with alpha enabled. Any other background color leaves jagged, visibly aliased edges around your subject once the alpha channel is applied. Black gives you a clean cutout.

Common render problems

SymptomFix
Cloth or hair flickers, but only when recording videoDisable SSR (screen-space reflections) in Graphics mod
A 4K F11 render comes out broken, blotchy, or garbledDisable SEGI (global illumination) in Graphics mod
Depth of field looks weak or missing in the renderMatch render resolution to your screen resolution (see step 2)
F11 comes out solid black or fully transparentIn Screenshot Manager, disable Alpha or set transparency to Composite instead of none
If a render looks visibly different in quality from your live view even with matched resolution, check your anti-aliasing mode. Some AA methods are tuned for one capture mode over the other, so pairing the wrong AA with the wrong hotkey is a common source of extra blur or shimmer between F9 and F11 shots.

Getting a cinematic look with less manual work

You don’t need to hand-tune a dozen sliders to get a graded, filmic look. A recent Graphics mod build’s color grading and bloom presets do most of the heavy lifting on their own, layered on top of whatever lighting setup you’ve already built. Start there before you go digging through individual tone curves.

If skin tone looks off once grading and bloom are active, that’s usually a shader mismatch rather than a grading problem, check gray or mismatched skin. And if Graphics mod’s own panel isn’t behaving (menu won’t open, settings won’t stick), see the Graphics menu won’t open.


What next

Once your shots are clean, pair this with lighting with the Graphics plugin for the full post-processing setup, and camera work in Studio for framing and composition. If you’re capturing motion rather than stills, most of the same UI-hiding and resolution-matching advice carries over.

Feedback

Did this guide help? Give it a like, no account needed.