Field SOP
Field SOP

Building a Zero-Cost Video Editing SOP with Shotcut: A 5-Step Open-Source Workflow

An open-source video editing SOP: a full Shotcut multi-track + AI-assisted (subtitles, smart transitions, grading) workflow in five steps -- organize footage, rough multi-track cut, AI subtitles/transitions, color grading and keyframes, export and distribute. Includes runnable commands, 5 pitfalls, and 5 FAQs; a zero-cost Premiere replacement.

Published August 12, 20268 min read
<!-- opensource-video-editing-sop | sop | Building a Zero-Cost Video Editing SOP with Shotcut: A 5-Step Open-Source Workflow -->

Short-video creators are trapped by subscription fees and repetitive labor: Premiere Pro costs a premium, CapCut's pro features are increasingly paywalled, and cracked software carries legal risk. Shotcut is a free, open-source, cross-platform video editor (Win/Mac/Linux) built on FFmpeg, supporting multi-track editing, filters, color grading, and keyframes. Version 26.2, no watermark. It replaces about 80% of everyday Premiere/CapCut editing needs. But be clear: Shotcut's built-in AI features are limited -- AI assistance (subtitle generation, smart processing) relies on external open-source tools. This article is honest about that; every command given is real and runnable. The SOP is a five-step pipeline: material organization and proxy -> rough cut multi-track -> AI subtitles and transitions -> color grading and keyframes -> export and distribution. Companion piece to our Shotcut review: that article answers "should you pick Shotcut," this one answers "how to build a pipeline with it."


1. Why Shotcut

Shotcut is not a full-feature Premiere replacement. It is a zero-cost solution covering 80% of everyday editing. Core strengths: multi-track timeline, native drag-and-drop editing (no media bin import needed), FFmpeg core supporting nearly all formats, cross-platform project portability, no watermark or time limits.

DimensionShotcutPremiere ProCapCut ProKdenlive
PriceFree open-sourceSubscriptionFree + paidFree open-source
Cross-platformWin/Mac/LinuxWin/MacWin/MacWin/Mac/Linux
Multi-trackYesYesYesYes
AI subtitlesNone (external)YesYesNone (external)
WatermarkNoneNoneYes (free tier)None

Shotcut's gaps: no built-in AI subtitles, no smart transition recommendations, weaker color grading than DaVinci Resolve. These are covered by external tools: Whisper for subtitles, FFmpeg for preprocessing and post-optimization, Shotcut for multi-track compositing and color.


2. The Five-Step SOP

Step 1: Material Organization and Proxy Generation

Footage from different devices comes in mixed formats (HEVC, AV1, H.264). Direct editing causes lag. First transcode to proxy format (low-res H.264) with FFmpeg for smooth editing, then switch back to source footage for final export.

bash
#!/bin/bash
# Run in the footage directory, creates proxy subfolder
mkdir -p proxy
for file in *.MP4 *.mov *.avi; do
  [ -f "$file" ] || continue
  name="${file%.*}"
  ffmpeg -i "$file" -c:v libx264 -preset fast -crf 23 \
    -vf "scale=960:-2,fps=30" -c:a aac -b:a 128k \
    "proxy/${name}_proxy.mp4"
done

-crf 23 is reasonable for proxy quality (does not need to be high; proxy is just for smooth editing). scale=960:-2 downscales width to 960px. In Shotcut, enable proxy mode via "Settings -> Proxy" and point to the proxy directory.

Step 2: Rough Cut Multi-Track

Open Shotcut and drag proxy clips directly to the timeline (no media bin import needed -- this is Shotcut's native timeline feature). Create three tracks: V1 main footage, V2 overlays (screenshots, B-roll), A1 audio.

Rough cut operations: use I / O keys to set in/out points, X to cut selected segments, remove filler words, pauses, and bad takes. Shotcut's multi-track editing supports track switching, solo/mute -- operation logic is similar to Premiere. This step does not need to be precise; the goal is to arrange clips in script order and remove obvious junk.

Step 3: AI Subtitles and Transitions

Subtitles use Whisper. Shotcut has no built-in AI subtitles. Use the open-source Whisper model to generate SRT, then import into Shotcut. Recommended: whisper.cpp (C++ implementation, runs on CPU):

bash
# Install whisper.cpp
git clone https://github.com/ggerganov/whisper.cpp.git
cd whisper.cpp && make

# Download model (base ~142MB; medium better for Chinese)
./models/download-ggml-model.sh medium

# Extract audio from video, then generate subtitles
ffmpeg -i proxy/talking_proxy.mp4 -vn -ac 1 -ar 16000 -c:a pcm_s16le audio.wav
./main -m models/ggml-medium.bin -l zh -f audio.wav -osrt

Import the generated SRT into Shotcut via "View -> Subtitles", where you can edit text and adjust the timeline. Whisper's Chinese accuracy with the medium model reaches 90%+ in quiet environments; proper nouns still need manual correction.

Transitions use Shotcut's built-in filters. Shotcut has no AI transition recommendations. Manually drag transition filters (fade, dissolve, slide) to the head/tail filter area of clips. Shotcut 26.2 supports track-to-track transitions (upper track clips overlay onto lower), more flexible than earlier versions.

Step 4: Color Grading and Keyframes

Shotcut's color grading is filter-based. Three core filters: Color Grading, Curves, White Balance. Right-click a clip -> Filters -> Add, then adjust parameters.

Keyframe animation: nearly all filter parameters support keyframes. Click the bell icon next to a parameter in the filter panel, set keyframes at different timeline positions, and parameter values auto-interpolate. Typical uses: brightness fade-in, zoom push, position move.

Shotcut's color grading is weaker than DaVinci Resolve, but sufficient for skin tone correction, exposure compensation, and stylization in short videos.

Step 5: Export and Distribution

After editing, disable proxy mode and switch back to source footage for export (to preserve quality). Shotcut's export panel offers presets: YouTube 1080p, H.264, H.265, and more. Recommended presets:

  • YouTube 1080p H.264: 8-12 Mbps, best compatibility
  • H.265 HEVC: 4-6 Mbps, half the file size, similar quality

For further compression or format conversion, use FFmpeg post-export:

bash
# Compress (H.265, good for storage)
ffmpeg -i export.mp4 -c:v libx265 -crf 28 -c:a aac -b:a 128k final.mp4

# Extract cover frame
ffmpeg -i export.mp4 -ss 00:00:01 -vframes 1 cover.jpg

3. Five Pitfalls

Pitfall 1: Non-ASCII paths break FFmpeg FFmpeg and Whisper handle non-ASCII paths poorly, causing No such file or directory errors. Fix: use English and underscores for all working directories and filenames, e.g. project_01/take_a_proxy.mp4.

Pitfall 2: Proxy files disconnect from source Editing with proxy but failing to switch back to source at export ruins quality. Fix: after enabling proxy mode in Shotcut, confirm "Use Proxy" is off before exporting; keep clear naming correspondence (e.g. name_proxy.mp4 maps to name.MP4).

Pitfall 3: Wrong Whisper model exhausts VRAM Using the large model with only integrated graphics causes OOM crashes. Fix: start with base or small models in whisper.cpp; use medium with 6GB+ VRAM; large needs 10GB+. On CPU, the small model processes a 30-minute video in about 15-20 minutes.

Pitfall 4: Unfamiliar keyframe interpolation curves Shotcut defaults to linear interpolation, making zoom/pan movements look stiff. Fix: right-click keyframes to switch interpolation (ease-in, ease-out, ease-in-out, discrete). Use ease-in-out for natural camera pushes.

Pitfall 5: Wrong export preset ruins quality or bloats file size Low bitrate presets cause mosaic artifacts; lossless formats produce 20GB files for 10 minutes of video. Fix: use H.264 at 8-12 Mbps for short videos; H.265 CRF 28 for smaller files; avoid lossless presets unless you need further post-processing.


FAQ

Q1: Shotcut or Kdenlive -- both are free and open-source, which to choose? A1: Both use the MLT framework. Shotcut is smoother cross-platform and has more intuitive native timeline drag-and-drop, ideal for creators switching between systems. Kdenlive has richer multi-track audio and effects, better for heavy users migrating from Premiere. Try both and pick the one that feels right -- project files are not interchangeable.

Q2: Can I run Whisper subtitles without a dedicated GPU? A2: Yes. whisper.cpp supports CPU inference; the small model processes a 30-minute video in about 15-20 minutes on CPU. No GPU does not block the workflow, just slower. With 6GB+ VRAM, use the medium model for better Chinese accuracy.

Q3: Can Shotcut fully replace Premiere? A3: No, but it covers about 80%. Shotcut lacks: built-in AI subtitles, dynamic linking (with AE/PS), advanced audio mixing, team collaboration. If your workflow does not depend on these, Shotcut is sufficient. For heavy effects and color grading, DaVinci Resolve or Premiere is stronger.

Q4: Does proxy editing degrade final export quality? A4: No, as long as you switch back to source footage at export. Proxy only uses low-res stand-ins during editing for smoothness; Shotcut automatically calls original footage for final render. If quality seems off, check that "Use Proxy" is disabled in export settings.

Q5: Are Shotcut project files portable between Windows and Mac? A5: Yes. Shotcut project files (.mlt format) are XML and cross-platform compatible. Note: footage file paths need re-linking across systems (Windows drive letters differ from Mac paths). After opening the project in Shotcut, right-click missing clips to re-link.


References

This article is AI-assisted and human-edited. Last updated: 2026-08-12

FAQ

Shotcut or Kdenlive -- both are free and open-source, which to choose?
Both use the MLT framework. Shotcut is smoother cross-platform and has more intuitive native timeline drag-and-drop, ideal for creators switching between systems. Kdenlive has richer multi-track audio and effects, better for heavy users migrating from Premiere. Try both and pick the one that feels right -- project files are not interchangeable.
Can I run Whisper subtitles without a dedicated GPU?
Yes. whisper.cpp supports CPU inference; the `small` model processes a 30-minute video in about 15-20 minutes on CPU. No GPU does not block the workflow, just slower. With 6GB+ VRAM, use the `medium` model for better Chinese accuracy.
Can Shotcut fully replace Premiere?
No, but it covers about 80%. Shotcut lacks: built-in AI subtitles, dynamic linking (with AE/PS), advanced audio mixing, team collaboration. If your workflow does not depend on these, Shotcut is sufficient. For heavy effects and color grading, DaVinci Resolve or Premiere is stronger.
Does proxy editing degrade final export quality?
No, as long as you switch back to source footage at export. Proxy only uses low-res stand-ins during editing for smoothness; Shotcut automatically calls original footage for final render. If quality seems off, check that "Use Proxy" is disabled in export settings.
Are Shotcut project files portable between Windows and Mac?
Yes. Shotcut project files (.mlt format) are XML and cross-platform compatible. Note: footage file paths need re-linking across systems (Windows drive letters differ from Mac paths). After opening the project in Shotcut, right-click missing clips to re-link.

Related

Field SOP

LLaDA-Image Local Deploy SOP: Setup, Inference, Production

A five-step SOP for running Ant's open-source 6B image model LLaDA-Image: (1) environment setup with dependencies and mirror-accelerated downloads; (2) choosing among four weight variants (Base 50-step / Turbo 4-step, each in BF16 or FP8, with ModelScope for China); (3) generating the first image with minimal Base and Turbo commands; (4) advanced work - reference-image editing, text rendering, ComfyUI integration, and degradation strategies when VRAM runs short; (5) productionizing with batch queues, concurrency sizing, cost monitoring, result storage and graceful failure modes. Includes 6 pitfalls and a 10-item launch checklist, with every command copied verbatim from the official README; note the repo license is null, so confirm rights before commercial use.

Sep 9, 202611 min read
Field SOP

Self-Hosting OpenMAIC: From Zero-Deploy to Agent Workbench

A complete SOP for getting OpenMAIC running from zero: (1) zero-deploy hosted mode with an access code from open.maic.chat; (2) standard local setup (pnpm >= 10: clone, pnpm install, .env, pnpm dev); (3) production (pnpm build && pnpm start, one-click Vercel, docker compose up --build); (4) advanced (Postgres persistence profile, ACCESS_CODE, MP4 export profile, Lemonade/FunASR local providers); (5) wiring it into agent workbenches (clawhub install openmaic or importing skills/openmaic/, generating classrooms from Feishu/Slack messages). Includes 6 pitfalls and a 10-item pre-launch checklist, with every command copied verbatim from the official README.

Sep 8, 202611 min read
Field SOP

Kimi Dual Protocol: One Config for Codex and Claude Code

Moonshot announced on 2026-09-02 that the Kimi API natively supports dual protocols: OpenAI Responses (api.moonshot.cn/v1) plus Anthropic Messages (api.moonshot.cn/anthropic), with kimi-k3 as the flagship model. Hands-on SOP: point Claude Code's ~/.claude/settings.json ANTHROPIC_BASE_URL to /anthropic with model kimi-k3[1m]; set Codex's ~/.codex/config.toml wire_api="responses". This turns Kimi into a unified model-routing gateway — switch the backend without touching client code. Boundaries: Responses is text+image only, kimi-k2.7-code forces thinking, and the old ANTHROPIC_API_KEY must be removed.

Sep 5, 202611 min read