buglinjo/laravel-webp
buglinjo/laravel-webp is a Laravel package for converting JPEG and PNG images to WebP, helping you serve smaller, faster-loading images. It offers a simple facade and API for saving, quality tuning, and cleanup, making WebP optimization easy in any Laravel app.
WebP::make($file)->save($path)). The decision it informs is narrow: do we hand-roll a converter service, or take a small dependency that gives us the encode-and-save primitive in ~10 lines? It buys the wrapper, not the pipeline.ImagePipeline service must own (queues, <picture>/srcset markup, cache invalidation, fallback serving for non-WebP clients).Adopt when:
Look elsewhere when:
Risk notes to record: the release is compatibility-only, so there are no new features or breaking API changes in v3.2.0 — the practical upgrade risk is low, but a version bump should still be exercised against our own upload paths. Maintain a thin internal adapter around the facade so a future swap to a fuller media solution is a one-file change.
For executives: This is a small, low-cost utility that converts uploaded images to WebP, a format that typically cuts image payloads substantially and improves page load and Core Web Vitals. The new v3.2.0 release is a maintenance update that keeps it compatible with Laravel 13, so it will not block our framework upgrade. Recommendation: keep it for simple conversion needs, and treat it as one component — not a strategy — within a broader image-delivery plan.
For engineering: v3.2.0 is a compatibility-only release adding Laravel 13.x support; no API changes, no deprecations, no migration work expected beyond your normal upgrade pass. The package remains a thin facade over GD/Imagick WebP encoding — we still own queuing, storage layout, cache headers, and non-WebP fallbacks. Wrap it behind our own ImageConverter interface, confirm WebP support is compiled into the PHP image driver in every environment (including CI and containers), and add a smoke test on the convert-and-save path so a future major bump surfaces immediately.
How can I help you explore Laravel packages today?