Version 8 (modified by bo <bo@…>, 12 years ago) (diff)

Image Quality

Discussion about Thumbnail Contribution for Django


The majority of applications that have images, probably use thumbnails in some capacity. There is no standard thumbnail capability in Django but there are a couple of different options out there that people have created. This page is an attempt to gather them in one place and discuss the best strategy for integrating one in Django.

The original thread discussing this issue is here - Google Discussion

Current Implementations

Design Considerations

Whichever solution is considered should have the following features:

  • Capability to define arbitrary thumbnail sizes in templates
  • Caching of the files to disk and possibly to memory

Some key questions:

  • Do we want to create a new field or just expand the existing image field?
  • What dependencies are we comfortable with?
    • Preference for limiting it to the Python Imaging Library only.
  • Image Quality using PIL
    • PIL has some serious quality problems for 'professional quality' images
    • Metadata destruction issues with PIL (wiping IPTC data, ICC profiles, EXIF data for instance)
    • No Color Profile Support (or 'hard to deal with' Profile support)
    • PIL and Large Files (20 MB Tiffs for instance) in a Web Environment = Bad
    • Lots of Thumbs on a page (i.e. 20+) .. In memory constant converting not so good for server performance ..
      • file caching is a must
    • Advanced Sharpening/Contrast enhancements for very small thumbs
    • SOLUTION:: ImageMagick .. and 'convert' ( (PyMagick is really not suitable for most things)
      • Yes! Command line, but in a 'web' environ .. separate fork to deal with Memory and _large_ files
      • use of 'convert' should at least be a setting option for those that want quality

Other Notes

  • Nesh's thumbnails can be used as a standalone templatetag without using his ImageWithThumbnails field. Just use the ordinary django ImageField
Back to Top