FAQ

Computer vision

Depth estimation datasets

Monocular and RGB-D depth data — and the difference between sensor depth, stereo depth and synthetic ground truth.

Depth datasets differ most in how the ground truth was obtained, and that provenance determines what a model trained on them can actually do.

There are three sources of depth ground truth and they are not equivalent. Active sensors give metrically accurate depth with characteristic failure modes — holes on reflective, transparent and distant surfaces. Stereo matching gives dense depth that is wrong in exactly the regions where matching is ambiguous. Synthetic rendering gives perfect, complete depth for scenes that do not look quite real.

The practical consequence is that a model trained on one source inherits that source's blind spots. Sensor-depth training data teaches a model to be uncertain about windows because the sensor was. If your application involves glass, water or shiny metal, check what the ground truth did there before anything else.

This list is short because the verified set is. The depth benchmarks most papers report — outdoor driving sets above all — are not among the datasets checked for this page, and the ones that are lean indoor: RGB-D scans of rooms and reconstructions of scenes. That matters more than the count. A model trained on indoor sensor depth has learnt ranges of a few metres and the statistics of furniture, and it will not tell you how far away a car is. If your target is outdoors, treat everything below as a pretraining source and plan to evaluate on data from your own environment, checking the terms of any outdoor benchmark before you build on it — several of the best known are non-commercial.

Four colour-coded depth maps with pixel axes: a) a flat yellow rectangle from Kinect v1, b) a room view from Kinect v2 with dark gaps at the edges, c) an octagon-shaped narrow-field Azure Kinect frame, and d) a circular fisheye-like wide-field Azure Kinect frame.
Depth frames from three generations of consumer sensor: Kinect v1 (a), Kinect v2 (b) and Azure Kinect in narrow (c) and wide field-of-view modes (d). Resolution, field of view and the shape of missing regions (dark blue) all differ, so ground truth captured with one sensor carries that sensor's quirks into every model trained on it. Image: Figure 4 of the article · CC BY 4.0 · from Tölgyessy et al. 2021, Sensors, “Evaluation of the Azure Kinect and Its Comparison to Kinect V1 and Kinect V2”, doi:10.3390/s21020413
DatasetModalitySizeLicenceBest for
NYU Depth V2Multimodal47,584 imagesUnclear — see belowMonocular depth estimation for indoor scenes
ScanNetImage1,513 scansGated access3D semantic segmentation
SceneSplat-7KImage7,916 scenesResearch onlyNeRF or 3D Gaussian Splatting models
CV-BenchMultimodal2,638 examplesApache 2.0Assessing 2D and 3D abilities
Licences in this shortlist — computed from the 4 datasets below. Red marks licences that are unclear or restricted.
A 4x4 grid: the top-left cell is a photograph of a living room with sofas, a coffee table and an ottoman; the remaining fifteen cells are inferno-coloured depth maps of that same scene, each captioned with a model variant such as 'v3.1 BEiT L-512', 'v3.1 Swin2 L-384', 'v3.0 DPT L-384', 'v2.1 Large 384' and 'v3.1 LeViT 224'.
One indoor scene through fifteen monocular depth models. The scene is identical and the sharpness is not; most of that difference traces back to each model's encoder and input resolution, since the v3.1 models share one twelve-dataset training mix. Image: isl-org/MiDaS · MIT repository
№ 01

NYU Depth V2

Multimodal
Size
47,584 training and 654 validation RGB images with dense depth maps (FastDepth preprocessing), Parquet
Licence
No licence stated on the official NYU page (citation requested); this Hugging Face copy's card says MIT and its metadata tag Apache 2.0

RGB images paired with dense depth maps from NYU Depth V2's indoor Kinect recordings, in the FastDepth preprocessing: 47,584 for training and 654 for validation. This copy holds depth only; the segmentation labels of the original 1,449-image labelled set are not in it. The long-standing baseline for monocular depth estimation.

What to train on it

Training monocular depth estimation for indoor scenes, building perception for home robots or AR/VR glasses, and studying 3D scene reconstruction from RGB-D.

Source: innovatiana.com

№ 02

ScanNet

Image
Size
1,513 annotated RGB-D scans, 2D/3D formats (images, voxels, meshes, depth maps)
Licence
ScanNet Terms of Use for the data (signed agreement required); code under MIT

1,513 annotated indoor RGB-D scans covering 20 object classes, delivered across 2D and 3D formats including images, voxels, meshes and depth maps. The reference dataset for indoor 3D semantic segmentation. Only the code is MIT: the data is released under the ScanNet Terms of Use, which you sign to request access.

What to train on it

3D semantic segmentation, interior scene reconstruction, object detection and tracking in enclosed spaces, and robotic perception and indoor navigation.

Source: innovatiana.com

Three panels of the same tabletop: a colour photo of four clear plastic bottles and two cases on a blue cloth; the depth camera's input depth, with black holes and wrong values where the bottles stand; and the ground-truth depth, in which each bottle appears as a complete shape.
A depth camera's view of clear bottles beside the ground truth. The sensor map has holes exactly where the objects are, and a model trained on sensor depth inherits them — the blind spot described above, in one frame. Images: Shreeyak/cleargrasp · Apache-2.0 repository · from “ClearGrasp: 3D Shape Estimation of Transparent Objects for Manipulation”, arXiv:1910.02550
№ 03

SceneSplat-7K

Image
Size
7,916 scenes, 11.27 billion 3DGS points, `.npy`, `.json` files and metadata in `.csv`
Licence
CC BY-SA 4.0 covers only the code, scripts and metadata; the scenes come from ScanNet, Matterport3D and other indoor sets, which restrict use to non-commercial research and education

7,916 indoor 3D scenes reconstructed from sources including ScanNet and Matterport3D, carrying 11.27 billion Gaussian Splatting points with poses and annotations in .npy, .json and .csv. Built for 3DGS and NeRF work. Access is gated, and the CC BY-SA 4.0 licence covers only the code and metadata: every source dataset restricts the scenes to non-commercial research and education. The card's statistics after later data updates total 5,384 scenes.

What to train on it

Training NeRF or 3D Gaussian Splatting models for photorealistic rendering, evaluating indoor 3D reconstruction from RGB-D, and testing 3D vision-language architectures.

Source: innovatiana.com

№ 04

CV-Bench

Multimodal
Size
2,638 examples with 2D/3D annotations and images, 810 MB, Parquet and JSONL
Licence
Apache 2.0

2,638 manually inspected examples with 2D and 3D annotations plus associated images, 810 MB shipped as both Parquet and JSONL, drawing labels from ADE20k, COCO and OMNI3D. It tests whether vision-language models grasp spatial layout and depth.

What to train on it

Assessing 2D and 3D abilities of multimodal models, probing comprehension of spatial layout and depth, and benchmarking vision and multimodal research.

Source: innovatiana.com

Left, a photorealistic rendered living room with a spiral staircase, hanging plants and a coffee table, labelled a. To the right, seven smaller panels of the same view: a yellow-to-blue depth map (b), a multicoloured surface-normal map (c), two flat-colour segmentation maps (d, e), the room's surface colours without shading (f), and two dark lighting layers (g, h).
A rendered Hypersim room with some of its labels: depth (b), surface normals (c), segmentation (d, e), reflectance (f) and lighting layers (g, h). Rendering gives a depth value at every pixel, with none of the holes a sensor leaves. Its depth files store distance to the camera centre, not planar depth, so convert before mixing them with sensor data. Image: apple/ml-hypersim · CC BY-SA 3.0 (dataset) · from “Hypersim: A Photorealistic Synthetic Dataset for Holistic Indoor Scene Understanding”, arXiv:2011.02523

How this list was put together

Found by searching Dataset Finder for datasets whose documentation describes the task, then checked by hand. A keyword match is not a fit — the first pass picked up a coral survey for the depth-estimation list because it was recorded below fifty metres — so every entry was read against what this page covers, and the ones that matched a word without matching the task were removed.

Sizes and licences come from each dataset's own documentation, vague wording included. Where we found a re-upload or catalogue card stating a licence that the original release contradicts — a CC0 tag on Flickr photographs, MIT on data whose terms require a signed agreement — the entry gives the original terms and says so. The comparison table abbreviates licences; hover a cell for the full wording.

Stop hunting. Start searching.

The datasets listed on this page are in Dataset Finder, alongside tens of thousands more — searchable in plain language.

Search Dataset Finder →