Making WordPress image settings work for editors
An editor uploads a sensible image, picks a size and still ends up with a blurry card, or a page hauling a far bigger file than expected. The media settings, the theme and the actual layout are making decisions the editor can’t see. Another reminder to “optimise images” will not explain the problem.
I’d make the publishing workflow understandable and check what the public page actually delivers. Editors need practical guidance for choosing and replacing images, and maintainers need to make sure the theme’s output supports that guidance.
Start with the places images appear
List the main uses: featured images, article content, cards, banners and any special layout. Identify the displayed shape and context for each. One upload may be reused in several places with different requirements.
Inspect real pages on narrow and wide screens. The editor’s preview may not reveal how a crop or responsive choice behaves in the final layout. Keep representative examples for the review.
I wouldn’t choose a universal pixel dimension before understanding these uses. A small card, a detailed diagram and a wide banner do different jobs. The guidance should help people supply suitable material for each task.
Explain the difference between source and display
The uploaded original and the size used in a layout are related but not identical. WordPress and the theme can create or select derived images, while layout rules determine how the chosen file is displayed.
WordPress has responsive image support that uses image markup to help browsers choose suitable sources. Check the actual theme output rather than assuming an upload’s full size is always what a visitor downloads.
Give editors a plain explanation of what they control and what the system handles. They should not have to understand every markup attribute to make a sensible publishing choice.
Review available sizes and cropping
Inspect the sizes registered by the current theme and relevant plugins, along with how they are used. A setting labelled medium may not correspond to the place an editor imagines. Name the workflow in terms of the layout where possible.
Check whether cropping removes important subject matter, text or context. A central crop can work for a portrait and fail for a diagram. Use appropriate source composition or a supported layout choice rather than expecting every image to fit every slot.
I would test a few deliberately awkward examples: a tall image, a wide image and a subject near an edge. Their behaviour can expose problems hidden by the site’s favourite sample photograph.
Give editors a short preparation route
Explain how to choose an appropriate source, avoid unnecessary dimensions and preserve required detail. Compression should maintain the information the image is meant to convey, especially for diagrams or product details.
Use descriptive file names and appropriate alternative text where relevant. Alternative text should reflect the image’s role and content, not become a list of target keywords. Decorative treatment needs its own appropriate handling.
Keep captions for information the reader should see. Don’t put an essential product qualification only in alt text, where not every visitor will see it.
Make replacement behaviour explicit
Show whether the editor should replace an existing asset, upload a new file or update a particular content field in the site’s approved workflow. Those approaches can affect reuse, URLs and other pages differently.
Before removing an old image, check where it is used. A file that looks obsolete in one post may still support another page or shared component. Don’t treat the media library as a pile of disposable attachments.
When a source image changes, verify derived versions and delivery caches through the maintainer’s process where necessary. An admin thumbnail is not enough to prove every public use has updated.
Test the ordinary publishing task
Ask an editor to add a suitable image, choose the intended setting and preview the result. Watch where labels or instructions are unclear. The workflow should make a good choice easier, not depend on remembering an informal warning.
Inspect the public output for clarity, crop and reasonable delivery. If the system still chooses an inappropriate source, route the issue to the theme or technical owner. I wouldn’t keep asking editors to compensate for a broken default.
Review important above-the-fold images separately where loading behaviour affects the experience. Don’t apply one lazy-loading rule to every use without considering the page’s actual content and performance.
Keep the guidance aligned with the theme
Update image instructions when layouts or generated sizes change. A useful old checklist can become misleading after a theme release even if the media upload screen looks familiar.
Keep a small set of visual examples showing suitable source composition and the expected public result. Editors can often recognise a correct crop more quickly from an example than from a long technical note.
Assign someone to maintain the settings and someone to maintain the editorial guidance. The two responsibilities should communicate when a change affects the other’s work.
Use examples instead of vague file-size warnings
Show editors a suitable source and its public result in the actual layout. Explain which detail must remain legible and what a poor crop looks like. This is more actionable than asking everyone to make images smaller without reference to their use.
If a technical limit is required, document the reason and the route for a legitimate exception. A detailed diagram may need different treatment from a decorative photograph.
Keep the guidance focused on the task an editor can perform. The maintainer should handle system-level delivery issues rather than expect contributors to compensate for every responsive-image problem manually.
Related reading
Choose one image used in a card and a full page. Can an editor predict how it will crop, which detail must survive and what they should check after publishing?