When should a section have no image at all?

Published Read 3 min read

On this page

A section is better with no image when the words already carry the meaning fully, when any image would only decorate rather than inform, or when typography and space can do the work more cleanly than a picture could. Omitting an image is a real design choice, not a gap waiting to be filled. The instinct that every section needs a visual to break up the text leads to images that are there only to occupy space, and those images cost more than the blankness they replaced. Sometimes type and space say it best.

The reasoning starts with what an image is for. An image earns its place by adding meaning the copy cannot supply, showing something, setting a tone, or giving evidence. When the copy already does all of that, an added image has no job. It does not clarify, because the point was already clear. It does not add emotion the words lacked, because the words had it. So it falls back on decoration, and decorative-only images dilute rather than strengthen, because they ask for attention without repaying it. They also push the real content down, slow the page, and signal that the section was treated as a template to fill rather than a message to deliver. A section that is purely words, set well, can be cleaner, faster, and more confident than the same section with a stock photo wedged in beside it.

A concrete case shows when none is right. Think of a pricing comparison section, three plans laid out in columns with features, prices, and a clear recommended tier. This section lives or dies on legibility: the reader needs to scan, compare, and decide. An image here helps nothing. A photo of a smiling team would only crowd the columns and steal the eye from the numbers that matter. The strongest version of this section is pure typography and space, generous alignment, clear hierarchy, a subtle highlight on the recommended plan, and no picture at all. The absence of an image is what makes it work. Add one and you would be fighting your own layout.

A second case is a focused statement section, the kind that carries a single strong line of copy meant to land hard, a mission, a promise, a turning point on the page. Here an image is not just unnecessary, it actively weakens the moment. The power of such a section comes from the room around the words, the silence that makes the sentence feel deliberate. Drop a photo beside it and the line stops being a statement and becomes a caption, sharing attention it needed to keep for itself. Big type, deep space, and nothing else is often the most confident thing a page can do, and reaching for an image there is a failure of nerve, not a gain in polish.

The qualifier is that this is not an argument against imagery, only against reflexive imagery. Plenty of sections genuinely need a visual, a product shot that shows what the thing looks like, a diagram that explains a flow, a photo that supplies emotional context the copy cannot. The point is to omit images where they would not earn their place, not to strip them from sections that need them. There is also a rhythm consideration: a long page of nothing but text blocks can become heavy, and an image can give the eye a rest. That is a real reason, but it is about pacing the whole page, not about owing every individual section a picture.

Practically, decide per section by asking what an image would add that the words do not. If the honest answer is nothing, leave it out and let strong typography, clear hierarchy, and deliberate space carry the section. Treat a clean, image-free section as a finished and confident choice rather than an unfinished one, and reach for an image only when it does work the copy cannot.

Related posts:

  1. How do you decide what earns a spot in the primary nav vs the footer? The primary nav holds the few destinations most users need to reach their goals, and the footer holds the secondary, legal, and reference links people seek out deliberately, so the......
  2. How much should the interface explain itself vs trust the user to explore? An interface should make its core actions self-evident and explain only what is genuinely non-obvious, trusting users to explore the patterns they already know. The balance turns on a single......
  3. How do you surface a submit error without making the user hunt for it? You surface a submit error so it cannot be missed by doing three things together: summarize the problems at the top of the form, move keyboard focus to that summary......
  4. How many CTAs should one page have before they start competing? The honest number is one primary action, not one button, and CTAs start competing the moment the page offers two different actions of roughly equal weight that pull the visitor's......
  5. When is a full-width section right vs a contained, centered one? Choose full width when the content is meant to envelop the viewer and a contained, centered width when the content is meant to be read. That single distinction settles most......
  6. How do you keep a hero readable from phone to ultrawide? A hero stays readable across every width when you decouple the text's legibility from the background image's behavior. The mechanism is that an image and the type laid over it......
  7. Should you build a color system from one hue or several? Start from one hue and expand only when the product proves it needs more. A single-hue system, built from one color stretched across tints, shades, and a neutral ramp, reads......
  8. How much whitespace is too much before a layout feels empty instead of intentional? Whitespace becomes too much the moment it stops doing a job. The tipping point is not a pixel value, a margin token, or a percentage of the viewport. It is......
  9. When does a second typeface add hierarchy vs just add noise? A second typeface earns its place only when it draws a clear functional line, the most common one being headings against body, and it becomes noise the moment it decorates......
  10. Should dark mode be a true inversion, or designed separately? Dark mode should be designed separately, as its own deliberate theme, not produced by inverting the light one. A literal flip is tempting because it looks like a single switch,......
  11. Why can shipping one more feature make a product feel worse to use? Shipping one more feature can make a product feel worse because every feature adds interface, choices, and surface area, and that accumulation crowds the core even when the new feature......
  12. At what point does a strong hero flatten everything below it? A hero flattens the page the moment the section directly below it stops earning attention on its own. That is the line, and it is a behavioral test, not a......
  13. How do you design for the user who lands mid-flow from a deep link? You design for the deep-linked user by treating every screen as a possible front door: orient them on arrival, supply or recover the context the earlier steps would have given,......

Leave a comment

Your email address will not be published. Required fields are marked *