DRAFT LENS · PRACTICAL GUIDE
Why Valid JSON Does Not Prove a CapCut Project Will Open
By BestTools ·
Valid JSON only proves that the bytes can be parsed as JSON. It does not prove the object follows a CapCut version’s project schema or can locate its media.
Separate four different checks
| Layer | Question |
|---|---|
| Encoding | Can the selected bytes be read as supported UTF-8 text? |
| Syntax | Does the text parse as JSON? |
| Recognized structure | Does the selected object contain the limited fields Draft Lens checks? |
| Application behavior | Can the intended CapCut version open the copied project and use its dependencies? |
Use a valid object that is not a timeline
The example below is syntactically valid JSON. It has a name and a note but no root tracks array. Draft Lens can report metadata-shaped JSON without inventing a timeline count.
A root tracks array is also not a universal compatibility certificate. Newer layouts, nested files and references outside the selected copy can change what an editor needs. The inspector deliberately leaves those questions unresolved.
{"draft_name":"Synthetic example","note":"Metadata only"}Respond to the actual status
- If decoding is unsupported, keep the bytes and find a supported original export or backup copy.
- If JSON parsing fails, preserve the file rather than guessing which characters to delete.
- If JSON is valid but fields are unrecognized, record the status and version context.
- If timeline-shaped fields are recognized, inspect the counts and warnings without treating them as recovery proof.
- Test a separate copied project in the relevant editor with its media dependencies available.
Avoid edits that hide the evidence
Inserting braces, deleting unfamiliar fields or copying version numbers from a different file can make one test pass while removing useful information. A parser success after a manual edit does not establish that the edit repaired the project.
Draft Lens never writes back to your selected file. Its report is a limited description of what it could read. Keep that report, the untouched copy and a record of the editor’s actual error separate so later investigation can distinguish them.
Sources and further reading
Sources checked on 2026-10-26. Platform menus and supported formats can change.