GITNUXSOFTWARE ADVICE
General KnowledgeTop 10 Best Depth Map Software of 2026
Top 10 depth map software ranking with tool comparisons for 3D artists and developers, including Mapillary and Adobe Substance 3D Sampler.
How we ranked these tools
Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.
Search agents gather the source set and the review record, including transcriptions of video reviews and podcasts.
Framework: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Mapillary is the best pick for teams that need automated, georeferenced depth data from camera captures to feed downstream 3D pipelines, whereas Adobe Substance 3D Sampler fits when you want depth maps to snap quickly into material asset workflows without CV pipeline overhead.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Mapillary
Mapillary Data APIs and dataset organization around georeferenced capture make repeatable batch depth computation feasible.
Best for: Fits when teams need automated georeferenced image datasets to feed depth pipelines.
Adobe Substance 3D Sampler
Editor pickMaterial-first depth generation with refinement controls aligned to texture and displacement authoring.
Best for: Fits when teams need depth maps that quickly convert into material assets without CV pipeline complexity.
3D Scanner App
Editor pickIntegrated depth-map visualization during the scan session enables fast cleanup before export.
Best for: Fits when makers need quick, exportable depth maps from mobile scans for compositing or lightweight reconstruction.
Comparison Table
Mapillary
API-firstStreet-level imagery platform that generates depth data and 3D understanding from camera captures.
Mapillary Data APIs and dataset organization around georeferenced capture make repeatable batch depth computation feasible.
Mapillary’s Data platform focuses on geotagged image management with camera metadata needed for vision pipelines that estimate depth from imagery. The platform workflow supports ingestion at scale, dataset organization by capture runs or areas, and retrieval of assets for batch processing. Mapillary’s automation surface is strongest when an external pipeline consumes images and pose context to compute stereo or monocular depth products and export depth-map formats for further 3D reconstruction.
A key tradeoff is that Mapillary does not replace dedicated depth solvers like photogrammetry packages or classical stereo pipelines, so depth denoising, metric alignment, and occlusion handling depend on the downstream engine. Mapillary fits best when an organization already has an image-to-depth workflow and needs reliable, automated capture-to-dataset plumbing for consistent scene coverage.
- +Strong dataset ingestion for georeferenced street imagery at scale
- +APIs support automated retrieval for batch depth processing
- +Camera pose context helps keep depth-map alignment consistent
- +Geospatial organization supports repeatable region-based workflows
- –Not a standalone stereo or monocular depth engine
- –Depth refinement and metric depth require external processing steps
- –Dataset governance needs disciplined labeling and area scoping
- –Output depth-map formats depend on the downstream export path
Geospatial analytics teams
Generate depth maps for city blocks
Repeatable depth-map generation
Computer vision pipeline engineers
Automate image-to-depth batch runs
Higher throughput pipelines
Show 1 more scenario
3D reconstruction teams
Reconstruct urban scenes from imagery
Denser scene models
Combine Mapillary camera context with external reconstruction tools to form dense point clouds.
Best for: Fits when teams need automated georeferenced image datasets to feed depth pipelines.
Adobe Substance 3D Sampler
enterpriseMaterial capture software that generates depth maps, normal maps, and PBR outputs from images.
Material-first depth generation with refinement controls aligned to texture and displacement authoring.
Substance 3D Sampler focuses on generating depth maps that feed material workflows rather than producing standalone depth from calibrated multi-view geometry. Its workflow centers on selecting or providing image inputs, generating a depth output, and then shaping the result through editing and material-oriented adjustments. The output is intended to move into 3D texturing, look development, and depth-aware compositing stages rather than to serve as an interchangeable reconstruction format across CV pipelines.
A key tradeoff is that it depends on a content-creation pipeline mindset instead of offering the camera-calibration, rectification, and dense reconstruction controls typically expected in dedicated depth estimation tools. It fits situations where depth maps are needed to drive shading, displacement, or material layers with predictable authoring controls. It is less suitable when a project requires strict metric depth guarantees from calibrated stereo or structured-light data collection.
- +Depth outputs are designed to plug into Substance material authoring workflows
- +Editing and refinement controls help correct artifacts before export
- +Depth-derived assets support repeatable look development across a library
- +Exports target common 3D texturing needs without extra CV glue
- –Less control over calibration, stereo geometry, and reconstruction parameters
- –Depth outputs are optimized for material use, not scientific measurement workflows
- –Batch automation and API extensibility are limited compared with pipeline tools
- –Complex scenes with strong scale variation can reduce depth consistency
3D artists and look dev teams
Turn photos into displacement-ready depth
Faster texture iteration
Studios building asset libraries
Standardize depth for reusable materials
More uniform results
Show 2 more scenarios
Compositors using depth-aware effects
Create depth mattes from images
Better layering accuracy
Use generated depth maps to drive depth-based compositing and occlusion-aware layering.
Small teams prototyping 3D content
Add depth cues without reconstruction setup
Less setup overhead
Produce usable depth maps from photo sets without managing camera models or dense stereo pipelines.
Best for: Fits when teams need depth maps that quickly convert into material assets without CV pipeline complexity.
3D Scanner App
SMBPhotogrammetry software for iPhone, iPad, and Mac that exports depth maps and 3D capture outputs.
Integrated depth-map visualization during the scan session enables fast cleanup before export.
3D Scanner App is built around a capture-to-depth workflow that targets depth estimation from real-world scenes, then produces an exportable depth image for downstream use. The application emphasizes on-device processing and rapid iteration, so depth-map visualization happens as part of the scan session rather than only after a desktop round trip. Depth-map alignment is handled inside the scan flow, which reduces manual calibration steps for users who want quick depth-map export.
A practical tradeoff appears when scenes include low texture or heavy motion, since mobile depth estimation can produce noisier surfaces that need more manual cleanup before export. A common use situation is generating aligned depth maps from short subject scans for assets that later need depth-aware image compositing or mesh reconstruction.
- +Fast scan-to-depth workflow for mobile capture sessions
- +Depth-map visualization supports quick iteration before export
- +Aligned depth output reduces manual post-alignment work
- +Depth-map export formats fit common depth-image pipelines
- –Mobile depth estimation can get noisy on low-texture scenes
- –Advanced configuration for calibration and refinement is limited
- –Large scenes may require multiple passes for clean depth
- –API and automation hooks are not a primary strength
Indie creators
Depth-aware compositing for short assets
Faster comp iteration with fewer reshoots
Small studios
Reference depth for mesh reconstruction
More stable downstream reconstruction inputs
Show 1 more scenario
Product modelers
Repeatable scanning of small objects
Consistent depth across similar items
Capture object scans and export depth maps for consistent asset-level depth edits.
Best for: Fits when makers need quick, exportable depth maps from mobile scans for compositing or lightweight reconstruction.
DepthPro
API-firstApple's open-source monocular depth estimation model for metric depth maps.
Metric scale inference in monocular depth estimation, driven by DepthPro’s internal normalization and depth-to-units mapping.
DepthPro turns single images into metric depth using a neural model that infers scale, not just relative structure. The GitHub project provides a developer-first codebase for running inference and exporting depth outputs in formats used by downstream pipelines.
- +Metric scale estimation from monocular input supports consistent depth units
- +Developer-friendly repository for running inference and exporting depth outputs
- +Produces dense depth maps that integrate with computer vision pipelines
- +Works without camera calibration inputs used in multi-view depth methods
- –Best results depend on image content and lighting conditions
- –Inference setup requires environment and GPU compatibility discipline
- –Limited direct tooling for multi-view alignment compared with photogrammetry stacks
- –Depth refinement quality may lag specialized depth completion pipelines
Best for: Fits when teams need metric depth from single images for automated downstream 3D reconstruction or compositing.
Relightable
vertical specialistAI depth and normal estimation service for 3D content pipelines.
Relighting-first depth generation that outputs assets usable for view-dependent rendering rather than only analysis.
Relightable turns captured views into relightable depth and lighting assets, not just static depth maps. The workflow centers on producing a depth representation that can be used for image relighting and depth-aware rendering.
- +Depth output tailored for view-dependent relighting workflows
- +Batch processing supports repeating generation across multiple datasets
- +Export-ready depth assets fit depth-aware rendering pipelines
- +Clear preprocessing expectations for consistent input images
- –Less suited for full photogrammetry tasks like dense reconstruction and mesh building
- –Limited control over stereo depth alignment and metric calibration parameters
- –Depth refinement controls are narrower than traditional depth-map toolchains
- –Advanced pipeline integration requires more external glue than API-first tools
Best for: Fits when teams need depth outputs optimized for relighting and depth-aware rendering from image sets.
Depthkit
vertical specialistVolumetric video software that uses depth sensors to create depth-aware human capture content.
Production batch generation with depth-map alignment and export geared for pipeline integration.
Depthkit focuses on turning image inputs into depth map outputs with a workflow aimed at production integration. It emphasizes depth estimation runs plus depth-map alignment and export in formats that support downstream computer vision pipelines.
- +Batch workflow supports consistent depth-map generation across large asset sets
- +Depth-map export targets downstream compositing and 3D reconstruction pipelines
- +Depth-map alignment helps when integrating depth with other calibrated imagery
- +Automation-oriented run flow fits repeatable production tasks
- –Limited visibility into the full calibration and refinement steps
- –Depth quality varies with scene content and input conditions
- –Depth-map format coverage can lag behind specialized reconstruction toolchains
- –More engineering is needed to integrate outputs into advanced stereo pipelines
Best for: Fits when teams need repeatable depth-map generation that plugs into existing computer vision workflows.
VSDC Video Editor
SMBDesktop video editor with a depth map effect for layered compositing and 3D-style scene animation.
Depth-map driven compositing via masks and effects on an editable timeline, with frame-accurate alignment tweaks.
VSDC Video Editor is primarily a video editor, and its depth-map workflow support is best viewed as a post-process lane rather than a full depth estimation pipeline. Depth maps are handled through media effects, mask-based workflows, and frame-by-frame editing tools that can pair with depth-map visualization and export formats commonly used in depth-aware compositing.
- +Timeline-based effects make depth-aware compositing practical for edited footage
- +Layering and masking tools support occlusion-style cutouts for depth-like results
- +Frame-accurate editing helps refine depth-map alignment during post
- +Media export workflows fit editorial pipelines that already manage depth assets
- –No built-in stereo reconstruction or camera calibration pipeline for metric depth
- –Depth refinement, denoising, and completion tools are not a first-class feature set
- –Depth-map formats and bit-depth handling are limited compared with dedicated depth tools
- –Automation and API surface is not positioned for computational vision batch jobs
Best for: Fits when depth maps already exist and the goal is editor-centric depth-aware compositing.
Avid Media Composer
enterpriseProfessional video editing software that supports depth map effects for compositing workflows.
Edit-timeline workflow that synchronizes external depth-map media with timecode-accurate editorial outputs.
Avid Media Composer is not a depth-map generator, but it can function as the media processing hub around depth-map visualization and depth-aware compositing. It handles high-throughput editorial workflows, timecode discipline, and round-tripping media through well-established post-production pipelines.
- +Timeline-based media management supports consistent depth-map review passes
- +Strong timecode and bin organization for tracking depth-related takes
- +Works with standard post pipelines that already produce depth outputs
- +High-throughput playback helps validate depth-aware composites
- –No native stereo or monocular depth estimation engine for generation
- –Depth-map-specific tooling like disparity alignment is not a core function
- –Depth-map export and format controls depend on external stages
- –Depth workflows can require custom effects and careful asset naming discipline
Best for: Fits when depth maps are generated elsewhere and the goal is controlled editorial review and delivery.
HitPaw FotorPea
SMBPhoto editing software with AI image depth generation for parallax and 3D-style visual outputs.
Single-image depth-map generation with depth-map visualization built into the same editing flow.
HitPaw FotorPea generates depth maps from images with a workflow focused on producing usable visual depth for downstream editing. It emphasizes monocular depth estimation for single images and provides tools to align, refine, and export depth-map outputs.
- +Monocular depth workflow for quick single-image depth-map creation
- +Built-in depth visualization to inspect depth distribution before export
- +Batch-style processing supports repeating the same parameter set
- +Depth-map export geared toward common post effects workflows
- –No documented API or extensibility surface for pipeline integration
- –Limited controls for calibration and metric depth output
- –Depth refinement options are constrained compared with research-grade tools
- –Stereo reconstruction workflows are not supported for disparity-based depth
Best for: Fits when solo creators need fast depth-map generation for editing, with limited calibration and pipeline integration.
MyHeritage AI Time Machine
SMBConsumer imaging product that creates 3D-style photo effects and depth-based animation from still images.
Time Machine’s automated face motion generation from uploaded portraits without camera or calibration inputs.
MyHeritage AI Time Machine focuses on generating stylized face animations from provided photos, rather than producing depth maps for computer vision pipelines. It uses an image inference workflow that outputs shareable results, not disparity maps or metric depth data.
- +Photo-to-animation workflow produces results without manual calibration
- +Fast iteration from uploaded images to shareable output
- +Good face consistency for well-lit, front-facing photos
- +Straightforward controls with minimal configuration overhead
- –No depth-map generation or depth estimation outputs for pipelines
- –No stereo or structured-light depth handling for 3D reconstruction
- –No exports for 16-bit or floating-point depth formats
- –Depth-map alignment and camera calibration tools are absent
Best for: Fits when teams need historical face animation from photos, not depth maps for depth estimation workflows.
Conclusion
After evaluating 10 depth map software, Mapillary stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right Depth Map Software
Depth map software turns image inputs into depth-map outputs that can drive compositing, relighting, or 3D reconstruction pipelines, and this buyer’s guide focuses on how those outputs are generated and operationalized. The tool coverage includes Mapillary, Adobe Substance 3D Sampler, 3D Scanner App, DepthPro, Relightable, Depthkit, VSDC Video Editor, Avid Media Composer, HitPaw FotorPea, and MyHeritage AI Time Machine.
Across these tools, integration depth and automation surface matter as much as depth quality, because some products are engines while others are workflow editors or dataset services. Teams also need to separate metric depth workflows from “depth for visuals” outputs to avoid rework when calibration and refinement controls are limited.
Depth Map Software for Depth Estimation, Refinement, and Depth-Aware Workflows
Depth map software produces depth-map generation outputs from image or capture sources, then exports depth-map formats for downstream use in compositing, material workflows, or reconstruction. Some tools like Mapillary emphasize georeferenced dataset organization and batch processing through data APIs, which supports repeatable depth computation over street-scale image sets. Others like Depthkit focus on production batch generation with depth-map alignment and export paths designed to plug into existing computer vision pipelines.
The category splits between tools optimized for analysis-grade depth estimation and tools optimized for creative depth-aware results, which shows up in how calibration and refinement controls are exposed. DepthPro targets metric scale inference from monocular inputs with a developer-friendly repository for running inference and exporting depth outputs, while VSDC Video Editor relies on already-existing depth maps to drive timeline-based depth-aware compositing and occlusion-style cutouts.
Depth-map operational controls: generation, calibration, and pipeline integration
Depth map software earns its place when depth outputs plug into an actual pipeline with repeatable generation, predictable alignment, and usable export formats. Features that control how outputs are generated and refined matter more than interfaces that only visualize depth maps.
Georeferenced dataset ingestion and batch processing through APIs
Mapillary supports automated retrieval of georeferenced street imagery via its Data APIs so teams can run depth-map generation repeatedly across large capture sets. This matters when depth estimation must stay consistent across months of field capture.
Monocular metric scale inference and inference exportability
DepthPro targets metric scale inference from monocular inputs and provides a developer-friendly repository for running inference and exporting depth outputs. This is the feature set to prioritize when downstream steps require depth in consistent units.
Calibration and refinement controls tuned for material workflows
Adobe Substance 3D Sampler is built around material-first depth generation with refinement controls aligned to texture and displacement authoring. This makes it suitable when the output drives material assets rather than scientific calibration and geometry parameters.
Depth visualization during capture for fast cleanup before export
3D Scanner App includes integrated depth-map visualization during the scan session to support quick cleanup before export. This helps on-the-spot iteration when scan quality depends on immediate handling of noisy frames.
Production batch generation with depth-map alignment and export paths
Depthkit focuses on production batch workflows with depth-map alignment and export geared toward pipeline integration. This helps when depth outputs must fit into existing computer vision steps with repeatable alignment.
Depth-driven compositing and occlusion-style cutouts on an editable timeline
VSDC Video Editor treats depth maps as timeline-controlled media that drive masks and effects with frame-accurate alignment tweaks. This matters when the goal is depth-aware compositing rather than generating metric depth.
Choose by output intent: dataset depth at scale, metric monocular, or depth-aware editorial
Selecting depth map software starts with output intent because multiple tools generate depth outputs that are optimized for different consumers. Metric depth requirements, material displacement needs, and depth-driven compositing workflows demand different generation and refinement controls.
If the team operates on georeferenced street capture sets, pick API-first dataset organization
Select Mapillary when repeatable depth computation must be fed by georeferenced capture organization and automated retrieval for batch processing. This decision aligns with teams that need consistent depth-map generation across large street-scale image datasets.
If single images must produce consistent depth units, prioritize monocular metric scale inference
Choose DepthPro when monocular inputs must map to depth in consistent units for downstream reconstruction or compositing. This approach also expects environment and GPU compatibility discipline for inference setup.
If depth outputs must directly become material assets, prioritize material-authoring aligned refinement
Select Adobe Substance 3D Sampler when depth maps are intended to drive texture and displacement authoring inside a material workflow. This path trades away deep control of calibration and stereo geometry that measurement-grade pipelines may require.
If depth is generated for mobile scanning sessions, prioritize in-session visualization and fast cleanup
Choose 3D Scanner App when scan-to-depth iteration must happen during the capture session using integrated depth-map visualization. This step is a practical fit when low-texture scenes risk noisy depth estimation that needs quick correction before export.
If depth exists already and the primary work is editorial depth-aware compositing, choose a timeline editor
Pick VSDC Video Editor when depth maps are used to drive masks and effects on a timeline with occlusion-style cutouts. This decision assumes stereo reconstruction and calibration pipelines are already handled elsewhere.
If the goal is relighting-ready depth assets from image sets, choose relighting-first output design
Choose Relightable when depth outputs must be optimized for view-dependent relighting rather than full photogrammetry mesh building. This matches teams that value depth outputs tailored for rendering workflows over dense reconstruction controls.
Who should buy Depth Map Software based on how they generate and use depth
Depth map software fits teams that already know where depth outputs will land next, because toolchains diverge sharply between generation engines and depth-aware editors. Buyers also need to distinguish between metric depth workflows and depth-for-visuals workflows to avoid rework.
Geospatial and street-capture teams running batch depth computation
Mapillary fits teams that need dataset organization around georeferenced capture and automated retrieval for batch depth generation through APIs. This segment usually runs repeated compute passes across many image batches.
Computer vision teams needing monocular depth in consistent units
DepthPro targets metric scale inference from monocular input and provides a repository for running inference and exporting depth outputs. This segment typically feeds depth into automated reconstruction or depth-aware compositing.
Material artists and pipeline teams converting depth into displacement assets
Adobe Substance 3D Sampler is designed so depth outputs plug into Substance material authoring workflows with editing and refinement controls that correct artifacts before export. This segment usually values depth aligned to texture workflows over stereo geometry control.
Mobile creators who need rapid scan-to-depth export for compositing
3D Scanner App supports fast capture-session cleanup by showing depth-map visualization during the scan. This segment benefits when handheld acquisition produces noisy depth on low-texture scenes.
Video editors using depth maps for masks, occlusion-style cutouts, and timeline effects
VSDC Video Editor supports depth-map driven compositing on an editable timeline with frame-accurate alignment tweaks. This segment typically already has depth maps and needs editorial control rather than reconstruction.
Common buying pitfalls when depth outputs meet pipeline constraints
Depth map buyers often fail by assuming depth quality is the only variable. Many failures come from mismatched assumptions about calibration control, metric scale, and where refinement steps actually occur in the workflow.
Assuming every tool that outputs a depth map provides metric depth suitable for geometry-scale workflows
DepthPro is built around metric scale inference from monocular input, while Mapillary commonly requires external processing steps for metric depth and depth refinement. Metric requirements should be validated against the generation controls exposed by the selected tool.
Buying an editor when the pipeline still needs depth estimation and calibration generation
VSDC Video Editor synchronizes depth-map media with an editorial timeline but does not provide a camera calibration pipeline for generating metric depth. Teams that still need stereo or monocular reconstruction should select a generation tool rather than relying on the editor.
Skipping configuration and compute checks for inference pipelines that require GPU compatibility discipline
DepthPro inference setup depends on image content and lighting conditions and requires environment and GPU compatibility discipline. When this step is missed, output inconsistency increases even if the UI looks correct.
Expecting mobile scan depth to be stable in low-texture scenes without extra cleanup time
3D Scanner App depth estimation can get noisy on low-texture scenes. In-session depth-map visualization helps reduce wasted exports, but it shifts effort into manual cleanup.
Optimizing for view-dependent relighting but selecting a tool focused on full reconstruction outputs
Relightable is optimized for relighting-first depth outputs usable for view-dependent rendering. Tools aimed at full photogrammetry mesh building often expose different controls that can cost time when the target is rendering-ready depth assets.
How We Selected and Ranked These Tools
We evaluated each tool on generation control coverage, automation surface, and practical integration paths into downstream depth-aware workflows. Features accounted for 40 percent because batch generation, alignment support, and depth export usability directly affect pipeline throughput.
Ease and value each accounted for 30 percent because inference setup friction, editing workflow fit, and output inspection mechanics determine whether depth-map production stays consistent. Mapillary led the ranking because its Data APIs and georeferenced dataset organization make repeatable batch depth computation feasible for street-scale teams, which converts depth estimation into an operational pipeline rather than a one-off output.
Frequently Asked Questions About Depth Map Software
How does Mapillary Data ingestion connect to external depth-map generation tools?
Which tools in the list provide metric depth scale rather than relative structure?
When a workflow needs relighting outputs, how does Relightable differ from standard depth-map generation?
What breaks if a team uses Avid Media Composer when depth maps must be generated and calibrated inside the same tool?
How does 3D Scanner App handle depth-map visualization and cleanup before export?
How does Depthkit approach batch automation compared with editor-centric tools like VSDC Video Editor?
Which tool is best aligned to converting photos into material-ready depth for displacement and texture workflows?
Where does HitPaw FotorPea fall short for pipeline integration compared with Mapillary and Depthkit?
What security and access controls should be validated when depth processing involves external APIs?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Funding and competing interests
This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.
They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.
Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →
- General KnowledgeTop 10 Best 2D Mapping Software of 2026
- Data Science AnalyticsTop 10 Best 3D Map Software of 2026
- Construction InfrastructureTop 10 Best 3D Topography Software of 2026
- Science ResearchTop 10 Best 3D Photo Scanning Software of 2026
- Science ResearchTop 10 Best Contour Map Software of 2026
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
General Knowledge alternatives
See side-by-side comparisons of general knowledge tools and pick the right one for your stack.
Compare general knowledge tools→