ArtificialGuyBR

Home / Blog / Prompting and control

Camera Angle Prompts in Stable Diffusion

Camera angle and shot-type vocabulary for Stable Diffusion and SDXL prompts, with verified resolution, CFG, sampler and weighting settings.

13 sources cited Prompting and control

Camera Angle Prompts in Stable Diffusion

Adding a camera angle or shot type to a prompt is the fastest way to change how a generated image is framed. The words come from real cinematography vocabulary, and the main Stable Diffusion interfaces recognize the syntax around them. This guide lists the documented terms and separates them from the settings that govern output.

TL;DR

What camera angle words actually work in Stable Diffusion prompts?

Camera angle terms like high-angle, low-angle, bird's-eye, Dutch angle, eye-level and POV are genuine cinematography vocabulary. No source directly measures whether Stable Diffusion reproduces those effects from the words alone, so treat the list as a vocabulary to test against your checkpoint.

The "conventional effect" column describes what each angle signifies in cinema, not what a model is proven to render.

Angle termFramingConventional effect in filmSource
Eye-level (EL)Camera level with the subject, looking straight on"Little to no psychological effect" — neutralWikipedia
High-angle (HA)Camera physically higher than the subject, looking downMakes the subject "look small or weak or vulnerable"Wikipedia
Low-angle (LA)Camera below the subject, looking upMakes the subject "look powerful or threatening"Wikipedia
Bird's-eye viewCamera directly above the sceneUsed "to establish the landscape and the actors relationship to it"Wikipedia
Worm's-eye viewCamera looks up from the groundThe view "a child or a pet would have"Wikipedia
Dutch angle (canted/tilted)Camera tilted left or right"Evokes a feeling that the world is out of balance or psychological unrest"Wikipedia
Point-of-view (POV)Shows the image "through the subject's eye"Immersive, first-person viewpointWikipedia

subject eye level high angle · looking down low angle · looking up eye-level shot bird's-eye · top-down worm's-eye The angle word sets where the camera sits. Height and tilt are separate axes: a low angle can still read as eye level if the camera is close to the ground.
Camera position relative to the subject, and the prompt term for each

What is the difference between a shot type and a camera angle in prompting?

A camera angle describes where the camera sits relative to the subject (above, below, tilted); a shot type or field size describes how much of the subject is visible in the frame.

"The field size explains how much of the subject and its surrounding area is visible within the camera's field of view, and is determined by two factors: the distance of the subject from the camera ('camera-subject distance') and the focal length of the lens." — Wikipedia)

The shot-size ladder runs from farthest to closest. Each is a documented film term; model response is not independently measured.

Shot sizeWhat's in frameSource
Extreme long shotSubject extremely far away; "might not even show a person at all"; usually high angle, opens a sceneWikipedia
Long shotSubject shown but "the setting still dominates the picture frame"Wikipedia
Medium long shotSubject and setting at "about 50/50 in the frame"Wikipedia
Medium shotEmphasizes the character; "about a knees to waist up type shot"Wikipedia
Medium close-up"Waist to the chest and up"Wikipedia
Close-up"Shoulders and up or maybe a little tighter on the head"Wikipedia
Extreme close-upOne body part — "an eye, a hand or anything else"Wikipedia

extreme close-up close-up medium shot full shot wide shotBlue area = how much of the frame the subject occupies. Pair the size word with an angle word.
Shot size: how much of the subject the frame contains

Angle and shot size combine: an "extreme long high-angle shot" is a real construction in film, and you can write it the same way in a prompt. No source measures how a given model weights the combination. For broader framing choices, see our composition techniques for AI art.

How do you weight a word in a Stable Diffusion prompt?

Wrap a term in parentheses with a number to push it: (low angle:1.5) multiplies attention by 1.5. Bare () defaults to 1.1, and [word] decreases attention. This syntax is shared across the main interfaces.

"a (word) - increase attention to word by a factor of 1.1 ... a (word:1.5) - increase attention to word by a factor of 1.5 ... If the weight is not specified, it is assumed to be 1.1." — AUTOMATIC1111 wiki

ComfyUI documents the identical convention with default emphasis 1.1 (ComfyUI README). Fooocus supports (happy:1.5) and uses AUTOMATIC1111's reweighting algorithm (Fooocus). Escape literal brackets with a backslash (anime_\(character\)) when needed. For more, see prompt weighting syntax.

What resolution, CFG and sampler settings should you use for SDXL?

SDXL was trained at roughly 1024² across multiple aspect ratios. Keep CFG modest and pair DPM++ samplers with a Karras schedule. Step-count guidance beyond the sampler's artifact floor is not independently sourced, so pick steps by testing.

SettingRecommendedWhySource
Resolution1024×1024, or same-pixel aspect ratios (896×1152, 1536×640)SDXL "work best with an image size of 1024x1024"; below 512×512 "is not recommended"diffusers, ComfyUI
Aspect ratioMultiple ratios supported at ~1024²SDXL was "trained on multiple aspect ratios (not just the square aspect ratio like previous versions)"Wikipedia
CFG scale~4–10 as a working range (community-reported)High CFG "above 12 or so will result in increased sharpness, hypersaturation, and a much more literal fixation"; touchstones of 4, 7, 15, 30 reportedCivitai study
SamplerDPM++ 2M SDE with a Karras scheduleDPM++ samplers "produce visual artifacts" on SDXL below 50 steps "because the solver becomes numerically unstable"; use_karras_sigmas=True (and euler_at_final=True for DPM++2M / DPM++2M SDE) is the documented fixdiffusers
Emphasis(word:1.5), bare () = 1.1Shared syntax across A1111, ComfyUI, FooocusA1111 wiki, ComfyUI

A community article on Civitai names "DPM++ 2M SDE Karras" as its usual sampler (Civitai); the diffusers documentation confirms the sampler family is real and that on SDXL it needs the Karras schedule (or ≥50 steps) to stay stable — the schedule is not decorative. For more, see our SDXL sampler guide and SDXL resolution and aspect ratios.

Common errors and fixes

SymptomSourced causeFixSource
Visual artifacts or corrupted output from a DPM++ sampler on SDXL"The solver becomes numerically unstable" below ~50 stepsUse ≥50 steps, or set use_karras_sigmas=True (or lu_lambdas=True); for DPM++2M / DPM++2M SDE also set euler_at_final=Truediffusers
Poor, degraded SDXL output at small resolutionsSDXL expects ~1024²; "Anything below 512x512 is not recommended"Generate at 1024×1024 or a same-pixel-count aspect ratio (896×1152, 1536×640)diffusers
Hypersaturated, overly literal outputCFG set too high pushes adherence at the cost of colorLower CFG; a community study reports saturation and over-literalness "above 12 or so"Civitai study

No literal error string is documented for the DPM++ issue — it shows up as visual artifacts, not a thrown exception.

Should you use "masterpiece" and "best quality" tags?

Quality-fluff tags like "masterpiece" and "best quality" come from an inherited tagging vocabulary, not anything SDXL-specific. The Danbooru wiki marks "masterpiece" as "Ambiguous and subjective. Do not use." (Danbooru). No source measures how SDXL responds to these tokens, so describe the framing and style you want directly instead.

Negative prompts: what's verified

Negative prompts are a real front-end feature that lets you "specify prompts which the model should avoid during image generation" (Wikipedia). Beyond that, the common heuristics are not independently sourced: a Civitai guide suggests leaving the negative blank until you see something unwanted, and warns that long "kitchen-sink" negatives "limit the algorithm" (Civitai) — no independent source confirms either. Treat both as the author's experience, not established practice. See negative prompts explained for the mechanics that are documented.

FAQ

Do camera angle words actually work in Stable Diffusion prompts? The angle words are genuine, documented cinematography vocabulary. No opened source directly tests whether Stable Diffusion or SDXL reproduces the conventional film effect from the word alone. The safe approach is to treat the terms as a vocabulary to test against your checkpoint and seed, comparing outputs with and without the term rather than assuming it always lands.

What is the difference between a shot type and a camera angle? A camera angle is about camera placement and tilt relative to the subject — high, low, eye-level, Dutch. A shot type (field size) is about how much of the subject is visible, set by camera-subject distance and focal length — close-up, medium shot, wide shot. The two are independent axes in film and can be combined in a single prompt.

What CFG should I use for SDXL? A community study on an SDXL-trained model reports a working range roughly from 4 to 10, with 4, 7, 15 and 30 as useful touchstones. It also reports that CFG "above 12 or so" drives hypersaturation and over-literal output. This is community-reported from one model, not a verified universal rule, so sweep CFG per checkpoint.

Why does DPM++ 2M SDE look broken at low steps on SDXL? The DPM++ solver becomes numerically unstable on SDXL below roughly 50 steps and produces visual artifacts. The documented fixes are to raise steps to 50+, enable use_karras_sigmas=True (or lu_lambdas=True), and for DPM++2M and DPM++2M SDE also set euler_at_final=True. The Karras schedule is what makes the popular "DPM++ 2M SDE Karras" combo stable.

Does (word:1.5) weighting still work in SDXL, and what is the default? Yes. (word:1.5) multiplies attention to that word by 1.5, and bare () with no number defaults to 1.1. The syntax is documented identically in AUTOMATIC1111, ComfyUI and Fooocus, so prompts copy cleanly between them. Escape literal parentheses with a backslash when you need the characters.

Should I leave the negative prompt empty for SDXL? Negative prompts are a real feature, but the "leave it blank by default" advice is an unverified heuristic from a single community article — no independent source confirms it as general best practice. A reasonable middle path is to start light and add specific exclusions only when an unwanted element actually appears in your output.

Are "masterpiece" and "best quality" still useful prompt tags? They come from an inherited tagging vocabulary. The Danbooru wiki marks "masterpiece" as "Ambiguous and subjective. Do not use." No source measures SDXL's response to these tokens specifically. Describing the framing, lighting and style you want directly is better-supported than relying on quality-fluff tags.

Sources