Comparison topics for image-handling methods

Drupal 7 will no longer be supported after January 5, 2025. Learn more and find resources for Drupal 7 sites

When selecting image handling modules consider these factors:

  • Ease of implementation for the site designer/admin relative to their experience and skill level with Drupal.
  • Ease of use for content authors; is the content being created by many users, or by a smaller group that can get some training? What about photo galleries?
  • Will the site design dictate the size and placement of images in the display, or do we want to enable/assist users to control this within the body of their content?
  • Do we want to control access to certain sets of images based on user roles? Do we need better control over per-user quotas than what's offered by core?
  • Will we want to re-use images once they're in the system, displaying them in multiple places on the site (e.g. blog post, news item and in a gallery)?
  • Is batch uploading of sets of files important, or is one-at-a-time uploading good enough? Can/should we offer content authors FTP access?
  • Will the modules we choose continue to be actively developed and supported through future versions of Drupal so we can upgrade without having to go back and edit existing content?

Furthermore, once you start to investigate the topic further you see that "handling images" includes many different processes, both from the users' and the system's point of view:

  • physical files
    • browsing/selecting
    • uploading to the server
    • where/how they are stored
  • relationship between the file and Drupal's database
  • linking the image to the relevant piece of content (node)
  • specifying where you want to display it and formatting details
  • how the relevant module actually displays the image to the site visitor
  • security and performance issues

The various image-handling modules have different strengths and weaknesses in each of these areas.

-------------------
Doc team helpers - I'm aware of the fact that I shouldn't be using numbering for ordering, but it's just temporary - I'll put in a weighting request to do a whole section at a time rather than bothering you frequently.

2. Display models

The various image-handling modules differ as to how/where images will be displayed on a website.

3. Security and access control issues

This is a stub page for an overview of image-handling in Drupal.

4. Performance issues

There aren't very many references to differences in performance (as in the speed of the web server displaying content to users) between the

5. Future-proofing

This is a stub page for an overview of image-handling in Drupal.

6. Examples of "killer features"

This page will showcase specific issues/features that example modules handle particularly well, or at least better than others. Perhaps it

Ease of Use

Usability is a critical factor to evaluate in comparing the different image-handling methods, and there is a lot of variability in this area

Files and the database

You will often see statements that imply an image file is contained "in" a node (Image module), "attached to" a node (Inline'/core Upload

Image re-usability

Nearly all the various image-handling modules allow you to display a given image in multiple nodes by treating an image as an asset.

Images as nodes approach

What is a node?

WYSIWYG rich text editors

This is a stub page within an overview of image-handling in Drupal.

Guide maintainers

kari.kaariainen's picture