Installer vips avec Homebrew, apk, dnf, MacPorts, Nix, apt, zypper

Liens du projet

• Page d'accueil
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• vips
• vipsedit
• vipsheader
• vipsthumbnail

Historique du projet

The VIPS lineage predates the libvips GitHub repository by decades. The project's own history traces ideas to Kirk Martinez's PhD software from 1986 onward and serious development to the VASARI project, which began in July 1989, with John Cupitt as a key programmer. Early design notes emphasized integer arithmetic, optimized inner loops, pointer-oriented image access, disk layout, and algorithm choice, all themes that still match libvips' performance identity.

The first major VIPS paper was 'VIPS: An image processing system for large images' by Cupitt and Martinez in SPIE proceedings in 1996, followed by a 2005 IEEE International Conference on Image Processing paper on VIPS as a highly tuned image-processing software architecture. The project history credits continuous EU research funding across imaging, printing, search/retrieval, 3D imaging, and web-viewing work, followed by open-source community contributions that stabilized and broadened the library.

Historique d'adoption

libvips moved from research and cultural-heritage imaging into mainstream package ecosystems by becoming the engine for image processing stacks such as sharp for Node.js, bimg, imgproxy, MediaWiki thumbnailing, Rails Active Storage pathways, CarrierWave integrations, and other services listed by the project. Its project wiki also notes use in PARSEC as a benchmark for parallel systems and in high-resolution image browsing/archive workflows.

The modern GitHub project remains active, with the public repository created in January 2011 and release metadata showing continued 8.x maintenance into 2026. The repository had more than eleven thousand stars and hundreds of forks at lookup time, but the stronger adoption signal is the presence of libvips behind high-volume wrappers and web image services.

Modes d'utilisation

The typical libvips usage pattern is batch or service-side image transformation: load an image or stream, construct a pipeline of operations, and let libvips evaluate the necessary regions with low memory overhead. Common tasks include thumbnails, resizing, format conversion, DeepZoom pyramids, color management, convolution, morphology, statistics, and large TIFF/scientific image handling.

Package users encounter it both directly through commands such as vips, vipsheader, vipsthumbnail, and vipsedit, and indirectly through bindings such as pyvips, ruby-vips, NetVips, php-vips, and sharp. In package-nerd terms, libvips is the small, fast native engine that lets higher-level ecosystems avoid routing every resize or thumbnail job through heavier image stacks.

Pourquoi les passionnés de paquets s'y intéressent

libvips is significant because it occupies a different design point from ImageMagick-style whole-image processing: it streams demand-driven regions through horizontally threaded pipelines, minimizing memory pressure and synchronization. That makes it especially attractive to package ecosystems that process untrusted, user-supplied, or very large images at server scale.

It also has unusual continuity: a 1980s/1990s research-image-processing system that survived into modern package managers, language bindings, web frameworks, and containerized services without losing its niche identity around speed and memory behavior.

Chronologie

• 1986: VIPS roots begin in Kirk Martinez's PhD-era image-processing software.
• 1989-07: Serious VIPS development begins with the VASARI project.
• 1996: Cupitt and Martinez publish 'VIPS: An image processing system for large images.'
• 2005: Martinez and Cupitt publish a paper on the VIPS software architecture at IEEE ICIP.
• 2011-01: The libvips/libvips GitHub repository is created.
• 2026: The 8.18.x release series is active, with current API docs published for Vips 8.0 / library 8.18 during this run.

Related projects

• Related projects include nip4/nip2 graphical front ends, vipsdisp, sharp, pyvips, ruby-vips, NetVips, imgproxy, bimg, MediaWiki VipsScaler/Thumbro, OpenSlide/IIPImage/OpenSeadragon image-pyramid workflows, and PARSEC.

Sources

• https://github.com/libvips/libvips
• https://github.com/libvips/libvips/wiki/Projects-using-libvips
• https://github.com/libvips/libvips/wiki/Speed-and-memory-use
• https://github.com/libvips/libvips/wiki/VIPS-History
• https://github.com/libvips/libvips/wiki/Why-is-libvips-quick
• https://www.libvips.org/API/current