Prompt Embeddings
Last updated: May 18, 2026

A prompt embedding automatically injects a consistent set of tokens into every prompt used with a model, without the user having to type them each time. It's how you bake in style descriptors, brand language, or quality cues so they apply transparently across all generations from a model.
This article covers what embeddings are, the two types, how to set them up, and how they interact with custom-trained models.

What prompt embeddings do
When you generate from a model with a prompt embedding configured:
The user types a normal prompt:
a young woman holding a coffee cupThe system silently appends your embedding tokens, such as
, MYSTYLE, vibrant colors, soft lightingThe model receives the combined prompt and generates accordingly
The user never has to remember the extra tokens. The embedding ensures consistency across every generation, every team member, every API call.The two types
Type | Purpose | Example tokens |
|---|---|---|
Standard prompt embedding | Tokens added to steer generation toward what you want |
|
Negative prompt embedding | Tokens added to exclude unwanted elements |
|
Both run automatically once configured.
Family support
Prompt embeddings work across all current Scenario training families, single-image and edit LoRAs alike:
Flux 2 (Dev / Klein 9B / Klein 4B)
Flux 2 Edit
Qwen Image
Qwen Edit
Z-Image (Z-Image / Z-Image Turbo)
Flux Kontext
Both standard and negative embeddings function across every family. There are no SD-only restrictions on negative embeddings.
Setting up a prompt embedding
Open your trained model and go to the Details tab.
Find the Prompt Embedding field.
Enter the tokens you want appended automatically: comma-separated, in the order you want them applied.
(Optional) Enter Negative Prompt Embedding tokens for things you want excluded from every generation.
Save. The embedding is now active for all generations from this model.
When to use embeddings
Internal team or brand consistency: you want every team member's outputs to share style cues without coordinating prompts.
Public model distribution: users discover the model and want it to "just work" without learning trigger words.
API / MCP integrations: embeddings reduce the per-call prompt construction load.
Quality control: negative embeddings filter out artifacts you've seen the model produce.
Common pitfalls
Too many tokens. Five to ten well-chosen tokens beats twenty. More is not better; tokens dilute one another.
Conflicting tokens.
cinematicplusflat illustrationwill fight. Make sure the embedding is internally coherent.Trigger word in embedding without it being in prompt. Confirm the trigger appears via the embedding (or via user prompts); never silently expecting both and getting neither.
Negative embeddings that exclude valid content.
realisticin the negative will hurt models that should sometimes produce realism. Be precise.Forgetting to update after retraining. When you retrain, double-check the embedding still reflects the new model's vocabulary.