Image
AuraSR
Upscale a photograph with AuraSR and compare checkpoint variants on the same source.
- Image editing
Sign in to create. Review the credit cost in the studio before running.
Catalog preview for AuraSR. Review your own result before publishing.
A starting point.
Upscale a photograph with AuraSR and compare checkpoint variants on the same source. Keep an untouched original for evaluating changed detail.
Before you publish.
Inspect tile boundaries, edges and fine texture. A larger image does not establish that newly added detail is accurate.
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
Provide image_url and select checkpoint from the available studio options.
overlapping_tiles uses overlapping regions to help reduce seams. Compare the actual result and turnaround rather than assuming this option is always preferable.
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 aura-sr. Other modes may require different inputs.
| Input | Type | Requirement |
|---|---|---|
image_url | Text | Required |
checkpoint | Text | Optional |
overlapping_tiles | On/off | Optional |
Check the full model schema for all options and cross-field rules. Request a quote for your selected settings before generating.
Use AuraSR through the API.
Start with this model ID for the endpoint featured on this page:
aura-sr
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.