capcut-cli
Independent, unofficial CLI to edit CapCut and JianYing (剪映) projects — subtitles, timing, speed, volume, templates, cut long-form to shorts. No API needed, reads draft_content.json and draft_info.json (剪映草稿) directly. Not affiliated with ByteDance.
No outside reports on file
Use this tool only on your own video projects and only if you trust the source; keep it updated, monitor what files it accesses, and avoid using it with CapCut projects from untrusted sources.
Based on public adoption and transparency signals as of Oct 24, 2026. Our opinion, not a code audit or security guarantee.
What it can access
- Local filesNo local folder access notedLOW
- Command executionNo shell command runner notedLOW
- Network reachConnects to outside service APINOTED
- CredentialsNo API token requiredLOW
- Package sourceGitHub (renezander030/capcut-cli)PUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
No npm or PyPI package is listed. Install from source: github.com/renezander030/capcut-cli ↗
About Capcut CLI
This is an unofficial command-line tool that edits CapCut and JianYing (a Chinese video editor) project files directly. It can modify subtitles, timing, playback speed, volume, apply templates, and split long videos into short-form clips without needing CapCut's official API.
Who it’s for
Video editors who want to automate edits to CapCut projects using scripts or command-line commands. Developers building tools that need to batch-process or modify CapCut videos programmatically.
Alternatives
- FFmpeg: Open-source video processing tool; requires manual scripting but more transparent and widely audited.
- Adobe Premiere Pro scripting APIs: Official, supported way to automate video editing if you have a subscription.
- DaVinci Resolve command-line tools: Free video editor with some automation capabilities.
- Shot.co or Runway ML: Cloud-based video editing APIs with official support.
Setup
Check these steps against the project’s own instructions before running anything.
Follow the setup steps in the project’s official README: https://github.com/renezander030/capcut-cli (opens external site)
Why this grade
Signal-based grade (3/7 points): well starred on GitHub, public source code. This reflects adoption and transparency, not a code review.
Popularity and upkeep
- GitHub stars
- 1.1k
- Listing last refreshed
- 2026-10-29
These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.
Security reports
No reports found for this package in our research (last checked 2026-10-29).
Risks to watch for
- File access: The tool reads and writes CapCut project files (draft_content.json and draft_info.json) directly from your computer, so it has access to all your video project metadata and content paths.
- Unverified code: This is an unofficial, community-maintained tool not made by ByteDance or CapCut, so there's no guarantee updates are safe or that the code does only what it claims.
- Malicious project files: An attacker could craft a CapCut project file with specially designed data that tricks the tool into running harmful commands or exposing sensitive information.
- Data in transit: If you use this tool as part of a larger workflow, edited projects could be uploaded or shared without your knowledge.
- Supply chain risk: Updates to the npm package could theoretically be compromised, affecting all users who auto-update.
How to lower the risk
Least-privilege permissions
- Run the tool only when you need it, not as a background service.
- Store CapCut project files in a dedicated folder separate from sensitive data.
Network isolation
- Use the tool offline if possible; it shouldn't need internet after installation.
- Block outbound network access from your terminal or container if running automated edits.
Monitoring
- Watch which files the tool reads and writes using system logs or file auditing.
- Review project files before and after editing to spot unexpected changes.
Red flags to watch for
- Unexpected new versions with large code changes or downloads that spike.
- Tool requesting network access, passwords, or API keys.
- Crashes or strange behavior when editing certain project files.
Questions
How do I install Capcut CLI?
Capcut CLI does not publish a standalone npm or PyPI package. Clone or follow the setup instructions in its source repository at github.com/renezander030/capcut-cli.
Are there security reports about Capcut CLI?
No reports found for this package in our research (last checked 2026-10-29). Capcut CLI currently holds Grade C (Moderate risk signals) based on public adoption and transparency signals. Key risk areas to watch include file access, unverified code, malicious project files.
Is Capcut CLI actively maintained?
Capcut CLI has 1.1k GitHub stars. Our directory data was last refreshed on 2026-10-29. Check recent commit activity, release tags, and open issues at github.com/renezander030/capcut-cli before pinning it in production.
What are alternatives to Capcut CLI?
Notable alternatives to Capcut CLI include FFmpeg (Open-source video processing tool), Adobe Premiere Pro scripting APIs (Official, supported way to automate video editing if you have a subscription), DaVinci Resolve command-line tools (Free video editor with some automation capabilities), Shot.co or Runway ML (Cloud-based video editing APIs with official support). You can also compare Capcut CLI side by side with other skills in the Related tools section on this page.
Key facts
- Type
- AI agent skill
- Publisher
- renezander030
- Source code
- github.com/renezander030/capcut-cli
- Est. context load
- ~89 tokens idle · ~450 tokens when active (on-demand skill)
- Popularity
- 1.1k GitHub stars
- Last updated
- 2026-10-29
- Last graded
- 2026-10-24
Community
Discussions for Capcut CLI
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.
Check before you install, in Claude
Your assistant answers Block, Review or No known issues for any package before it installs it.
Get this check inside Claude