- What is folklore/image used for in Laravel?
- Folklore Image provides a fluent API for image manipulation in Laravel, built on Intervention Image. It is used to attach uploads to Eloquent models, resize and crop images, apply filters, and generate configured image sizes. It also supports URL-driven image generation with built-in caching for manipulated images.
- Does folklore/image support Laravel 8, 9, 10, or 11?
- No. folklore/image is a Laravel 4/5-era package that was last released in 2015 and is archived. It should not be expected to work with modern Laravel versions, PHP 8+, or current Illuminate components without significant adaptation. Use a maintained image package for modern Laravel applications.
- How do I install folklore/image in a Laravel app?
- For a legacy Laravel 4/5 application, install it with Composer as folklore/image, then register its service provider and facade and publish its configuration. Because the package is archived, dependency constraints may conflict with modern Illuminate or PHP versions. Prove installation in the exact legacy runtime before committing.
- How does folklore/image attach images to Eloquent models?
- It uses a trait-based API on Eloquent models. You attach uploads to a model and define image configurations, including sizes for cropping and resizing. The package then generates derivatives according to those configured sizes.
- Can folklore/image generate image derivatives on demand from a URL?
- Yes. folklore/image supports on-demand image generation through URLs and includes built-in caching for manipulated images. This makes derivative URLs convenient for templates or content authors. However, arbitrary dimensions, formats, or source paths can create denial-of-service and cache-poisoning risks, so restrict or sign derivative URLs.
- Does folklore/image work with cloud storage disks?
- The package advertises support for local and cloud storage disks. That fits Laravel filesystem abstraction, but the package is legacy and assumes filesystem-backed caching patterns. Validate cache invalidation and multi-server cache coherence before using it with cloud storage in production.
- Is folklore/image maintained and safe for production?
- It is archived, last released in 2015, and has zero dependents. That means there is no security patch path, outdated image-processing dependencies, and high technical risk. Treat it only as a contained legacy maintenance dependency, not as a choice for greenfield or modern production work.
- What are the best alternatives to folklore/image?
- Maintained alternatives include Intervention Image, Glide, Spatie Image, imgproxy, Thumbor, and CDN or cloud image services. Because folklore/image itself builds on Intervention Image, moving to a maintained image library or external image service is a natural migration path. Choose based on Laravel version, driver requirements, storage model, and URL security needs.
- How do I migrate from folklore/image to a maintained image library?
- First inventory every URL pattern, template helper, configuration value, and cache path used by folklore/image. Pin or vendor the package, wrap it behind an internal image-service interface, and add characterization tests around representative URLs and cache behavior. Then migrate callers to a maintained option such as Intervention Image, Glide, imgproxy, or a CDN service while preserving originals separately from rebuildable derivatives.
- Which image driver does folklore/image require, GD or Imagick?
- The available context does not specify whether folklore/image requires GD or Imagick. Because it relies on Intervention Image/Imagine, the driver depends on that underlying library and the PHP extensions available on the legacy server. Confirm the exact driver requirement against the pinned package version and runtime before deployment.