OpenShot Video Editor: a Python 3 timeline over libopenshot and FFmpeg
OpenShot Video Editor is an award-winning free and open-source video editor for Linux, Mac, and Windows, and is dedicated to delivering high quality video editing and animation solutions to the world.
At a glance
- What is it?
- OpenShot Video Editor keeps its editing logic in Python 3 and pushes decoding, audio and rendering down into libopenshot, libopenshot-audio and FFmpeg. That split explains both how easily it starts from a source tree and how often the written documentation stops short of the controls you actually need.
- Who is it for?
- OpenShot suits someone who wants a free desktop editor with frame stepping, title templates, unlimited tracks and exports to EDL or XML, and who is willing to assemble a dependency stack by hand when no installer fits. It does not suit a team that needs documented shortcuts, proxy rendering or a supported downgrade path.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- OpenShot/openshot-qt6,790 ★ · +254
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| OpenShot/openshot-qt | 6.5k | 6.8k |
254 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The application layer is Python, the engine is not
Nothing in this repository has to be compiled before it will start, but it also will not start on its own. The dependency list asks for Python 3.0 or newer, a PyQt or PySide binding for Qt5 or Qt6, defusedxml for safe SVG title parsing, libopenshot for video work, libopenshot-audio for audio, FFmpeg or Libav, and GCC build tools, with MinGW named for Windows. The entry point is a script run from a checkout, and the path has to be edited to match wherever the tree lives:
cd [openshot-qt folder]
python3 src/launch.pysetup.py describes itself as the script that installs OpenShot on Linux while excluding native dependencies such as libopenshot, which confirms that the two libraries are acquired outside pip. defusedxml is the one dependency given with an install command: python3 -m pip install defusedxml. The top level of the tree mixes application code (src/), packaging (installer/, setup.py, MANIFEST.in, freeze.py), assets (images/), data files (xdg/) and docs (doc/), so a partial copy of src/ on its own is not a runnable editor.
Two separate switches pick the Qt generation
Which Qt ends up under the running window is decided twice, in two different places, by two parties. Packagers and developers select the Python binding through the OPENSHOT_QT_API environment variable, whose documented values are auto, pyqt6, pyside6 and pyqt5. The C++ side is chosen separately at configure time, where libopenshot takes -DUSE_QT6 as AUTO, ON or OFF. Nothing in the README ties those two decisions together. The word auto in the first switch has no documented resolution order, and no startup check is described that would report a mismatch before the window appears. There is also no per user override or settings entry documented for the variable, which leaves it in the hands of whoever packages or launches the process instead of in front of an editor at a workstation.
Daily builds and numbered releases answer different questions
The download page carries pre-built installers, and it also carries a Daily Builds button described as the latest, experimental builds, created for each new commit to this repository. Those two paths solve different problems. A numbered release is a point you can name later, and recent ones include v4.1.1 dated 2026-11-02, v4.1.0 dated 2026-10-31 and v4.0.1 dated 2026-09-27. A daily build tracks the develop branch, which is the default branch here, and whose last push is dated 2026-11-01. What neither path offers is a way back. There is no downgrade procedure, no changelog describing what changed between v4.1.0 and v4.1.1, no stated memory, disk or graphics requirements for any installer, and no checksum or signature guidance. A machine being upgraded therefore has nothing written down that predicts whether an earlier release can be restored if the new one misbehaves. Build status is split into three separate CI workflows, one for this repository, one for libopenshot and one for libopenshot-audio, so a passing workflow here says nothing about whether the libraries it links against still build.
An uninstalled libopenshot is reached through PYTHONPATH
Running against a libopenshot that was compiled but never installed takes an explicit path export, because the Python bindings land inside the CMake build directory rather than on the default search path:
cd [libopenshot folder]
cmake -B build -S . [options]
cmake --build build
cd [openshot-qt folder]
PYTHONPATH=[libopenshot folder]/build/bindings/python \
python3 src/launch.pyThe [options] placeholder is left unfilled in the documentation, so the configuration step is left to whoever builds the library, and the same is true of the two bracketed folders.
FFmpeg sits at both ends of the pipeline
Format handling is delegated outward. Clips are read through FFmpeg or Libav, and rendering returns through the same libraries across many codecs and formats. The stated feature set covers chroma key, brightness, gamma, hue and greyscale effects, compositing, image overlays and watermarks, audio mixing and editing, time mapping and speed changes on clips in either direction, and import and export of EDL and XML. Hardware paths are named but marked experimental: VA-API, NVDEC, D3D9, D3D11 and VTB. What none of those lines describes is the control surface around them. No export preset list, no bitrate or quality control, no proxy or background render workflow, and no per codec settings appear anywhere in the written documentation, so the render parameters you will reach for first are left to the running interface rather than to a reference you can check before committing to a long encode. Format coverage is likewise attributed to FFmpeg rather than to work in this repository, so which containers and codecs open successfully tracks the version of that library you happened to install, not the version of the editor.
The editing claims carry no limits and no numbers
The feature list is wide and mostly unquantified. The timeline is described as advanced, with drag and drop, scrolling, panning, zooming and snapping, and frames are said to be individually steppable for accuracy. Unlimited tracks and layers are listed, alongside curve based key frame animations, title templates, title creation, sub titles, 3D animated titles, scrolling credits and SVG friendly vector titles and credits. Not one of those lines carries a ceiling, a version qualifier or an outcome at the boundary. There is no documented undo depth, no autosave or crash recovery interval, no keyboard shortcut remapping, no statement about whether two people can open one project at once, and no measurement behind the word accuracy. Read as an inventory of intentions, the feature list is honest about scope and silent about cost, and the questions an editor has after a lost afternoon are not answered in it.
Repository housekeeping does not line up
Several edges of the tree disagree with each other, and each one matters when you are deciding whether to depend on the project. The README's license text names the GNU General Public License, version 3 or later, with redistribution and modification allowed and no warranty of merchantability or fitness for any purpose, while the repository's own license metadata reads NOASSERTION instead of a single identifier. The header inside setup.py carries a 2008-2016 copyright line while the main text runs to 2008-2022. The application translation link points at a Launchpad project versioned 2.0, while releases are on the 4.x line. Bugs are routed either through a guided form on the project site or straight to the GitHub issue tracker, with no response time stated for either route. Documentation is generated with Sphinx: cd doc followed by make html. Translation work is done in a browser through Launchpad, with step by step instructions linked for anyone who wants to become a translator.
Editorial conclusion
OpenShot suits someone who wants a free desktop editor with frame stepping, title templates, unlimited tracks and exports to EDL or XML, and who is willing to assemble a dependency stack by hand when no installer fits. It does not suit a team that needs documented shortcuts, proxy rendering or a supported downgrade path. Before committing to a daily build over v4.1.1, check what your own page reports about that build, because the repository offers no upgrade or rollback guidance.
Frequently asked questions
Is OpenShot really free?
Yes. OpenShot Video Editor is free software under the GNU General Public License, version 3 or later, so it can be redistributed and modified. It is also distributed with no warranty of merchantability or fitness for any particular purpose.
Why is OpenShot crashing?
The documentation gives no crash log format and no list of known crashes. Problems are collected through the guided report form on the project site or through the GitHub issue tracker, and neither route carries a stated response time.
What are the downsides of using OpenShot?
The costs that are written down are a dependency stack made of Python 3, a PyQt or PySide binding, libopenshot, libopenshot-audio and FFmpeg or Libav, a Qt binding chosen by an environment variable that must be matched separately from libopenshot's own Qt choice, and hardware encoding still listed as experimental.
Which is better, Shotcut or OpenShot?
The repository makes no comparison with Shotcut or with any other editor. Its only stated routes in are the pre-built installers, the experimental daily builds, and building from source against its own dependency list.
what is openshot qt
It is the desktop application repository for OpenShot Video Editor, written in Python 3 and layered on libopenshot and libopenshot-audio, with FFmpeg or Libav for decoding and rendering, running on Linux, Mac and Windows.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/openshot-openshot-qt)Star history chart for your README
[](https://hysenlabs.com/projects/openshot-openshot-qt)Was this useful?