--- title: "Laravel 13.20 adds first-party image processing and other new features" url: https://daily.dev/posts/laravel-13-20-adds-first-party-image-processing-and-other-new-features-hgi55fw6f source_url: https://daily.dev/posts/laravel-13-20-adds-first-party-image-processing-and-other-new-features-hgi55fw6f type: collection source: "Collections" published: 2026-07-15T13:59:39.115Z updated: 2026-07-16T07:22:58.604Z tags: ["php", "laravel", "image-processing"] reading_time: 3 upvotes: 23 comments: 3 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Laravel 13.20 adds first-party image processing and other new features **[Collections](https://daily.dev/sources/collections)** · 3 min read · 23 upvotes · 3 comments ## Summary Laravel 13.20 introduces a first-party Image facade that wraps Intervention Image v4 with a fluent, Laravel-native API for upload-process-store workflows. The facade handles driver configuration, filename generation, and storage, supporting GD and Imagick drivers with an immutable API. Other additions include a #[WithoutMiddleware] attribute for controller methods, a dedicated Redis session prefix to avoid key collisions, quiet bulk increment/decrement methods for Eloquent models, enum support for the WithoutOverlapping queue middleware, and minor fixes like collision-free migration timestamps. ## Content ## What's new in Laravel 13.20 Laravel 13.20 shipped with a handful of meaningful additions. Here's what's worth knowing. --- ## First-party image processing The headline feature is a new `Image` facade backed by [Intervention Image v4](https://image.intervention.io/). You'll still need to pull in `intervention/image` via Composer, but Laravel now wraps it with a fluent, driver-based API that handles the boilerplate you'd otherwise write yourself. The API is immutable and supports GD and Imagick drivers. You can read from uploads, URLs, file paths, or raw bytes, then resize, crop, convert formats (WebP, JPEG), optimize, and store - all in one chain. Compared to using Intervention Image directly, the main win is less setup: no manual driver configuration, no separate filename generation, no stitching together upload and processing steps. Here's roughly what that looks like: ```php // Raw Intervention Image $manager = new ImageManager(new GdDriver()); $image = $manager->read($request->file('photo')); $image->scale(width: 800); $encoded = $image->toWebp(quality: 80); Storage::put('photos/' . $filename, $encoded); // New Laravel Image facade Image::read($request->file('photo')) ->scale(width: 800) ->toWebp(quality: 80) ->save(storage_path('app/photos/' . $filename)); ``` This feature originated from a pull request in March and went through several revisions - notably, planned Cloudflare driver support was removed before it shipped. **When Spatie Media Library is still the better choice:** if you need media collections, galleries, multiple format conversions per upload, or database-tracked media, Spatie remains the more complete solution. The new `Image` facade is a convenience layer, not a full media management system. --- ## Collision-free migration timestamps This one's subtle but worth understanding, especially if you use AI agents to scaffold code. When multiple migrations are generated within the same second, they get identical timestamps. Laravel falls back to alphabetical ordering in that case, which can cause foreign key errors - a migration for a dependent table runs before the parent table exists. The tricky part: SQLite silently ignores the problem, while MySQL throws an error. So if an AI agent is generating migrations against a SQLite database (common in development), it may never catch the issue. The fix, contributed by Push Back and Nick and merged by Taylor Otwell, introduces a collision-free path function that increments the timestamp by one second at a time until it finds a unique prefix. Multiple migrations generated simultaneously now get sequential timestamps and run in the correct order. --- ## Other additions **`#[WithoutMiddleware]` controller attribute** - Fine-grained middleware exclusion directly on controller methods, without touching route definitions. **Dedicated Redis session prefix** - Session keys are now separated from cache keys in Redis, avoiding collisions when both use the same Redis instance. **`incrementEachQuietly` / `decrementEachQuietly`** - Bulk increment and decrement on Eloquent models without firing model events. Useful when you want to update counters without triggering observers. **Enum support for `WithoutOverlapping` queue keys** - You can now pass an enum as the key for the `WithoutOverlapping` job middleware. **`#[SensitiveParameter]` on secret-carrying parameters** - Secrets are now marked sensitive in stack traces, reducing accidental exposure in error logs. --- The migration timestamp fix is probably the most important change for teams using code generation tools. The image facade is genuinely useful for straightforward upload-and-resize workflows, though it's worth being clear-eyed that it's a wrapper, not a replacement for heavier media management packages. ## Community discussion Top comments from developers on daily.dev. **@chadfremo** · 2 upvotes > Laravel is the best MVC framework. **@j3ss3** · 1 upvotes > libvips support is amazing ## Similar posts on daily.dev - [A Practical Guide to Laravel's First-Party Image Processing](https://daily.dev/posts/a-practical-guide-to-laravel-s-first-party-image-processing-vd2qss3ac) · Laravel News · 7 upvotes · 0 comments --- Tags: [#php](https://daily.dev/tags/php), [#laravel](https://daily.dev/tags/laravel), [#image-processing](https://daily.dev/tags/image-processing) [View this post on daily.dev](https://daily.dev/posts/laravel-13-20-adds-first-party-image-processing-and-other-new-features-hgi55fw6f)