Papers › Depth Anything: Unleashing the Power of Large-Scale Unlabeled Data

Depth Anything: Unleashing the Power of Large-Scale Unlabeled Data

19 Jan 2024CVPR 2024 1arXiv:2401.10891archive 2025-07-28

Lihe Yang, Bingyi Kang, Zilong Huang, Xiaogang Xu, Jiashi Feng, Hengshuang Zhao

This work presents Depth Anything, a highly practical solution for robust monocular depth estimation. Without pursuing novel technical modules, we aim to build a simple yet powerful foundation model dealing with any images under any circumstances. To this end, we scale up the dataset by designing a data engine to collect and automatically annotate large-scale unlabeled data (~62M), which significantly enlarges the data coverage and thus is able to reduce the generalization error. We investigate two simple yet effective strategies that make data scaling-up promising. First, a more challenging optimization target is created by leveraging data augmentation tools. It compels the model to actively seek extra visual knowledge and acquire robust representations. Second, an auxiliary supervision is developed to enforce the model to inherit rich semantic priors from pre-trained encoders. We evaluate its zero-shot capabilities extensively, including six public datasets and randomly captured photos. It demonstrates impressive generalization ability. Further, through fine-tuning it with metric depth information from NYUv2 and KITTI, new SOTAs are set. Our better depth model also results in a better depth-conditioned ControlNet. Our models are released at https://github.com/LiheYoung/Depth-Anything.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 11 code samples harvested from 3 repositories linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 1 sample from 1 repository, 1 ran (0 with no instrument failure; 1 where Syntology's instrument failed); community (archive-listed): 10 samples from 2 repositories, 8 ran (7 with no instrument failure; 1 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 4 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

LiheYoung/Depth-Anything officialmentioned in papermentioned on GitHubpytorchSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
JTRNEO/SynRS3D mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to SynRS3D: A Synthetic Dataset for Global 3D Semantic Understanding from Monocular... (arXiv:2406.18151; that paper's own run record: 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified; the one sample that ran constructed an object rather than computing a result); nothing checks that they implement this paper's method. report
duan-song/SATNet mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to MobileNetV2: Inverted Residuals and Linear Bottlenecks (arXiv:1801.04381; that paper's own run record: 85 ran (of which 40 constructed an object rather than computing a result; 64 with no instrument failure: 8 honoured, 0 violated, 56 with no contract checked; 21 where Syntology's instrument failed) · 26 unverified); nothing checks that they implement this paper's method. report
fabio-sim/Depth-Anything-ONNX mentioned on GitHubpytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Depth Anything V2 (arXiv:2406.09414; that paper's own run record: 9 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 0 violated, 3 with no contract checked; 5 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
greatenanoymous/monodpt_grasp mentioned on GitHubpytorchApache-2.0Syntology: 8 samples, 7 ran (1 instrument-failed) · 1 unverified report
MindCode-4/code-3 mindsporeSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to MathOdyssey: Benchmarking Mathematical Problem-Solving Skills in Large Language Models... (arXiv:2406.18321; that paper's own run record: 5 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
spacewalk01/depth-anything-tensorrt pytorchMITSyntology: 2 samples, 1 ran (0 instrument-failed) · 1 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

11 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
1ran; the contract check could not run
7ran
2unverified

Licence: 0 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 3 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

LiheYoung/Depth-Anything official repository 1 sample, 1 ran (1 instrument-failed) · 0 unverified
load_ckpt in 31 papers metric_depth/train_mono.py ran; the contract check could not run (DEP_MISSING) · metamorphic tier: deterministic Apache-2.0 (permissive) · 6ff08048a8305588 · report fixture: signature config:MinimalConfig/0/?, model:callable/0/?, checkpoint_dir:str/0/str, ckpt_type:str/0/str · returned MinimalModel · level recorded 2026-09-22
greatenanoymous/monodpt_grasp community (archive-listed) 8 samples, 7 ran (1 instrument-failed) · 1 unverified
depth2PointCloud metric_depth/create_pc.py ran Apache-2.0 (permissive) · 8f37f1dad72ee59a · report fixture: signature depth:MockDepthData/0/?, rgb:MockRGBData/0/?, depth_scale:float/0/float, clip_distance_max:float/0/float, intrinsics:MockIntrinsics/0/? · returned ndarray · level recorded 2026-09-25
depth2PointCloudFakeDepth metric_depth/create_pc.py ran Apache-2.0 (permissive) · 0813761694382465 · report fixture: signature depth:ndarray/2/float, rgb:ndarray/3/int, depth_scale:float/0/float, clip_distance_max:float/0/float, intrinsics:FakeIntrinsics/0/? · returned ndarray · level recorded 2026-09-24
infer in 29 papers metric_depth/evaluate.py ran · our draft was wrong Apache-2.0 (permissive) · 8ffddb7d6410c4f1 · report fixture: signature model:callable/0/?, images:Tensor/4/float · returned Tensor · level recorded 2026-09-22
infer_relative_depth metric_depth/evaluate_relative.py ran Apache-2.0 (permissive) · c7ed25a9b6ac1ab2 · report fixture: signature model:callable/0/?, images:Tensor/4/float · returned Tensor · level recorded 2026-09-24
project_point metric_depth/camera.py ran Apache-2.0 (permissive) · fe823f83592f9fc3 · report fixture: signature camera_pose:ndarray/2/float, ee_pose:ndarray/2/float, marker_offset:ndarray/1/float · returned ndarray · level recorded 2026-09-24
project_point_to_pixel metric_depth/camera.py ran Apache-2.0 (permissive) · 822210307d6c6191 · report fixture: signature camera_pose:ndarray/2/float, ee_pose:ndarray/2/float, marker_offset:ndarray/1/float, K:ndarray/2/float · returned ndarray · level recorded 2026-09-24
reprojection_error2d metric_depth/camera.py ran Apache-2.0 (permissive) · 55658559d5046929 · report fixture: signature x:ndarray/1/float, ee_poses:list/1/ndarray, marker_points_2d:list/1/ndarray, K:ndarray/2/float · returned ndarray · level recorded 2026-09-25
infer_complete_depth metric_depth/evaluate_complete.py unverified Apache-2.0 (permissive) · 03b9e7ce46a39fe4 · report
spacewalk01/depth-anything-tensorrt community (archive-listed) 2 samples, 1 ran (0 instrument-failed) · 1 unverified
apply_min_size in 5 papers python/depth_anything/util/transform.py ran MIT (permissive) · 8d4e5ab503856d09 · report fixture: signature sample:dict/0/?, size:tuple/1/int, image_interpolation_method:int/0/int · returned tuple · level recorded 2026-09-24
load_image in 273 papers python/depth_anything/util/transform.py unverified MIT (permissive) · 24a768b877a487a4 · report

Tasks

Data AugmentationDepth EstimationMonocular Depth EstimationSemantic Segmentation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Monocular Depth Estimation ETH3D Depth Anything Delta < 1.25 0.882 #4 of 10 Archive leaderboard report
Monocular Depth Estimation ETH3D Depth Anything absolute relative error 0.0127 #4 of 10 Archive leaderboard report
Monocular Depth Estimation KITTI Eigen split Depth Anything Delta < 1.25 0.982 #10 of 79 Archive leaderboard report
Monocular Depth Estimation KITTI Eigen split Depth Anything Delta < 1.25^2 0.998 #10 of 79 Archive leaderboard report
Monocular Depth Estimation KITTI Eigen split Depth Anything Delta < 1.25^3 1.000 #10 of 79 Archive leaderboard report
Monocular Depth Estimation KITTI Eigen split Depth Anything RMSE 1.896 #10 of 79 Archive leaderboard report
Monocular Depth Estimation KITTI Eigen split Depth Anything RMSE log 0.069 #10 of 79 Archive leaderboard report
Monocular Depth Estimation KITTI Eigen split Depth Anything Sq Rel 0.121 #10 of 79 Archive leaderboard report
Monocular Depth Estimation KITTI Eigen split Depth Anything absolute relative error 0.046 #10 of 79 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 Depth Anything Delta < 1.25 0.984 #11 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 Depth Anything Delta < 1.25^2 0.998 #11 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 Depth Anything Delta < 1.25^3 1.000 #11 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 Depth Anything RMSE 0.206 #11 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 Depth Anything absolute relative error 0.056 #11 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 Depth Anything log 10 0.024 #11 of 85 Archive leaderboard report
Semantic Segmentation Cityscapes test Depth Anything Mean IoU (class) 84.8% #8 of 105 Archive leaderboard report
Semantic Segmentation Cityscapes val Depth Anything mIoU 86.2 #8 of 99 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections