Camera_Angles Styler

This one's actually useful. Camera_AnglesStyler is a 39-entry dropdown of shot angles - dutch angle, fisheye, from above, from below, from behind, panorama, POV, perspective, upside-down, sideways. Camera position is one of those things that changes an image completely and that people constantly forget to prompt, so having a menu of angle words to flip through is a legitimately handy way to break out of the default eye-level front-on shot the model gives you by default.

Don't confuse it with CameraStylerAdvanced, which is a list of physical camera bodies (Canon this, Sony that). This node is about where the camera is pointed, not what camera it is. Fair warning: a few of the 39 entries lean toward booru/NSFW framing (there's an "upskirt" angle in there) - it's a Danbooru-flavored tag list, so scroll with that in mind.

How it works

MileHighStyler is a fork of SDXL Prompt Styler. Each angle is a JSON template with a {prompt} slot; the node drops your text_positive in and wraps the angle phrase at a strong weight (~2.0). The nice thing about angle words specifically is that they're plain descriptive English - "from below," "dutch angle" - so they survive well as literal text even where the weighting doesn't apply. Output is a rewritten prompt string into your CLIP Text Encode; nothing touches the model.

The inputs and outputs that matter

• camera_angles - the 39-entry dropdown. none is the off switch.
• text_positive - your subject; the angle gets welded onto it.
• text_negative - optional negative text.

log_prompt prints the finished prompt so you can confirm which angle phrase landed. Outputs are text_positive and text_negative strings, into a CLIP Text Encode.

Installing it

ComfyUI Manager: search ComfyUI_MileHighStyler, install, restart. Or:

cd ComfyUI/custom_nodes && git clone https://github.com/TripleHeadedMonkey/ComfyUI_MileHighStyler

then restart. No models, no requirements.txt, no dependencies - Python and JSON. Nodes appear under ali1234/stylers.

Where people get burned

• Angle words fight your composition guides. If you're also running a ControlNet pose or a fixed composition, a strong "from below" can pull against it. Keep the seed fixed and A/B - sometimes the angle wins, sometimes the ControlNet does.
• Extreme angles need model support. "Fisheye" and "upside-down" are ambitious; SD 1.5 fumbles them more than SDXL does. If you get a normal shot back, the model just doesn't know the concept well - not the node's fault.
• Model era. The 2.0 weighting is SDXL/SD 1.5 syntax, silently dropped on 2026 LLM-encoded models (Flux 2, Z-Image, Qwen). The angle text itself still works as plain language on those - you just don't need the weighting wrapper, so you might as well type the angle directly.
• You could type it. Like most single-menu stylers, the honest ceiling is "a dropdown instead of typing 'from below.'" Worth it for browsing angles you'd forget; not magic.