Image
Zoe Depth Preprocessor
Estimate an image’s depth structure with the Zoe preprocessor.
- Image editing
Sign in to create. Review the credit cost in the studio before running.
Catalog preview for Zoe Depth Preprocessor. Review your own result before publishing.
A starting point.
Estimate an image’s depth structure with the Zoe preprocessor. Use its depth-map output when planning a compatible conditioning workflow.
Before you publish.
Compare foreground boundaries and depth transitions with the source. Do not infer calibrated real-world distances from the returned picture.
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 image_url without a prompt. This operation returns a depth-map image.
Inspect the map and keep it alongside the source. Verify the next operation’s accepted depth representation before passing it onward.
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 image-preprocessors/zoe. Other modes may require different inputs.
| Input | Type | Requirement |
|---|---|---|
image_url | Text | Required |
Check the full model schema for all options and cross-field rules. Request a quote for your selected settings before generating.
Use Zoe Depth Preprocessor through the API.
Start with this model ID for the endpoint featured on this page:
image-preprocessors/zoe
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.