Workflow & Automation

Featured Images at Scale: Building a Template That Survives 200 Posts

The least loved field in publishing is the only part most people ever see.

Choosing a good picture per post works beautifully for the first twenty. What breaks afterwards is consistency, and that is a systems problem.

An automation panel generating featured images for a batch of posts

The featured image is the least loved field in publishing. It sits at the bottom of the sidebar, it is filled in last, and on most sites it is either missing, a stock photograph nobody looked at, or the same picture as the last four posts.

It is also the only part of an article most people ever see. It appears in the archive, in related posts, in search results on some layouts, and as the preview when the link is shared anywhere at all. Getting it consistently right across a couple of hundred posts is a systems problem, not a design problem.

Why the ad hoc approach fails

Choosing a good image per post works beautifully for the first twenty and collapses afterwards, for reasons that have nothing to do with effort.

The archive page shows twelve of them at once, and twelve unrelated photographs at twelve different crops, brightness levels and color temperatures looks like a mess even when every individual picture is good. Consistency across a grid is a different requirement from quality in isolation, and it is the requirement that actually governs how the site feels.

Then there is the practical drift: the aspect ratio changes when the theme is updated, someone uses a portrait image, someone else uses one with text baked in at the wrong size, and after a year the archive is a patchwork.

Decide the anatomy once

Before automating anything, settle what a featured image on this site is. Not a mood board, a specification:

  • One aspect ratio. 16:9 or 1.91:1 are the sensible defaults because they match how links preview when shared. Pick one and never deviate.
  • One size. Around 1600 by 900 covers dense screens without being wasteful.
  • A fixed structure. Where the title sits, if it appears at all. Where the category marker goes. Whether there is a logo.
  • A defined visual field. A photograph, an illustration, a screenshot, a color field, but the same kind of thing every time.
  • A rule for legibility. If text sits over an image, there is a scrim or a gradient under it, always, not only when the photograph happens to be busy.

Write it down. The specification is what makes automation possible, and it is also what stops the drift even if you never automate anything.

To put the title on it or not

Both work; they fail in different ways.

Title on the image gives a card that communicates without any surrounding text, which is exactly what happens when a link is shared into a chat. It costs you an update problem: change the headline later and the image is now wrong, silently, forever.

Pure visual ages better, adapts to any layout, and never contradicts the headline. It communicates less on its own.

The deciding question is where your traffic comes from. If links are shared a lot, put the title on. If most people arrive through the site itself, where the headline already sits next to the image, keep it visual and save yourself the maintenance.

If you do put the title on, the image has to be regenerated whenever the title changes, which is an argument for generating it from a template rather than making it by hand.

An automation panel that generates featured images for posts in a batch
Generating on publish is the part that makes it stick. A step that has to be remembered is a step that will be skipped.

The template is the whole trick

A featured image template is a design with holes in it: a slot for the title, a slot for a category or kicker, a slot for a picture, and a fixed background treatment. Producing an image becomes filling the holes rather than making a design.

Three things separate a template that survives from one that breaks in week two.

Text has to fit itself

Headlines are not the same length. A template with a fixed font size will look right for the title you designed it around and wrong for everything else, either overflowing or floating in space.

The rule is: measure, and shrink the type until the block fits its box, with a sensible floor. This is unglamorous and it is the single difference between a template that can be pointed at a hundred posts and one that needs supervision.

Pictures have to be cropped, not squashed

Source images arrive in every proportion there is. Dropping one into a fixed slot by stretching produces the distinctive squashed look that instantly reads as automated. Crop to fill the slot from the center, or from a detected subject, and keep the proportions.

Categories can carry the variety

If every card is identical the archive gets monotonous. Let the category drive one variable: an accent color, a background texture, a corner marker. The set stays coherent and the grid gains rhythm without anyone choosing anything per post.

Automate at the right moment

The moment to generate is on publish, from the post’s own data, with a manual override available.

That combination matters. On publish means it always happens. From the post’s own data means the title and category on the image are correct by construction. The override means the one post that deserves a bespoke image can have one, without the automation fighting you.

Two settings are worth insisting on: skip posts that already have a featured image, so nothing you made by hand is ever overwritten, and refresh when the title changes, so images with text on them do not go stale.

A generator dialog producing a full layout as editable layers
A generated result you can open and adjust is a starting point. A flattened one is a wall.

The metadata that travels with it

While you are automating, do the adjacent fields in the same pass, because they are all part of the same job of “how this post appears when it is not on your site”.

  • Alt text for the featured image. Frequently forgotten, and it is the image most likely to be encountered on its own.
  • The social preview image, which some setups treat as separate from the featured image. If your SEO plugin has its own field, fill it, or you will discover the fallback is your logo.
  • The description that appears under the link in a preview card. If it is not set, platforms invent one from the first paragraph, with mixed results.

None of these are visible on your own site, which is exactly why they rot.

Retrofitting an archive

If you already have two hundred posts with inconsistent images, do not start at the beginning. Sort by traffic, do the top twenty by hand to establish what the template should be, then batch the remainder.

Keep the manual twenty. They are your reference for whether the automated ones are good enough, and if they are not, the template is wrong rather than the idea.

Table of Contents

Learn it by building something

Every week one thing you can make the same afternoon, from dynamic templates to 3D type. Written down step by step.

One mail a week, and then it ends.
Unsubscribe in one click.

Free

Chaos Art

Autonomous painters make one-of-a-kind abstract art in 3D space - gestures, art movements, painterly media, and embeds that paint a new original for every visitor.

Download the free WunderPaint Plugin for WordPress

The Image Editor & Design Studio

Everything described here can be done in the browser, on your own site. The live demo runs the full editor with nothing to install.

Design Tools

Brush & Paint Styles

Paint with six styles that mix pigment instead of blending it, pick from thirty-seven tips shown as real strokes, draw a tip of your own out of shapes, and let the color travel along the stroke.

Workflow & Automation

Dynamic Templates: Build the Design Once, Let Your Posts Fill It In

You build the layout once, tell a few layers where to get their content, and from then on every post, product or page renders its own version.

Print & Craft

Making Things That Fold: Dielines, Duplex and Why Previews Matter

A gift box, a paper crane, a bunting banner. They look simple, and they fail in ways flat design never does, because there is a second geometry underneath.

WordPress Images

Why Should a Design Become a File at All?

Every static graphic on a page is a snapshot of what was true when somebody exported it. There is a whole category of quiet wrongness that follows from that.