Stable Diffusion Regional Prompting with Regional Prompter

Stable Diffusion Regional Prompting with Regional Prompter

Regional Prompter assigns separate prompt clauses to defined parts of a Stable Diffusion canvas. It is an AUTOMATIC1111 extension, so the syntax and compatibility notes below are extension-specific rather than general Stable Diffusion syntax.

Version boundary: Regional Prompter upstream main commit 3ed4cb30e10e510e4cd9b33cd9b11cda170859c2, documented against AUTOMATIC1111 1.10.1. Documentation verified: 2026-07-16.

No independent image-generation comparison was performed for this guide.

Choose the region model before writing the prompt

This worksheet begins with ratio-defined regions because every input can be recorded as text. Mask and prompt-derived region modes exist upstream, but they add experimental behavior that is outside this text-only reference.

Core syntax

BREAK maps clauses to regions

Regional Prompter reads prompt clauses separated by BREAK. With three regions and no base prompt, supply three clauses:

misty pine forest BREAK
stone observatory BREAK
dry grass foreground

The same count rule applies to a region-specific negative prompt. If the negative prompt contains no BREAK, the extension applies that negative prompt to all regions.

Base prompt adds a shared clause

When Use base prompt is enabled, the first clause is treated as the base and is blended into every region according to the base-ratio setting. A three-region layout therefore needs four clauses:

overcast mountain landscape BREAK
misty pine forest BREAK
stone observatory BREAK
dry grass foreground

Do not confuse a base prompt with a common prompt. Upstream describes the common clause as text appended to each regional clause, while the base prompt is mixed by weight through the base-ratio control.

Divide ratio sets relative size

Comma-separated values describe relative region sizes. 1,1,1 creates three equal shares; 3,1,1 creates shares of 60%, 20%, and 20%. Scaling every number by the same factor leaves the proportions unchanged.

Rows and columns refer to the direction selected in the extension. Confirm the visible order in the region template before adding subject details; swapping a split direction changes which physical band receives each clause.

Three-region text worksheet

Use this worksheet to keep the region contract explicit before opening the WebUI:

Combined prompt:

quiet coastal landscape, early morning BREAK
dark rocks, tide pools BREAK
small lighthouse, pale walls BREAK
low dunes, beach grass

The worksheet is reproducible as a text configuration: another operator can enter the same canvas, mode, ratios, base weight, and clauses. It does not predict identical image content unless the rest of the generation configuration is also held constant, and it does not guarantee that every described object stays inside its assigned region.

Input-to-region audit

For the 2,3,2 example, translate each input into its intended region before generation:

If a local phrase belongs everywhere, move it to the base or common clause. If a phrase belongs to one region, keep it out of the shared clause to reduce cross-region influence.

Two-dimensional regions

Regional Prompter activates 2D behavior with ADDROW or ADDCOL; a semicolon in the divide ratio is another documented trigger. The prompt is traversed from the upper-left, then top to bottom and left to right according to the chosen main split.

A four-cell text template can be written explicitly:

cloud layer ADDCOL distant ridge ADDROW
river bank ADDCOL footpath

Before extending this layout, use the extension's region visualization/template control and record the generated ordering. Uneven 2D ratios are compact, but commas and semicolons change meaning with Rows, Columns, and flip settings.

Compatibility boundary

The upstream compatibility table at the recorded commit distinguishes Attention and Latent modes:

The same documentation notes that Latent mode repeats work per area and can corrupt LoRA behavior. LoCon and LoHa have additional WebUI-specific constraints. Treat this matrix as a snapshot of the named commit, not a promise about later forks or releases.

One-variable troubleshooting sequence

Keep the seed and every unrelated generation setting fixed while changing one item at a time:

1. Count only: disable the base prompt and use one plain noun per region. Confirm that the BREAK clause count equals the ratio count.
2. Direction only: switch Rows to Columns, or Columns to Rows, without editing the prompt or ratio. Confirm the physical ordering.
3. Ratio only: replace the ratio with equal values such as 1,1,1. If ordering becomes clear, restore the uneven ratio.
4. Base only: enable the base prompt, add exactly one leading clause, and keep a single base-ratio value.
5. Mode only: use Attention mode before evaluating Latent mode or region-specific LoRA behavior.
6. Extension stack only: disable other extensions, then re-enable one at a time after the text mapping is correct.

This sequence isolates syntax, geometry, weighting, calculation mode, and extension interaction. It cannot distinguish model behavior from regional configuration unless the checkpoint, sampler, seed, dimensions, and other inputs remain unchanged.

Workflow boundaries and related references

Regional prompting controls where prompt clauses are applied; it does not replace prompt cleanup. Establish exclusions with the Stable Diffusion negative prompts reference before splitting them by region.

For controlled prompt variation, use the Dynamic Prompts wildcard guide. Review repository provenance and rollback preparation in the extension selection and installation guide before adding Regional Prompter.

Primary sources

• Regional Prompter upstream repository
• Regional Prompter snapshot at commit 3ed4cb30e10e510e4cd9b33cd9b11cda170859c2
• AUTOMATIC1111 1.10.1 release