Image
Depth Anything V2 Preprocessor
Produce a depth-map image from a photograph with Depth Anything V2.
- Image editing
Sign in to create. Review the credit cost in the studio before running.
Catalog preview for Depth Anything V2 Preprocessor. Review your own result before publishing.
A starting point.
Produce a depth-map image from a photograph with Depth Anything V2. Use the map to inspect the scene’s depth structure before another image workflow.
Before you publish.
Compare subject boundaries and depth transitions with the source. Do not treat this image as a calibrated distance measurement.
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; no scene prompt is required.
Inspect the returned image at full size. Confirm that a downstream operation accepts depth maps before passing the result to it.
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/depth-anything/v2. 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 Depth Anything V2 Preprocessor through the API.
Start with this model ID for the endpoint featured on this page:
image-preprocessors/depth-anything/v2
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.