Image
Google Virtual Try On
Preview clothing on a person with Google Virtual Try On.
- Image editing
Sign in to create. Review the credit cost in the studio before running.
Catalog preview for Google Virtual Try On. Review your own result before publishing.
A starting point.
Preview clothing on a person with Google Virtual Try On. Use a clear person photo and a separate image of the garment.
Before you publish.
Inspect garment boundaries, prints and body proportions. A generated preview does not establish real fit or size.
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
Send person_image_url and product_image_url in their respective fields.
Start with num_images set to one; quote again before requesting more variations.
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 google/virtual-try-on. Other modes may require different inputs.
| Input | Type | Requirement | Options and limits |
|---|---|---|---|
person_image_url | Text | Required | — |
product_image_url | Text | Required | — |
num_images | Whole number | Optional | ≥ 1 · ≤ 4 |
Check the full model schema for all options and cross-field rules. Request a quote for your selected settings before generating.
Use Google Virtual Try On through the API.
Start with this model ID for the endpoint featured on this page:
google/virtual-try-on
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.