Skip to content
Reduced motion is on. Play a preview to watch it.
Explore models

Image

Fibo Edit [Erase by Text]

Use Fibo Edit [Erase by Text] to remove a named object from a photo.

  • Image editing
Create with Fibo Edit [Erase by Text]
Preview for Fibo Edit [Erase by Text]

Catalog preview for Fibo Edit [Erase by Text]. Review your own result before publishing.

A starting point.

Use Fibo Edit [Erase by Text] to remove a named object from a photo.

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.

How credits work · Use the API · Content guidelines

Settings and model questionsCheck the available settings and guidance when preparing your input.

Inputs and settings

Name the object in object_name; no selection mask is needed.

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-edit/erase_by_text. Other modes may require different inputs.

Input types, requirements and limits for bria/fibo-edit/erase_by_text
InputTypeRequirement
image_urlTextRequired
object_nameTextRequired

Check the full model schema for all options and cross-field rules. Request a quote for your selected settings before generating.

Use Fibo Edit [Erase by Text] through the API.

Start with this model ID for the endpoint featured on this page:

bria/fibo-edit/erase_by_text

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.