Weave Code
Laravel Cloud Images Laravel Package
makeabledk/laravel-cloud-images
Laravel Cloud Images provides a simple API for serving optimized, responsive images from cloud storage. Generate transformed image URLs for resizing, cropping, and format conversion, with CDN-friendly delivery and caching for faster Laravel applications.
Never generate another thumbnail again - image sizing on the fly for Laravel
Frequently asked questions about Laravel Cloud Images
- How do I install makeabledk/laravel-cloud-images?
- Install it with Composer using composer require makeabledk/laravel-cloud-images, then publish the package config with the vendor:publish command. Add your cloud image provider credentials to your .env file and config. The package is a thin service provider plus facade layer, so there are no migrations, queues, or persistence changes to worry about.
- Does laravel-cloud-images support Laravel 13 and PHP 8.5?
- Yes. Version 4.4.0 was an additive compatibility release that widened the Composer constraints to allow Laravel 13 and PHP 8.5, with no API changes, deprecations, or removals. Note that the package declaring support does not mean your other dependencies, provider SDKs, or CI images are PHP 8.5 clean, so verify the full transitive tree before planning a platform upgrade around it.
- What image transformations can laravel-cloud-images generate?
- The package translates transformation parameters into provider-specific image URLs, covering resizing, cropping, format conversion, and quality settings. You pass the parameters in Blade templates or controllers and get back a URL that your cloud image provider renders on demand. That means you avoid pre-generating and storing thumbnail variants entirely.
- How do I configure my cloud image provider credentials?
- Publish the package config file and set the provider credentials and defaults through environment variables. The config layer holds your provider account details, default transformation options, and delivery settings. Because it is only a config and facade layer, setup is the standard publish-and-set-env workflow rather than any custom bootstrapping.
- Which image providers does laravel-cloud-images work with, such as Cloudinary or imgix?
- The package targets Cloudinary/imgix-style providers whose URL conventions support on-the-fly resize, crop, format, and quality transformations. It builds provider-specific URLs, so the exact parameter syntax follows the provider you configure rather than a generic local image pipeline. Check that your provider's transformation syntax matches what the package emits for your configured driver.
- Does laravel-cloud-images work with locally hosted images or Storage::url()?
- Not really. The package is built around cloud image providers that render transformations on demand, so if you self-host images or rely on Laravel's native Storage::url() path, it offers little value. It fits best when your originals already live in cloud storage behind a transformation-capable CDN.
- How do I build responsive images and srcset with laravel-cloud-images?
- Generate a transformed URL per breakpoint or density and assemble them into a srcset attribute in your Blade template. Because every URL is generated on the fly, you can add widths without pre-rendering or storing extra files. The package pairs naturally with a responsive-image or srcset helper layer, though it does not build the markup for you.
- How do I test the image URLs that laravel-cloud-images generates?
- Treat URL shape as the realistic regression surface rather than PHP errors. Assert on the generated URL strings or snapshots for your highest-traffic image templates, since a change in parameter order or provider syntax is the most likely breakage. Also smoke-test one page per provider configuration in staging before shipping.
- Is upgrading from 4.3.2 to 4.4.0 a breaking change?
- No. Version 4.4.0 is a constraint-widening release only, so the code change should be a no-op. Update on a branch with composer update makeabledk/laravel-cloud-images --with-dependencies, then diff composer.json to confirm nothing beyond constraints moved. Run your test suite plus a visual or DOM snapshot check on image templates, and remember that if you run Laravel 11 or 12 on PHP 8.3 or 8.4 this release changes nothing operationally.
- Is laravel-cloud-images actively maintained, and what if I need alternatives?
- It is a small, narrow package maintained by a single maintainer, so treat it as a low-bus-factor dependency. The upside is that its scope is limited to building URLs, which makes it easy to replace. Keep an exit ramp in mind: you can generate the same provider URLs yourself with a small helper class, and alternatives include using your provider's own SDK directly or a dedicated responsive-image package.
Weaver
How can I help you explore Laravel packages today?