Install vapoursynth with Homebrew, dnf, MacPorts, Nix, pacman, scoop, winget, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• vapoursynth
• vspipe

Project history

The project was created by Fredrik Mellbin after he began thinking through alternative designs for AviSynth. The official introduction says most of the initial implementation was written over a three-month period, with the goal of making a 21st-century rewrite inspired by AviSynth rather than another direct clone.

Early public development was already active in 2012. Release posts from November 2012 discuss R15/R16 work on API changes, AviSynth compatibility, AVISource, and calls for users to port favorite AviSynth functions, filters, and scripts. By December 2013, R22 added Windows x64 support, removed the Qt dependency in favor of C++11, and reviewed locking so relevant functions were thread-safe.

Adoption history

VapourSynth grew in the same enthusiast video-processing culture that used AviSynth scripts for restoration, denoising, deinterlacing, inverse telecine, resizing, and encoding preparation. Its selling points for that audience were Python scripting, frame-level multithreading, runtime colorspace flexibility, per-frame properties, variable format support, and compatibility with many existing AviSynth plugins.

The project remains active as a niche but important tool in the video-encoding ecosystem. The GitHub project advertises the framework as 'with simplicity in mind', links to the official documentation, and shows a long release history, with R77 current in June 2026.

How it is used

Typical use is to write a `.vpy` Python script that builds a clip graph, loads source material, applies filters or third-party plugins, and emits frames through tools such as `vspipe` into encoders or preview applications. Package users care about the plugin ABI, Python bindings, bundled command-line tools, and whether the build exposes the same core behavior across macOS, Linux, and Windows.

Compared with line-oriented command-line transcoders, VapourSynth is usually not the final encoder. It is the programmable preprocessing layer: a precise, reproducible scriptable frameserver that can be inserted before x264, x265, FFmpeg-based workflows, or specialized restoration/upscaling pipelines.

Why package nerds care

For package maintainers, VapourSynth is interesting because it sits at the boundary between native multimedia libraries, Python packaging, and a plugin ecosystem. A useful package must provide the core library, Python module, command-line bridge, and enough ABI stability for separately packaged filters.

Its history also explains why distributions package it even though the audience is specialized: it is one of the main modern heirs to AviSynth-style scripted video processing, and it made that workflow portable and Python-based instead of tied to older Windows-centric tooling.

Timeline

• 2012: Official documentation copyright begins and early R15/R16 release posts describe API and AviSynth-compatibility work.
• 2013: R22 adds Windows x64 support, removes Qt, moves core code toward C++11, and improves thread safety.
• 2026: GitHub release history shows R77 as the latest release in June 2026.

Related projects

• AviSynth is the direct conceptual predecessor and compatibility target.
• VapourSynth plugins and scripts, including ports of AviSynth filters, form much of the practical ecosystem around the core.

Sources

• Official December 2013 release archive: https://www.vapoursynth.com/2013/12/
• Official GitHub repository: https://github.com/vapoursynth/vapoursynth
• Official November 2012 release archive: https://www.vapoursynth.com/2012/11/
• Official introduction: https://www.vapoursynth.com/doc/introduction.html