- 关注公众号iOS开发：iOSDevTip 获取更多源代码。
This library provides a category for UIImageView with support for remote images coming from the web.
- An UIImageView category adding web image and cache management to the Cocoa Touch framework
- An asynchronous image downloader
- An asynchronous memory + disk image caching with automatic cache expiration handling
- Animated GIF support
- WebP format support
- A background image decompression
- A guarantee that the same URL won’t be downloaded several times
- A guarantee that bogus URLs won’t be retried again and again
- A guarantee that main thread will never be blocked
- Use GCD and ARC
- Arm64 support
NOTE: The version 3.0 of SDWebImage isn’t fully backward compatible with 2.0 and requires iOS 5.1.1 minimum deployement version. If you need iOS < 5.0 support, please use the last 2.0 version.
Who Use It
Find out who uses SDWebImage and add your app to the list.
How To Use
API documentation is available at CocoaDocs - SDWebImage
Using UIImageView+WebCache category with UITableView
Just #import the UIImageView+WebCache.h header, and call the sd_setImageWithURL:placeholderImage: method from the tableView:cellForRowAtIndexPath: UITableViewDataSource method. Everything will be handled for you, from async downloads to caching management.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
With blocks, you can be notified about the image download progress and whenever the image retrival has completed with success or not:
1 2 3 4
Note: neither your success nor failure block will be call if your image request is canceled before completion.
The SDWebImageManager is the class behind the UIImageView+WebCache category. It ties the asynchronous downloader with the image cache store. You can use this class directly to benefit from web image downloading with caching in another context than a UIView (ie: with Cocoa).
Here is a simple example of how to use SDWebImageManager:
1 2 3 4 5 6 7 8 9 10 11
Using Asynchronous Image Downloader Independently
It’s also possible to use the async image downloader independently:
1 2 3 4 5 6 7 8 9 10 11 12 13
Using Asynchronous Image Caching Independently
It is also possible to use the async based image cache store independently. SDImageCache maintains a memory cache and an optional disk cache. Disk cache write operations are performed asynchronous so it doesn’t add unnecessary latency to the UI.
The SDImageCache class provides a singleton instance for convenience but you can create your own instance if you want to create separated cache namespace.
To lookup the cache, you use the
queryDiskCacheForKey:done: method. If the method returns nil, it means the cache
doesn’t currently own the image. You are thus responsible for generating and caching it. The cache
key is an application unique identifier for the image to cache. It is generally the absolute URL of
1 2 3 4 5
By default SDImageCache will lookup the disk cache if an image can’t be found in the memory cache.
You can prevent this from happening by calling the alternative method
To store an image into the cache, you use the storeImage:forKey: method:
By default, the image will be stored in memory cache as well as on disk cache (asynchronously). If you want only the memory cache, use the alternative method storeImage:forKey:toDisk: with a negative third argument.
Using cache key filter
Sometime, you may not want to use the image URL as cache key because part of the URL is dynamic (i.e.: for access control purpose). SDWebImageManager provides a way to set a cache key filter that takes the NSURL as input, and output a cache key NSString.
The following example sets a filter in the application delegate that will remove any query-string from the URL before to use it as a cache key:
1 2 3 4 5 6 7 8 9 10
Using dynamic image size with UITableViewCell
UITableView determines the size of the image by the first image set for a cell. If your remote images don’t have the same size as your placeholder image, you may experience strange anamorphic scaling issue. The following article gives a way to workaround this issue:
Handle image refresh
SDWebImage does very aggressive caching by default. It ignores all kind of caching control header returned by the HTTP server and cache the returned images with no time restriction. It implies your images URLs are static URLs pointing to images that never change. If the pointed image happen to change, some parts of the URL should change accordingly.
If you don’t control the image server you’re using, you may not be able to change the URL when its content is updated. This is the case for Facebook avatar URLs for instance. In such case, you may use the
SDWebImageRefreshCached flag. This will slightly degrade the performance but will respect the HTTP caching control headers:
1 2 3
Add a progress indicator
See this category: https://github.com/JJSaccolo/UIActivityIndicator-for-SDWebImage
There are three ways to use SDWebImage in your project: - using Cocoapods - copying all the files into your project - importing the project as a static library
Installation with CocoaPods
Installation with Carthage (iOS 8+)
Carthage is a lightweight dependency manager for Swift and Objective-C. It leverages CocoaTouch modules and ins less invasive than CocoaPods.
To install with carthage, follow the instruction on Carthage
Installation by cloning the repository
In order to gain access to all the files from the repository, you should clone it.
Add the SDWebImage project to your project
- Download and unzip the last version of the framework from the download page
- Right-click on the project navigator and select “Add Files to “Your Project”:
- In the dialog, select SDWebImage.framework:
- Check the “Copy items into destination group’s folder (if needed)” checkbox
- In you application project app’s target settings, find the “Build Phases” section and open the “Link Binary With Libraries” block:
- Click the “+” button again and select the “ImageIO.framework”, this is needed by the progressive download feature:
Add Linker Flag
Open the “Build Settings” tab, in the “Linking” section, locate the “Other Linker Flags” setting and add the “-ObjC” flag:
Alternatively, if this causes compilation problems with frameworks that extend optional libraries, such as Parse, RestKit or opencv2, instead of the -ObjC flag use:
If you’re using Cocoa Pods and have any frameworks that extend optional libraries, such as Parsen RestKit or opencv2, instead of the -ObjC flag use:
Import headers in your source files
In the source files where you need to use the library, import the header file:
At this point your workspace should build without error. If you are having problem, post to the Issue and the community can help you solve it.
- LRU memory cache cleanup instead of reset on memory warning
All source code is licensed under the MIT License.