- The full pipelines this page comes from
- The Lab — members' canvas rooms
- Studio Canvas — pre / prod / post boards
ONCE一回
1:1 · two hours
AI Video line · stop 11 of 14 · 16 min · members
Where they belong, why a separate field is often worse, and the list that is only making things slower.
Free with an account
Membership is free: an account opens all 86 script pages. The Lab, Studio Canvas and the paid guides need the $99 pass, paid once. Already signed in on this browser? The page opens by itself.
The inheritance
A long list, passed between people, that nobody has tested.
Ask someone why a particular term is in their negative prompt and the honest answer is usually that it was in the one they copied. The lists circulate, grow, and are almost never tested against the model actually being used.
Two things follow. Most of the terms are doing nothing, and the two or three that would have helped are diluted by the rest.
The fix is not a better list. It is a much shorter one, written for the specific image and tested.
How they work
Which is why advice about them does not transfer.
Some models treat the negative field with real weight; others handle it weakly or ignore parts of it. Some do better with exclusions stated inline in the main prompt than in a separate field.
This variation is why the same negative list produces different results across models, and why the confident advice you read may simply not apply to what you are running.
Test it once: generate with your negative list, then with it emptied, everything else identical. If the images are indistinguishable, the list was decoration.
Writing a useful one
Specific to the shot, not a general quality wish.
A useful negative names something concrete that this particular image is likely to get wrong.
Three of these beat twenty generic terms, because each is doing work and none is competing with the others.
Generic quality terms — 'low quality', 'blurry', 'bad anatomy' — are the ones to drop first. They ask the model not to be bad, which is not an instruction it can act on.
Inline versus separate
On many models this is stronger than the dedicated field.
Writing the constraint as part of the main prompt — 'no logos, no readable text, nothing else in frame' — often lands harder than the same words in a negative field.
The reason is that the main prompt is generally weighted most heavily, and the exclusion arrives in the same context as the description it modifies.
Test both on your model. It costs two generations and it settles a question you will otherwise be guessing at on every prompt you write.
For video
No cuts.
Video models will invent a cut mid-generation — a sudden change of angle or lighting that makes the clip unusable in an edit where a continuous take was required.
Stating 'no cuts, one continuous shot' prevents most occurrences and costs four words.
Pair it with 'no additional objects enter the frame', which prevents the other common video failure: something walking or drifting into shot partway through.
The rule
One pass through your list, and it will get much shorter.
Go through whatever negative prompt you currently carry and, for each term, state the specific failure it prevents. Anything you cannot answer for goes.
Most people end up with three or four terms, and their results do not get worse. Frequently they improve, because the terms that were working are no longer competing with fifteen that were not.
Then add back only in response to an actual observed failure. That way the list stays short and every entry has earned its place.
1:1 · two hours