Weave Code
Picasso Bundle Laravel Package
silarhi/picasso-bundle
Symfony bundle that integrates Picasso for on-the-fly image manipulation, letting you resize, crop, and cache images through configuration and services. Useful for generating thumbnails and responsive image variants without custom glue code.
Responsive images for Symfony: one Twig component for AVIF/WebP srcset, blur placeholders, Glide/Imgix, inspired by next/image
Frequently asked questions about Picasso Bundle
- Can I use silarhi/picasso-bundle in a Laravel application?
- It is a Symfony bundle, not a Laravel package: it depends on Twig templates, Symfony dependency injection, kernel.reset tags and Symfony router services. Laravel has no first-class fit, so integration means building a bridge such as Twig-in-Laravel or a Blade rendering path, Glide wiring, and an Octane-safe reset mechanism. Treat it as a separate adapter initiative rather than a drop-in Composer install.
- What does Picasso Bundle actually do for image resizing and cropping?
- It integrates the Picasso image manipulation library, which wraps Glide, into Symfony so you can define reusable image styles for resize, crop and filters in configuration. You then render derivatives from Twig helpers or services, and generated files are cached automatically. URLs are signed, and multiple source loaders are supported, including a remote URL loader.
- How do I install and configure Picasso Bundle in a Symfony app?
- Install it via Composer, register the bundle in config/bundles.php, then configure source loaders, signing and your image styles under the bundle's configuration key. Check composer.json for the PHP, Symfony, Twig and Glide constraints before scheduling the work. Once configured, styles become reusable across templates and services without custom glue code.
- Does Picasso Bundle work with Laravel Blade instead of Twig?
- No, the bundle ships Symfony and Twig templates such as image.html.twig plus Twig helpers, and there is no Blade equivalent. You would need to reproduce the URL generation and image tag output yourself in a custom rendering layer. That is a bespoke adapter, not a configuration change, and it would need ongoing maintenance as the bundle evolves.
- Is Picasso Bundle compatible with Laravel Octane or long-running workers?
- Version 2.5.0 fixes a resource leak in long-running workers by tagging the bundle's own URL loaders with Symfony's kernel.reset tag. Under Octane there is no direct kernel.reset equivalent, so you would have to reproduce that reset behaviour yourself. Any consumer-defined loader or custom HttpImageSource wiring is not tagged automatically and would keep the pre-2.5.0 leak.
- How does caching work for generated image files in Picasso Bundle?
- Derivatives are generated on the fly and written to a cache directory, so repeat requests are served from disk instead of being re-rendered. Public-cache URLs still route normally and bypass the router memoization added in 2.5.0. Plan cache directory permissions, warmup and invalidation into your deployment process.
- Can I add custom filters, loaders or image processors to Picasso Bundle?
- Yes, the bundle exposes extension points for custom filters and processors and supports several source loaders, including a remote URL loader. Anything you register yourself sits outside the bundle's automatic kernel.reset tagging, so add the tag manually if you run worker mode. Overriding image.html.twig also forfeits the picasso_escape_urls escaping speedup.
- Why do images return 404 or invalid signatures after upgrading to 2.5.0?
- Version 2.5.0 memoizes Glide URL generation once per image and query-key set, filling in width, format and signature for subsequent URLs. That optimization assumes the Symfony router is pure, so custom router decorators or URL-generation side effects can yield stale signatures. The failure is quiet, producing rejected or broken images rather than an exception.
- What are the alternatives to Picasso Bundle for image manipulation in Laravel?
- For Laravel, intervention/image, spatie/laravel-medialibrary or a direct league/glide setup with a queued derivative job are more natural fits. In Symfony, LiipImagineBundle is the closest comparable bundle. Compare the caching model, signed URL support and Twig versus Blade rendering before committing.
- Which PHP, Symfony and Twig versions does Picasso Bundle support, and is it maintained?
- The release notes do not state PHP, Symfony, Twig or Glide version ranges, so read composer.json constraints against your platform before upgrading. The 2.5.0 release is a minor bump with no declared breaking changes, dependency refreshes and a PHPStan fix, which suggests active maintenance. Check release cadence on the repository before committing long term.
Weaver
How can I help you explore Laravel packages today?