Weave Code
Imagine Bundle Laravel Package
liip/imagine-bundle
LiipImagineBundle is an image manipulation toolkit for Symfony. Define filter sets in YAML or XML to apply thumbnails, scaling, cropping, flips, and more, with post-processors, caching, and responsive image support.
LiipImagineBundle is an image manipulation abstraction toolkit for Symfony projects. It lets you define reusable filter sets in YAML or XML, apply built-in transformations, and serve processed images through a configurable cache and resolver pipeline—keeping original uploads untouched while generated variations are handled automatically.
- Declarative filter sets pairing filters with post-processors
- Built-in filters: thumbnail, scale, crop, flip, strip, and more
- Cache and resolver abstraction for generated images
- Symfony integration with routing, Twig helpers, and controllers
- Extensible via custom filters, post-processors, and loaders
Frequently asked questions about Imagine Bundle
- Can I use liip/imagine-bundle in a Laravel application?
- Yes, but not natively. LiipImagineBundle is a Symfony bundle tightly coupled to Symfony's dependency injection and YAML/XML configuration, so a vanilla Laravel app needs a bridge such as spatie/laravel-symfony or a custom integration. If that overhead is unacceptable, use the underlying liip/imagine library directly and lose bundle features like filter sets, caching, and lifecycle events.
- How do I install liip/imagine-bundle in Laravel with Composer?
- Run composer require liip/imagine-bundle, but installation alone does not make it Laravel-ready. You must provide Symfony container integration and map Symfony-style filter set configuration into the Laravel app. Plan for compatibility testing because the bundle does not ship a native Laravel service provider.
- Does liip/imagine-bundle support Laravel 10 and Laravel 11?
- There is no official Laravel version support matrix because this is a Symfony bundle. As of 2.18.0 it targets PHP 8.1+, which aligns with Laravel 10 and newer, and integration depends on the Symfony bridge you choose. Treat Laravel compatibility as an integration concern and test your specific stack.
- What Symfony dependencies does liip/imagine-bundle bring into a Laravel project?
- The bundle pulls in Symfony components such as symfony/yaml and symfony/config plus the liip/imagine library. That increases dependency surface and can create version conflicts in Laravel projects. Using a Symfony integration bridge can mitigate some risk, but you should audit Composer constraints before adopting it.
- How do I configure LiipImagineBundle filter sets in Laravel?
- Filter sets are defined in Symfony-supported configuration formats such as YAML or XML, not Laravel's PHP config files. In Laravel you either bridge that configuration or duplicate settings between Symfony config and Laravel .env/PHP config, which adds maintenance overhead. Keep filter sets centralized and avoid the bundle for very simple image needs.
- Is liip/imagine-bundle a good alternative to Intervention Image for Laravel?
- They solve image manipulation differently. LiipImagineBundle offers declarative filter sets, post-processors, caching, and lifecycle events, but it expects Symfony integration. Intervention Image is more Laravel-native and simpler to adopt; choose Liip only if its filter-set and caching model justifies the Symfony bridge.
- What changed in LiipImagineBundle 2.18.0 that affects production Laravel apps?
- Version 2.18.0 adds a default_image fallback for missing filters or failed generation unless controller.debug is enabled, which is a behavioral change. It also fixes WebP cache variant deletion and adds CacheManager pre/post store and remove events. Map controller.debug to Laravel's APP_DEBUG and test the fallback path in staging before rollout.
- How does caching work with LiipImagineBundle and should I use Laravel cache?
- The bundle uses a Gaufrette-based caching layer for generated images, which is powerful but separate from Laravel's native cache. You need to align it with your Redis, CDN, or Laravel cache-tag strategy. The new CacheManager events in 2.18.0 can help trigger CDN purges or cache invalidation when images are stored or removed.
- What PHP version does liip/imagine-bundle require for Laravel projects?
- As of 2.18.0 the bundle requires PHP 8.1 or newer and dropped PHP 8.0 support. Laravel 10+ aligns well with that requirement, but legacy PHP 8.0 hosts must be upgraded before adoption. Confirm your production and CI environments match the bundle's PHP constraint.
- How do I wire LiipImagineBundle telemetry and image events into Laravel?
- Version 2.18.0 exposes filter lifecycle events plus CacheManager pre/post store and remove events that can be wired into Laravel's event and listener system. Use them for observability, CDN invalidation, or cache-tag cleanup rather than blocking image generation. Keep listeners lightweight and test failure cases.
Weaver
How can I help you explore Laravel packages today?