Checklist
- Launch Shotcut.
- Open a short clip you can discard.
- Drag it to the Timeline.
- Trim or split once.
- Export File to a new name.
- Play the export in a separate player.
- Optional: File → Save As for a
.mltproject.
Avoid on hour one
Do not install random filter packs, chase GPU toggles, or overwrite masters. Proof first.
Continue: installed, edit video, export MP4.
Why this door matters
A video editor install fails most often when the file comes from a renamed portal. Stick to GitHub Releases for mltframework/shotcut, winget Meltytech.Shotcut, Homebrew cask shotcut, Flatpak org.shotcut.Shotcut, or Snap shotcut. Those doors keep the binary aligned with Meltytech builds.
Write the door on the machine ticket beside the Windows build. That habit prevents a second install path from appearing after the next reimage. If SmartScreen prompts on a fresh signature, use More info and confirm Meltytech when Windows shows a publisher.
Proof export habit
After any install or update, open a short disposable clip, place it on the Timeline, and export one throwaway file. A video editor that launches but cannot export is not finished. Keep masters read-only while you learn the Export panel.
If export fails, try a software preset, confirm disk space, and retest with a tiny clip before you change GPU options. Save a .mlt project when you expect to reopen the cut. Prefer a new output filename every time so you never overwrite the only master.
Related pages on this guide
Continue with the Windows install walkthrough, the download-safe notes, the releases file map, and the installed checklist. Compare built-in editors when you only need a light trim. Use troubleshooting when SmartScreen, architecture mismatches, or failed exports block the first hour.
This video editor path stays local: media, timeline, and export output remain on disks you choose. Network is required for the first download and for package updates, not for everyday cutting once Shotcut is installed.
Lab and desk habits
Write the video editor install door on the machine ticket beside the Windows build. Prefer GitHub shotcut-win64-*.exe or winget Meltytech.Shotcut on x64 desks. After every reimage, run one proof export before you call the station ready.
Travel laptops without admin rights can use the portable zip with manual updates. Family PCs usually prefer the normal exe or winget so Start menu search finds Shotcut. Keep built-in trim tools available for a week when you are switching habits.
SmartScreen may warn on brand-new signatures. Use More info and confirm Meltytech when listed. Return to GitHub Releases if the publisher string looks unrelated. Checksums on the release tag help when a desk requires hash verification.
macOS and Linux doors stay honest in their install guides even though the Install panel on the home page stays Windows-primary. Brew cask shotcut, Flatpak org.shotcut.Shotcut, and Snap shotcut are verified when those desks matter.
A video editor install is complete only after a throwaway export plays in a separate player. Keep masters read-only while you learn Export presets. Save a .mlt project when you expect to reopen the cut later.
Frequently asked questions
What file type is the project?
Shotcut saves MLT XML projects with a .mlt extension. Prefer GitHub Releases for mltframework/shotcut or winget Meltytech.Shotcut on Windows x64, then finish one proof export before you change advanced settings.
Do I need a GPU on first run?
No. Finish a software export before you change GPU processing settings. Prefer GitHub Releases for mltframework/shotcut or winget Meltytech.Shotcut on Windows x64, then finish one proof export before you change advanced settings.
Where should exports go?
Pick a new folder and a new filename so masters stay untouched. Prefer GitHub Releases for mltframework/shotcut or winget Meltytech.Shotcut on Windows x64, then finish one proof export before you change advanced settings.