Install and verify
The system libvips package and a language package are different installs. pyvips and govips usually need a discoverable system libvips. A prebuilt sharp package can carry its own copy. Elixir Image depends on Vix, and Vix can also ship its own libvips. Recording only the binding version is not enough to reproduce encoders and format support.
Version baseline on the verification host
Section titled “Version baseline on the verification host”The table records the example container used to verify the examples in this handbook.
| Component | Version observed | libvips it loaded |
|---|---|---|
| vips CLI | 8.17.3 | 8.17.3 |
| pyvips | 3.2.0 | 8.17.3 |
| sharp | 0.35.5 | 8.18.7, bundled in the package |
| Go | 1.27.0 | Does not ship libvips. Executed examples use govips v2.20.0 linked to the system libvips 8.17.3 above |
| Node.js | 24.14.1 | See sharp |
| Python | 3.14.5 | See pyvips |
govips has no separate version command. Executed examples record v2.20.0 together with system libvips 8.17.3.
How that container is assembled, which loaders it keeps, and the full container definition are in Docker Runner.
Elixir / Image
Section titled “Elixir / Image”The Image combination checked on 2026-10-16 is Elixir 1.20.4, OTP 29.1.2, image 0.72.0, and Vix 0.42.0, loading libvips 8.17.3. Those examples set VIX_COMPILATION_MODE=PLATFORM_PROVIDED_LIBVIPS at compile time and at runtime, so they link that system library rather than the prebuilt libvips Vix bundles by default.
The usual path on a reader’s machine is still Vix’s bundled library. Format support and encoded bytes can differ between the two paths, so the install record has to name which one was used.
{:image, "0.72.0"}After the application starts, print the Image, Vix, and libvips versions together:
{:ok, _} = Application.ensure_all_started(:image)IO.puts( "#{Application.spec(:image, :vsn)} #{Application.spec(:vix, :vsn)} #{Vix.Vips.version()}")The Image 0.72.0 documentation does not list Elixir 1.20.4 or OTP 29.1.2 among its supported combinations. The versions above are what compiled and ran the thumbnail, format conversion, geometry, alpha, and colour recipes in this check. They are not a promise copied from the upstream support table.
Reference install commands for other platforms
Section titled “Reference install commands for other platforms”These two commands come from the official libvips install guide, reviewed 2026-10-12.
Development package on Ubuntu or Debian:
sudo apt-get updatesudo apt-get install libvips-devHomebrew on macOS:
brew install vipsAfter installing, check the CLI version with vips --version. A distribution package can be older than 8.17.3; verify that your target operations exist in that version before relying on behaviour from this handbook.
Install a binding
Section titled “Install a binding”Go / govips
Section titled “Go / govips”go get github.com/davidbyttow/govips/v2@v2.20.0govips uses CGO. If the compiler cannot find headers, check that pkg-config --modversion vips matches the system library you intend to use.
Node.js / sharp
Section titled “Node.js / sharp”npm install sharp@0.35.5node -e "import('sharp').then(({default:s}) => console.log(s.versions))"Keep both sharp and vips from that output. The 0.35.5 prebuilt package carried libvips 8.18.7 in this check.
Python / pyvips
Section titled “Python / pyvips”python -m pip install pyvips==3.2.0python -c "import pyvips; print(pyvips.__version__, pyvips.version(0), pyvips.version(1), pyvips.version(2))"Sources
Section titled “Sources”- libvips install guide, reviewed 2026-10-12
- sharp install guide
- pyvips README
- govips README
- Image 0.72.0 documentation, reviewed 2026-10-16
- Vix repository
- Version compatibility matrix