Do you have the installation package for CapCut 6.2.8?

[0xLDF]

Do you have the installation package for CapCut 6.2.8? I’ve found that versions 6.3.0 and 9.1.0 both fail to work properly. An error message pops up when I try to open my drafts, stating that this draft comes from an unconventional path and is temporarily unsupported.

[renezander030]

Hi @0xLDF,

No, I can't share a CapCut installer. That binary is ByteDance's to distribute, not this repo's. But I don't think downgrading is the fix you actually need.

"This draft comes from an unconventional path and is temporarily unsupported" is the app rejecting the draft's registration, not its content. CapCut only opens drafts that are listed in root_meta_info.json under the draft root it is currently configured to use. A folder created or moved outside that root, or one whose draft_root_path entry still points at an old location, gets exactly that message. Same family as #32 and #21.

Two things to try first:

1. Confirm where the app expects drafts. capcut doctor prints the detected store for your OS. The defaults are:

• Windows: %LOCALAPPDATA%\CapCut\User Data\Projects\com.lveditor.draft (JianYing: ...\JianyingPro\User Data\...)
• macOS: ~/Movies/CapCut/User Data/Projects/com.lveditor.draft

The project folder has to sit inside that directory.

2. Repair the registration. Close CapCut, then:

capcut register "<path/to/project>"           # prints the plan, writes nothing
capcut register "<path/to/project>" --apply   # writes, with .bak

It rebuilds draft_meta_info.json and the root_meta_info.json entry from your draft_content.json. If the draft lives outside a known store, add --drafts <dir>.

One likely cause, and it's on me. If you created the draft with capcut init or capcut quickstart (no --drafts) on Windows or Linux, the CLI put it in the wrong place. Those commands default to the macOS store and never branch per OS, unlike capcut doctor, which does know the Windows paths. On Windows HOME is usually unset, so the default collapses to a literal ~/Movies/CapCut/... folder next to your working directory. CapCut would reject a draft there with exactly your message, on any version. Until that's fixed, pass --drafts explicitly:

capcut init myproject --drafts "%LOCALAPPDATA%\CapCut\User Data\Projects\com.lveditor.draft"

If it still refuses to open, I'd like to fix it properly rather than guess. 6.3.0 and 9.1.0 are both listed as "expected-compatible, unverified" in docs/version-support.md for exactly this reason: no app-created fixture from those versions has been committed yet. Could you post:

• OS, and the exact version string the app reports
• whether the draft was created by capcut init or by CapCut itself, and whether it was ever moved or copied between machines
• output of capcut version "<project>" and capcut diagnose "<project>" -H
• ideally capcut diagnose "<project>" --bundle, which writes a sanitized bundle (no media, no personal paths) you can attach here

With a real folder from 6.3.0 or 9.1.0 I can commit a fixture and a regression test, which moves those rows off "unverified" and stops the CLI from producing drafts your version won't accept.

[renezander030]

Found a real bug behind this, so the fix is in rather than a workaround.

init, quickstart and compile (without --out) resolved their default draft store from a hardcoded macOS path built on $HOME, on every platform. doctor already knew the Windows stores, but nothing else used that list. On Windows, where HOME is normally unset, the default collapsed to a literal ~/Movies/CapCut/User Data/Projects/com.lveditor.draft folder created next to your working directory. CapCut refuses a draft there with exactly your message, on any app version. That would explain why 6.3.0 and 9.1.0 both failed for you and why finding a 6.2.8 installer would not have helped.

Merged in #53:

• draft-creating commands resolve the store per OS now, Windows from LOCALAPPDATA (falling back to USERPROFILE), never from HOME
• CAPCUT_DRAFT_DIR overrides it everywhere
• a platform with no known store exits 1 naming --drafts and CAPCUT_DRAFT_DIR, instead of writing a draft the editor will not open
• CI now runs the suite on Windows, macOS and Linux for this path

Two things for you:

1. Drafts already created in the wrong place are not lost. Move the folder into the store capcut doctor reports, then capcut register "<path/to/project>" --apply (close CapCut first) to rebuild draft_meta_info.json and the root_meta_info.json entry.
2. If you were creating drafts by hand rather than with the CLI, this fix does not cover your case, and I would still like the details: OS, exact app version, and capcut diagnose "<project>" --bundle, which writes a sanitized bundle with no media or personal paths. 6.3.0 and 9.1.0 are still "expected-compatible, unverified" in docs/version-support.md for lack of a real app-created fixture.

Leaving this open until you confirm it opens for you.

[renezander030]

Reopening: the merge auto-closed this via the PR's Fixes line, but I'd rather keep it open until @0xLDF confirms the draft opens.