A Swift image component library for Alamofire providing image response serializers, filters, caching, and async UIImageView downloads.
AlamofireImage is a Swift library that extends Alamofire to handle image downloading, caching, and processing. It provides image response serializers, UIImage extensions for manipulation, an auto-purging in-memory cache, and async UIImageView support, solving the problem of efficiently managing remote images in iOS and other Apple platform apps.
Swift developers building iOS, macOS, tvOS, watchOS, or visionOS applications that require downloading and displaying images from the network, especially those already using Alamofire for HTTP networking.
Developers choose AlamofireImage for its seamless integration with Alamofire, comprehensive feature set (serialization, filters, caching), and performance optimizations like duplicate request merging and prioritized downloading, which simplify image handling compared to manual implementations.
AlamofireImage is an image component library for Alamofire
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Extends Alamofire's response serializers to directly handle image downloads, supporting formats like PNG, JPEG, GIF, WebP, and HEIC, reducing boilerplate code for network-driven apps.
Provides UIImage extensions for inflation, scaling, rounding corners, and Core Image filters, making common edits straightforward without external libraries.
Combines URLCache for original images and an auto-purging in-memory cache for filtered variants, with configurable memory limits to optimize performance.
Features prioritized queues, duplicate request merging, and cancellation with request receipts, ideal for handling images in scroll views like UITableView.
Tightly coupled with Alamofire, making it unsuitable for projects using other networking libraries or aiming for minimal dependencies, as noted in the README's dependency list.
The auto-purging cache is in-memory only; persistent storage relies on URLCache, which may not suffice for apps needing robust offline image access or custom disk caching.
Migration guides for versions 2.0, 3.0, and 4.0 indicate a history of breaking changes, potentially complicating long-term maintenance and upgrade paths.