How Should a CMS Handle Images? From Upload Optimization to Descriptions and URL Management

A CMS’s image handling should go beyond simply allowing uploads and insertion into articles. For the content publishing and SEO scenarios covered by the supplied material, requirements can be organized into four categories: image sizing and format processing during upload, page loading and preview settings, image descriptions and metadata, and stable image URLs. These are recommendations to check when selecting or developing a system, not official rules that every CMS must follow. If a website relies heavily on image search, URL management deserves particular attention.

Handle Sizing, Cropping, and Formats During Upload

In a November 2026 article, Search Engine Journal recommends that a CMS have built-in capabilities for resizing, cropping, compression, and conversion to WebP or AVIF, incorporating these tasks into the upload process rather than simply accepting original files.

• Resizing and cropping: Check that editors can adjust image dimensions and framing within the system.
• Compression and format conversion: Check which processing operations the upload workflow supports, rather than looking only at which file extensions it accepts.
• Width and height attributes: Include width and height when outputting images to help prevent layout shifts.

The material does not provide universally applicable compression ratios or size thresholds, so no single set of values should be presented as a standard for all websites.

Allow Separate Settings for Loading Behavior and Sharing Previews

The same article advocates lazy-loading images, except for the first image on the page. This is an implementation recommendation from that article. It should not be simplified to “lazy-load all images,” nor does it establish that the approach suits every page layout.

Two additional items to check are whether a custom OG image can be set for each page and whether max-image-preview: large can be configured. These should be listed as separate requirements. A CMS’s ability to insert images into article content does not mean it also supports these preview settings.

Preserve Image Descriptions and Make Them Visible to Readers

A 2011 discussion recommends that a CMS support and preserve not only EXIF but also metadata used to describe images, such as IPTC-IIM and XMP. Another contributor advocates extracting keywords and descriptions from images and displaying them as visible text on the page, while also mentioning the uses of alt or title.

For editorial workflows, this suggests distinguishing between “preserving descriptions within the file” and “displaying descriptions on the page.” For example, an image containing descriptive metadata does not mean the article displays a caption. However, the contributor’s view at the time that visible text seemed to carry more weight in search can only be retained as a historical assessment, not treated as a current ranking rule.

Check Whether Image Processing Creates Confusing URLs

The 2026 article recommends maintaining a single clean, stable URL for each image, taking CDN use and resizing into account. The author describes a system in which adding an identifier to an image and then resizing or cropping it generated multiple URLs, while the original URL without the identifier remained accessible.

This experience reminds those selecting a CMS to check not only whether cropping works but also the resulting URLs. The author believes that, for websites where image search matters, this situation could create substantial duplication issues. The material does not establish that all image variants incur search penalties, so this risk should not be presented as an inevitable outcome.