Generated images
How images are generated for articles, how many an article may carry, the style and reference controls, and how text inside a picture is handled.
On this page
When no approved asset fits a section, an image can be generated for it.
How many an article can carry
- Four images per articlemaximum
The ceiling on section images attached to one article. It is a per article limit and it is not raised by your plan: a plan buys you more images across the Project, not more images inside one piece.
- One image per articleminimum on a generated draft
A drafting run asks for at least one useful visual rather than treating images as optional decoration.
- Three reference assets per imagemaximum
How many of your own approved assets can be handed to the model as visual reference for a single image. This is a separate constraint from the four above.
Style
- ai_recommended
Let the pipeline choose per image.
- vector
Flat, graphic, diagrammatic.
- illustration
Drawn, editorial.
- photorealistic
Photographic.
Style is a Project setting, so a blog does not alternate between three visual languages by accident.
References
Generation can be guided by your own approved assets, so generated visuals resemble your product rather than a generic dashboard. This is the setting that makes the difference between illustrations that look like your software and illustrations that look like everyone's.
Budget
Image generation is metered per Project, alongside posts and topics. On a paid plan the budget refills with the billing period; a Free Project's 15 images are a one-time lifetime total that never refills.
When the image allowance is spent, articles are produced without generated images rather than failing. See usage and limits.
Replacing a generated image
Replacing one in the editor queues the work on the same durable queue automatic generation uses, so a manual replacement is paced with everything else rather than jumping the queue or timing out in the browser.
Replacing one on a post that is already live
You can regenerate a section image on a post that is already scheduled or published, and the replacement is checked like any other: it gets a real quality verdict rather than being left permanently marked in progress.
- The post stays where it is
Checking a replacement never unschedules or unpublishes the post. Whatever state the post was in, it stays in.
- The current image keeps serving
Readers continue to see the image that is there until a replacement is actually ready, so a live article is never left with a gap while work runs.
- One bounded retry
If the check is not satisfied, one replacement attempt may follow. It is bounded on purpose rather than looping.
Words inside a picture
Text baked into an image cannot be corrected later the way a sentence can, so how much readable copy an image carries is decided per image rather than left open.
This is not a setting you choose. The pipeline picks one of three modes for each image as it plans it, and the default is no readable copy at all.
| Mode | What it means |
|---|---|
| None | The visual carries no readable copy. This is the default and the most common answer. |
| Minimal | A few short conceptual labels, capped in both count and length. Labels only, and nothing that asserts a fact. |
| Verified caption | The image is allowed to state something checkable. |
Where an image does carry required copy, the editor shows you the exact strings alongside the image card, so what the picture is supposed to say is reviewable next to the article rather than only visible in the rendered image.