Generated images
A site without pictures feels empty, and generic stock photos never quite match the style. So when the design needs them, the agent creates your app’s images itself with an image generation model, in your theme’s art direction and colors. They’re saved in your project like any other image.
When the agent creates images
Section titled “When the agent creates images”The agent uses its generate_image tool when the design calls for photos or illustrations: a hero, products, people, places, a gallery, a background. Instead of leaving empty boxes or pointing to external images, it creates the missing picture.
| It does | It doesn’t |
|---|---|
| Create the images the page really shows, usually 2 to 5 per page | Create icons (it uses lucide-react) |
| Match the theme’s style, lighting and colors | Create logos (they’re drawn as SVG, or provided by you) |
| Keep text, logos and watermarks out of the picture | Replace an image you provided |
| Create several at once, in parallel | Create images in Discussion mode (it changes nothing there) |
In the conversation thread, each image shows up as a step: “Creates the image hero-workshop”, for example.
Where images go
Section titled “Where images go”-
The agent describes the picture (subject, framing, style, lighting, theme colors) and picks a format: landscape (1536 × 1024), portrait (1024 × 1536) or square (1024 × 1024).
-
The image is created in about ten seconds, then saved as WebP in
public/assets/, with a readable name (public/assets/hero-workshop.webp). -
If that name is already taken (by one of your images, for example), the image gets a free name (
hero-workshop-2.webp): an existing image is never overwritten. -
The agent uses it in the site through its URL (
/assets/hero-workshop.webp), cropped to fill its slot.
You’ll find every image, generated or uploaded, in the editor’s Images tab: see Project images.
Limits and cost
Section titled “Limits and cost”- At most 6 images per request. Beyond that, the agent reuses the images it already created.
- The price of the images is added to the run’s cost, and so to the credits the request uses, on top of the agent’s work. See Credits.
- Image generation must be enabled on the platform. If it isn’t, the agent can’t create images and puts a placeholder instead.
Asking for images
Section titled “Asking for images”Describe what you want to see: the subject, the mood, the framing. The agent keeps the theme’s style.
Add a large photo at the top of the home page: a ceramics workshop bathed inmorning light, with clay pots on wooden shelves.Create a gallery of 4 of the restaurant's signature dishes, shot from above on adark stone table, warm lighting.Replace the photos in the "How it works" section with flat illustrations in thetheme's colors, one per step.Avoiding generated images
Section titled “Avoiding generated images”If you’d rather have a site without generated images (you’ll provide your own photos, or you want a purely graphic style), say so:
Don't use generated images: build the design with typography, shapes and flatareas of the theme's colors.To make the rule apply to the whole project, add it to Instructions for the agent (Project settings), for example “No generated images”. See Project settings.
Replacing an image with your own
Section titled “Replacing an image with your own”-
Open the editor’s Images tab and click Upload images (or drop your files on the panel). Your images are saved in
public/. -
Switch to Design mode, click the image to replace in the preview, then Pick a project image and choose yours. This change costs no credits.
-
Or ask the agent: upload the image to the project from the chat’s + menu (Upload an image to the project), then write for example “put this photo in place of the hero image”.
A generated image you no longer use can be deleted from the Images tab (Delete). The panel shows whether an image is still used in the site.