Image
Fibo Lite
Generate a composed image with Fibo Lite, using a written or structured prompt.
- Text to image
Sign in to create. Review the credit cost in the studio before running.
Catalog preview for Fibo Lite. Review your own result before publishing.
A starting point.
Generate a composed image with Fibo Lite, using a written or structured prompt.
Before you publish.
Compare the result with your source, especially object boundaries, fine text, faces and shadows.
Review the quote before running. A failed generation releases its reserved credits. Download the results you want to keep; stored media is retained for 30 days.
Settings and model questionsCheck the available settings and guidance when preparing your input.
Inputs and settings
Enter prompt or structured_prompt; an empty request cannot start. Set aspect_ratio and seed for a repeatable setup.
Inputs, all modes and APIModel IDs, current input limits and the API generation workflow.
Supported inputs
These fields come from the current studio form for bria/fibo-lite/generate. Other modes may require different inputs.
| Input | Type | Requirement | Options and limits |
|---|---|---|---|
aspect_ratio | Text | Optional | 1:1, 2:3, 3:2, 3:4, 4:3, 4:5, 5:4, 9:16, 16:9 |
image_url | Text | Optional | — |
prompt | Text | Optional | — |
seed | Whole number | Optional | — |
structured_prompt | Object | Optional | — |
Check the full model schema for all options and cross-field rules. Request a quote for your selected settings before generating.
Use Fibo Lite through the API.
Start with this model ID for the endpoint featured on this page:
bria/fibo-lite/generate
Input requirements belong to this model ID. Check a different mode’s schema separately when switching modes.
Check the current model schema for supported inputs and options. Other tasks may use different model IDs.
From quote to result.
Request a credit quote for your input and settings before submitting a generation. A sample output or the price of another model is not a quote for your request.
Follow the generation workflow, then poll the job for its status and result. The API and studio use the same balance.