Original picture: https://unsplash.com/photos/-6mZyblCys4 Every time I started a new project or while I was working on existing ones, I used to wonder which image library should I use. Android I have to admit that I have looked for some comparison among this libraries to understand how they perform but I haven’t found any benchmark that really satisfies me. That’s why I decided to make my own comparison between , and . Picasso Universal Image Loader Glide Note: Maybe you wonder why Fresco (the option provided by Facebook) is not among my options. This library uses its own custom view to display images (called Drawee) so, you should use it instead of ImageView. As I was running this test in an existing project and entirely refactoring it was not one of the options (because of the Drawee thing), I couldn’t choose it as the winner. Specially, if I still could get very good results from the other three. Sorry Fresco fans and Facebook! What did I compare? Memory and CPU consumption, amount of methods (because of the 65k methods limit), , size and ease to implement. networking How did I test? I had a list of 200 elements that included an image. Images (180 x 135 px) were no repeated and they were loaded from the server on the first run. I scrolled up and down three times the list to measure the use of networking, CPU and memory. The idea was to use each library how it was “out-of-the-box”. For Universal Image Loader I had to set manually to cache on memory and disk and for the memory benchmark I used Picasso with its default memory cache limit and with a custom limit of 25 mb. This is a part of the listing that was scrolled during the test. Show me the results! Size in kilobytes of each JAR. The winner is Picasso. Measured with . The winner is Picasso. Dexcount Gradle Plugin by KeepSafe Measured from Android Studio. The winner is Universal Image Loader. What about ? There were in these two aspects. network and CPU no noticeable difference And… what about ? Well, all of them are easy to use. needs (let’s say ~4 more lines) before using it as well as the other competitors. Regarding , although it I found that in situations where the others had no issues of that kind. Regarding , I had nothing to add, it ease to implement Universal Image Loader a few more lines Picasso is easy to use, it easily generates memory leaks Glide works greatly just out of the box. So, what did I learn? I can say that all the libs mentioned above are great and really makes easy the usage of images on Android. Thanks for that guys. I would recommend the following: : I recommend (or switch to it) because of its customization, low memory consumption and good balance between methods and size. Existing Projects Universal Image Loader : I would choose . I really like its simple implementation and where the Picasso implementation on my code has memory leaks, Glide doesn’t (neither Universal Image Loader). Small projects Glide I think it is OK if you are sure that you have no memory leaks and you control how much cache memory is using. Currently using Picasso? Well, as far as I know, it is a really good library. I would try it out if I have to start a project from scratch. and… Fresco!? Recommend this story (by clicking the ❤ button) so other people can see it!You can also react on Twitter Did you like what you read? @santihollmann

Picasso, Universal Image Loader or Glide? That’s the question.

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

10 Things to check on Android code reviews

Java bits: 0xFF and 0xFFL

10 Things You Didn't Know You Could Do With Google Keep

10 Things to check on Android code reviews

10 Mistakes In Mobile App Development That Make You Look Dumb

10 Things to check on Android code reviews

Java bits: 0xFF and 0xFFL

10 Things You Didn't Know You Could Do With Google Keep

10 Things to check on Android code reviews

10 Mistakes In Mobile App Development That Make You Look Dumb

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps