Stable Diffusion Prompts Guide: What Works by Model
Summary
Stable Diffusion prompts work differently depending on the model version. SD1.5 and SDXL want comma-separated token lists; SD3.5 understands natural language. This guide covers the five-part prompt structure that holds across all versions, tested negative prompts tailored by use case, how parenthesis weighting works without distorting outputs, and LoRA trigger word integration. Includes copy-ready examples for editorial portraits, architecture shots and cinematic scenes.
Your Stable Diffusion prompt does not work the same way on SD1.5, SDXL and SD3.5. This stable diffusion prompts guide covers the exact syntax per model version -- tested negative prompts, weight mechanics, LoRA integration and copy-ready examples from production. If you have been copy-pasting generic prompts and getting inconsistent results, the fix is structural, not random.
SD1.5, SDXL, SD3.5: Each Model Has Its Own Prompt Language
The biggest mistake in every beginner guide is treating Stable Diffusion as one tool. It is three different prompt languages.
SD 1.5 wants short, dense token lists. The model reads your prompt as a bag of concepts weighted by position. Earlier concepts pull more attention. This means: lead with what matters. portrait of a woman, cinematic lighting, shallow depth of field, film grain, 35mm, kodachrome, highly detailed works because the subject and lighting come first. A long descriptive sentence confuses SD 1.5 -- it is not built to parse grammar.
SDXL handles longer prompts and responds well to quality preambles. The structure (masterpiece, best quality:1.2), [subject], [style tags], [lighting], [camera] remains reliable. SDXL is more forgiving on token order than SD 1.5 but still reads prompts as a list, not a sentence. One key difference: SDXL handles negative prompts more precisely, so specificity in your negatives pays off more here than on SD 1.5.
SD 3.5 changed the rules entirely. With its MMDiT-X architecture and triple text encoder, it understands natural language at a level the older versions cannot. Write A woman standing in front of a neon-lit bookshop in rain, photographed with a 50mm lens, warm interior light spilling out, film photography aesthetic and SD 3.5 follows the sentence. The same prompt on SD 1.5 will produce something passable but compositionally different -- and not always in the direction you wanted.
The practical test: take your best SDXL prompt, run it verbatim on SD 3.5. You will get a decent output. Now rewrite it as two natural sentences. Run again. The second output will noticeably follow your composition intent better.
SD 3.5 also handles text in images better than any previous Stable Diffusion version. If readable text in the output matters for your use case, SD 3.5 is the only SD version worth using for that task.

The Five-Part Prompt Structure That Holds Across All Versions
Whatever model you are running, this structure gives you a reliable starting point:
Subject -- who or what, stated clearly in the first few words
Style reference -- the visual language: cinematic, editorial, vintage photograph, brutalist illustration, analog
Lighting -- the most undertested variable (soft diffused light, golden hour, hard directional light, neon rim light, overcast flat)
Technical and camera -- focal length, film stock, medium, implied aspect ratio
Quality signal -- for SD 1.5 and SDXL:
best quality, highly detailed, 8k. For SD 3.5: skip it, it adds nothing
Put the subject first in every version. Everything else can shift. When an output looks wrong, fix the subject line before adding more tokens.
Steal this SD 1.5 and SDXL base:
[subject], [style], [lighting], 35mm photography, film grain, highly detailed, best qualitySteal this SD 3.5 base:
[Scene described in one or two sentences.] Shot on 35mm film, [lighting condition], [specific aesthetic reference].Both are starting points. Adapt when you know the model's behaviour well enough to know what to push.
Negative Prompts: Stop Using the Generic List
Here is the negative prompt you find in 90% of guides:
ugly, blurry, bad anatomy, extra limbs, deformed, low quality, worst quality, jpeg artifactsNot wrong. But barely doing any real work in most contexts. Negative prompts work by encoding what you do not want in the latent space. The more specific you are to the actual problem showing up in your outputs, the more effective they become.
If you are getting muddy backgrounds: add busy background, cluttered, noisy background, absent depth of field.
If portraits drift anatomically: add asymmetrical eyes, deformed hands, fused fingers, extra fingers, elongated neck.
If the output slides toward stock photography despite your prompt: add stock photo, overexposed, corporate photography, glossy, overly bright.
If you are seeing watermark bleed-through from training data: add watermark, signature, logo, text overlay.
My production negative prompt for editorial portraits on SDXL:
blurry, out of focus, bad anatomy, deformed hands, extra limbs, asymmetrical eyes, stock photo, overexposed, watermark, signature, text, low quality, worst quality, jpeg artifacts, plastic skin, airbrushed, over-retouchedStrip the clauses that do not apply to your subject. Running portrait-specific negatives on a landscape generation wastes computation and can suppress things you actually want.
One thing worth knowing: SD 3.5 responds to natural language in the negative field. No watermarks. Do not include text. Avoid overexposed highlights. works alongside token lists. Test both formats on your subject and pick whichever gives you cleaner outputs.

Weights and Emphasis Without Wrecking the Output
In SD 1.5 and SDXL, parentheses increase weight and square brackets decrease it.
(cinematic lighting:1.3)-- 30% more weight on this concept[cluttered background]-- slightly suppresses this element((very important detail))-- each parenthesis pair multiplies by roughly 1.1
The hard rule: stay under 1.4 for any single element. Above that, the model distorts the weighted concept and can pull the composition toward it in ways you do not want. You are not adding emphasis, you are burning the generation.
A common mistake: stacking multiple weighted elements. Running (golden hour:1.3), (film grain:1.3), (shallow depth of field:1.2) spreads the weight budget across three things and often delivers none of them cleanly. Pick one or two elements to weight. Leave the rest at natural weight.
For SD 3.5, weight syntax has less effect. The model's natural language understanding means you get emphasis from sentence structure. Write an imposing Victorian mansion, with a small figure barely visible in the foreground and the compositional relationship comes through without any parenthesis syntax.
Try this on SD 3.5: build your prompt with zero weight tokens. Add them only if the model consistently underweights something critical across three or more generations.
LoRAs: How They Change What You Need to Write
LoRAs are small add-on models that tune Stable Diffusion for a specific style, character or subject. Loading one shifts your base prompt strategy.
The syntax: <lora:model_name:0.8> in the positive prompt, where 0.8 is the weight. Start between 0.7 and 0.8. Going above 1.0 often oversaturates the effect and can break anatomy on portrait subjects.
What changes when a LoRA is active: the trigger word carries a lot of weight, so your base prompt can be leaner. If you load a cinematic film grain LoRA with trigger word filmgrain35mm, you do not need 35mm, kodachrome, film grain, analog photography in your base. Write filmgrain35mm portrait of [subject], soft window light, editorial and let the LoRA do the texture work.
What does not change: your subject line, lighting direction and negative prompt still matter as much as without the LoRA. LoRAs handle style and surface. They do not fix a poorly structured subject line or a composition that mismatches your output intent.
Where to find reliable LoRAs: Civitai is the main repository. For production use, stay with LoRAs that have solid download counts and example outputs close to what you need. A LoRA with minimal downloads and no example images is a black box -- you will spend more time debugging than generating.

Copy-Ready Prompts: Start Here, Adapt Later
Editorial portrait on SDXL:
Positive:
portrait of a woman in her late 30s, looking past the camera, editorial photography, soft window light from the left, muted warm tones, film grain, medium format, (shallow depth of field:1.2), highly detailed, best qualityNegative:
blurry, bad anatomy, deformed hands, plastic skin, overexposed, stock photo, watermark, text, low qualityBrutalist architecture on SD 1.5:
Positive:
brutalist apartment building exterior, raw concrete texture, overcast sky, documentary photography, wide angle, desaturated palette, high contrast shadows, 28mm lens, kodak tri-x grain, highly detailedNegative:
people, cars, colorful, oversaturated, blurry, digital art, illustration, paintingNatural language scene on SD 3.5:
Positive:
A young woman reading in a small independent bookshop late afternoon, warm light from a window beside her, shot on 35mm film, editorial photography style, slightly underexposed, visible grain, candid feelNegative:
blurry, deformed hands, asymmetrical eyes, watermark, stock photo, overlitSteal this. Remix if you want, but start from something that works before you diverge.
Platforms to Run These Prompts
You do not need a local GPU setup to test these. Several platforms let you run SD-based and related models in-browser or via API.
One Thing Before You Keep Tweaking
Most prompt problems are not actually prompt problems. They are seed problems.
Run a solid prompt at least three times before touching anything. Stable Diffusion is stochastic -- variation is built into the generation process. One bad output from a good prompt is noise. Three bad outputs in a row, all wrong in the same way, is signal worth acting on.
The workflow that actually works: fix your prompt structure, find a seed that produces a strong output, then refine from that baseline. Tweaking the prompt after every single generation will keep you in an endless loop of marginal changes with no reference point to compare against.
Go try it. Pick one of the prompts above. Drop it into ComfyUI, AUTOMATIC1111 or your SD platform of choice. Run it ten times before you change a word. You will learn more about what the model responds to in those ten runs than in any prompt guide.
Crack it open and see how it is built.