Papers › Video Depth Anything: Consistent Depth Estimation for Super-Long Videos

Video Depth Anything: Consistent Depth Estimation for Super-Long Videos

21 Jan 2025CVPR 2025 1arXiv:2501.12375archive 2025-07-28

Sili Chen, Hengkai Guo, Shengnan Zhu, Feihu Zhang, Zilong Huang, Jiashi Feng, Bingyi Kang

Depth Anything has achieved remarkable success in monocular depth estimation with strong generalization ability. However, it suffers from temporal inconsistency in videos, hindering its practical applications. Various methods have been proposed to alleviate this issue by leveraging video generation models or introducing priors from optical flow and camera poses. Nonetheless, these methods are only applicable to short videos (< 10 seconds) and require a trade-off between quality and computational efficiency. We propose Video Depth Anything for high-quality, consistent depth estimation in super-long videos (over several minutes) without sacrificing efficiency. We base our model on Depth Anything V2 and replace its head with an efficient spatial-temporal head. We design a straightforward yet effective temporal consistency loss by constraining the temporal depth gradient, eliminating the need for additional geometric priors. The model is trained on a joint dataset of video depth and unlabeled images, similar to Depth Anything V2. Moreover, a novel key-frame-based strategy is developed for long video inference. Experiments show that our model can be applied to arbitrarily long videos without compromising quality, consistency, or generalization ability. Comprehensive evaluations on multiple video benchmarks demonstrate that our approach sets a new state-of-the-art in zero-shot video depth estimation. We offer models of different scales to support a range of scenarios, with our smallest model capable of real-time performance at 30 FPS.

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

By repository: community (archive-listed): 10 samples from 1 repository, 10 ran (3 with no instrument failure; 7 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.

Levels written between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 2 of the 10 samples that ran have no recorded date.

DepthAnything/Video-Depth-Anything mentioned on GitHubpytorchApache-2.0Syntology: 10 samples, 10 ran (7 instrument-failed) · 0 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.

Code Syntology ran Syntology

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

1ran · honoured contract
1ran · violated contract
2ran · our draft was wrong
5ran; the contract check could not run
1ran

Licence: 1 of the 10 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from DepthAnything/Video-Depth-Anything. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

DepthAnything/Video-Depth-Anything community (archive-listed) 10 samples, 10 ran (7 instrument-failed) · 0 unverified
add_residual in 18 papers video_depth_anything/dinov2_layers/block.py ran; the contract check could not run (RAISES) Apache-2.0 (permissive) · 5d16d4d4fc573ac7 · report fixture: signature x:Tensor/2/float, brange:Tensor/1/int, residual:Tensor/2/float, residual_scale_factor:float/0/float, scaling_vector:NoneType/0/? · returned Tensor · level recorded 2026-09-26
apply_rotary_emb in 121 papers video_depth_anything/motion_module/attention.py ran Apache-2.0 (permissive) · 307785ce73cb99aa · report fixture: signature xq:Tensor/3/float, xk:Tensor/3/float, freqs_cis:Tensor/2/complex · returned tuple · level recorded 2026-09-24
drop_add_residual_stochastic_depth in 26 papers video_depth_anything/dinov2_layers/block.py ran; the contract check could not run (RAISES) Apache-2.0 (permissive) · 85f7ffc01945bb72 · report fixture: signature x:Tensor/3/float, residual_func:callable/0/?, sample_drop_ratio:float/0/float · returned Tensor · level recorded 2026-09-26
drop_path in 325 papers
census: 27 implementations from 61 papers, 5 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 4, kind float, dtype float32
video_depth_anything/dinov2_layers/drop_path.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant Apache-2.0 (permissive) · c157f5b112b3a392 · report fixture: signature x:Tensor/4/float, drop_prob:float/0/float, training:bool/0/bool · returned Tensor · level recorded 2026-09-22
get_branges_scales in 18 papers video_depth_anything/dinov2_layers/block.py ran; the contract check could not run (RAISES) fingerprinted Apache-2.0 (permissive) · 5be3610fa1fee19e · report fixture: signature x:Tensor/3/float, sample_drop_ratio:float/0/float · returned tuple · level recorded 2026-09-26
make_2tuple in 21 papers video_depth_anything/dinov2_layers/patch_embed.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · 3c04490a215299f2 · report fixture: signature x:int/0/int · returned tuple · level recorded 2026-09-22
named_apply in 32 papers video_depth_anything/dinov2.py ran · our draft was wrong Apache-2.0 (permissive) · e7fcb6d9ac9deaf4 · report fixture: signature fn:callable/0/?, module:callable/0/?, name:str/0/str, depth_first:bool/0/bool, include_root:bool/0/bool · returned SimpleModel · level recorded, date not recorded
precompute_freqs_cis in 112 papers video_depth_anything/motion_module/attention.py ran · violated contract Apache-2.0 (permissive) · e93cc5b705c2eb3b · report fixture: signature dim:int/0/int, end:int/0/int, theta:float/0/float · returned Tensor · level recorded 2026-09-22
reshape_for_broadcast in 90 papers
census: 6 implementations from 10 papers, 1 distinct output on one shared input
video_depth_anything/motion_module/attention.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · 70bf6ebaafd266c4 · report fixture: signature freqs_cis:Tensor/2/float, x:Tensor/4/float · returned Tensor · level recorded, date not recorded
zero_module in 184 papers video_depth_anything/motion_module/motion_module.py ran · our draft was wrong Apache-2.0 (permissive) · 4719c763c53be3fe · report fixture: signature module:callable/0/? · returned SimpleModule · level recorded 2026-09-22

Tasks

Computational EfficiencyDepth EstimationMonocular Depth EstimationOptical Flow EstimationVideo Generation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

BASE

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