Weave Code
Imagine Laravel Package
orchestra/imagine
Orchestra Imagine is a Laravel package that integrates the Imagine image manipulation library, providing a fluent, configuration-driven API to resize, crop, and transform images within Laravel applications.
Orchestra/Imagine is a Laravel extension that integrates the Imagine image manipulation library into your application, offering a fluent, framework-friendly API for resizing, cropping, and transforming images. It wraps Imagine's ImageInterface in Laravel-native conventions, making image processing feel like a natural part of your application stack.
- Seamless Imagine integration via a Laravel service provider and facade
- Fluent resizing, cropping, rotating, and thumbnail generation
- Supports GD, Imagick, and Gmagick drivers
- Publishes a configuration file for driver and quality settings
- Designed for use within the Orchestra Platform ecosystem
Frequently asked questions about Imagine
- What is orchestra/imagine and what does it actually do?
- Orchestra/Imagine is a Laravel extension that wraps the Imagine image manipulation library behind a service provider and facade, giving you a fluent API for resizing, cropping, rotating, and generating thumbnails. It publishes a configuration file for driver and quality settings and supports GD, Imagick, and Gmagick backends. Architecturally it is a thin shim: a service provider, a facade, a config file with essentially one meaningful key (driver), and a pass-through to imagine/imagine. It adds no capability you could not get by binding Imagine\Gd\Imagine or Imagine\Imagick\Imagine directly behind your own interface.
- How do I install orchestra/imagine in a Laravel application?
- Installation is composer require orchestra/imagine followed by php artisan vendor:publish to get the config file. There is no installer and no Artisan commands, so setup is genuinely cheap to try. The catch is that the package does not install GD, Imagick, or Gmagick for you, so the install succeeding does not mean the package will resolve at runtime. Verify that the configured driver extension exists on your machine before assuming it works.
- Does orchestra/imagine support Laravel 9, 10, or 11?
- This is a Laravel 8-era release line, and its release history stops at an update for Laravel Framework v8. On newer frameworks the expected outcome is that Composer will not resolve the package rather than a surprise failure. Widening your Composer constraints to force it onto a current Laravel version buys you an install and an unbudgeted debugging session. Treat compatibility as unproven until someone validates resolution against your actual PHP and Laravel versions.
- Which image drivers does orchestra/imagine support and how do I choose one?
- The package supports GD, Imagick, and Gmagick, selected through the driver key in the published config file. The wrapper does not install any of these extensions, so pointing the driver at a missing extension produces a container-resolution failure rather than a clear extension-missing error. Be aware that GD and Imagick produce visibly different output at identical settings, so a dev/prod driver mismatch can ship a QA pass that does not reflect production. Set the driver per environment and mirror it locally.
- How do I publish and configure the orchestra/imagine config file?
- Run php artisan vendor:publish and select the Orchestra Imagine service provider tag to copy the config into your config directory. The meaningful settings are the driver and quality values, which control which Imagine backend is used and the output compression level. Because there are so few options, the config file is arguably the only durable artifact the wrapper gives you. Keep environment-specific driver values explicit rather than relying on defaults.
- Is orchestra/imagine a good alternative to Intervention Image?
- For most new projects, no. Intervention Image is actively maintained with a current v3 release and a broader API, while orchestra/imagine is a thin pass-through to imagine/imagine with zero stars, zero dependents, and a release history that stops at Laravel 8. The wrapper only fits naturally inside an existing Orchestra Platform application or a legacy Laravel 8 tree where it already arrived transitively. For greenfield work you are better off binding GD or Imagick directly or adopting Intervention.
- Can I use orchestra/imagine outside the Orchestra Platform ecosystem?
- Technically yes, it is a normal Laravel package with a service provider and facade, so it works in any application that resolves it. Practically, the fit is low outside Orchestra Platform because the wrapper contributes almost nothing beyond a config file and a facade alias. If you only need Imagine, bind Imagine\Gd\Imagine or Imagine\Imagick\Imagine in a service provider behind your own interface and skip the dependency. That gives you the same functionality with one less unmaintained package in your tree.
- Is orchestra/imagine still maintained and safe to use in production?
- It shows no signs of active maintenance: zero stars, zero dependents, and a release history that ends with Laravel 8 support. Zero dependents also means no filed issues, so incompatibilities surface silently instead of being reported upstream. The real risk surface is not the wrapper but imagine/imagine, which means you own CVE tracking against a transitive dependency yourself. If the package is already in your tree, pin the Imagine version explicitly, vendor or fork the wrapper for reproducibility, and contain usage behind your own interface.
- How do I protect against image decoder vulnerabilities when using Imagine?
- Image decoders are a known attack vector through decompression bombs, malformed headers, and memory exhaustion during decode. Enforce input-dimension and memory ceilings before decode on your worker processes rather than relying on the library to fail gracefully. Because orchestra/imagine offers no upstream fix path, you have to track advisories against imagine/imagine directly. Running image transformations in a queued worker with resource limits is safer than processing uploads synchronously inside the request.
- How do I migrate away from orchestra/imagine without rewriting my code?
- Write an application-owned ImageProcessor interface and route every call site through it, which is roughly an hour of work and makes the eventual swap a constructor change instead of a rewrite. If the package is inherited and working, contain it: wrap call sites, pin the Imagine version in your own composer.json, and vendor or fork the wrapper so your tree stays reproducible. If you are starting fresh or planning a framework upgrade, avoid the dependency entirely and bind GD or Imagick behind the same interface. Either direction converts a future move to Intervention Image v3, a CDN transform tier, or a queued worker into a small, predictable change.
Weaver
How can I help you explore Laravel packages today?