Read CapCut Draft Timing: Declared Duration vs Observed End

Work through a synthetic timeline

The downloadable example has two segments: one starts at zero with a duration of 2,000,000, and one starts at 2,000,000 with a duration of 1,000,000. Under the inspector’s microsecond interpretation, the observed end is three seconds.

The root duration is also 3,000,000 in this example. Matching values establish that these recognized fields agree in the fixture. They do not certify an arbitrary CapCut schema or establish that the selected file is the active timeline.

Segment 1: start 0 + duration 2,000,000 = end 2,000,000
Segment 2: start 2,000,000 + duration 1,000,000 = end 3,000,000
Observed end: 3,000,000 microseconds = 3.000 seconds

Download the synthetic timing example ↓

Recognize a partial observation

The inspector requires nonnegative safe integer time fields and a safe sum. A missing, negative, non-integer or unsafe range is not included as a reliable observed end. A report can therefore summarize only the ranges it recognized.

Counts and timing are separate too: a segment entry can be counted without supplying a supported time range. Read the warnings before treating a smaller observed end as evidence that a later scene was deleted.

Compare the fields without guessing a repair

Verify in the appropriate application

Keep the selected JSON copy intact and note the project version and any timeline references. If you have the complete copied project, inspect the intended timeline in the relevant editor and check whether the visible content matches your expectation.

Draft Lens does not resolve references to nested files or linked media. Changing a duration number until it matches another field is not a supported repair. Use the report to frame a precise question, then investigate the project in a reversible copy.