Answer Box: Laravel 13.20, released July 14, 2026, introduces a first-party image processing component via the `Illuminate\Image` facade, supporting GD and Imagick drivers with immutable transformation pipelines, lazy loading, and integration with Laravel's filesystem and validation.
What First-Party Image Processing Means
Laravel 13.20 does not replace existing tools like Intervention Image. Instead, it provides a native API that wraps `intervention/image:^4.0` underneath. The new `Image` facade lets developers chain transformations such as `orient()`, `cover()`, `toWebp()`, and `quality()` before storing results through Laravel's filesystem. The default driver is GD, with a default quality of 70. Imagick is available as an alternative. Pipelines are immutable: each transformation clones the original image, making it safe to derive multiple variants from a single source.
Installation and Configuration
To use the component, install `intervention/image:^4.0` via Composer and ensure PHP 8.3 or newer. The required PHP extension depends on the driver: `ext-gd` for GD, or `ext-imagick` plus the ImageMagick system library for Imagick. The default driver is set in `config/image.php` via `IMAGE_DRIVER` environment variable, defaulting to `gd`. You can also select a driver per-pipeline using `usingGd()` or `usingImagick()` without changing the global configuration. Always test both drivers with representative files in your deployment environment.
Supported Sources and Lazy Loading
The component accepts request uploads, local paths, URLs, raw bytes, Base64 strings, and Laravel storage paths. For uploads, validate first with `$request->validate()` then retrieve the image via `$request->image('avatar')`, which returns an `Illuminate\Image\Image` instance or `null`. Other entry points include `Image::fromPath()`, `Image::fromUrl()`, `Image::fromBytes()`, `Image::fromBase64()`, `Image::fromStorage()`, and `Storage::disk('s3')->image()`. Most sources are lazy: actual contents are read only when output or metadata is requested. Never pass untrusted URLs to `fromUrl()`; use a controlled downloader with redirect limits, timeout, and media type checks.
Transformations and Output
Laravel 13.20 exposes transformations like `cover()`, `contain()`, and `scale()` for resizing, plus `orient()` for EXIF orientation. Output methods include `toWebp()`, `toJpg()` (alias `toJpeg()`), and `quality()`. You can inspect results with `width()`, `height()`, `dimensions()`, `mimeType()`, `extension()`, `toBytes()`, `toBase64()`, and `toDataUri()`. The `optimize()` method is available for WebP output. Store paths and metadata in the database, not the Image instance or large Base64 values.
Production Avatar Workflow
A safe workflow preserves the previous asset until both the new file and database update succeed. After validation, orient and resize the uploaded image (e.g., `cover(512, 512)`), convert to WebP with quality 82, and store via `storeAs()`. Use a database transaction to update the user record; if the transaction fails, delete the stored file. This approach prevents orphaned files and ensures atomicity.