When a photo beats an illustration (and when it does not)

This question usually arrives disguised as a taste debate, which is why it rarely resolves. Someone prefers the illustrated look, someone else finds it juvenile, and the decision gets made by whoever is more senior. But there is an actual functional difference underneath, and once you name it the choice mostly makes itself.

The functional difference

An illustration is a drawing of an idea. It can show things that have no appearance - a data pipeline, a permission model, three abstract benefits arranged around a circle. It can omit everything irrelevant, which is its superpower: no distracting background, no awkward hand position, nothing but the point.

A photograph is a record of a moment that occurred. Its power runs the opposite direction: it carries the irrelevant detail, and that surplus is what makes it feel true. The scuffed table leg and the half-drunk coffee are not the subject, but they are the evidence.

So the question is never which is prettier. It is whether the job at hand is explaining or convincing.

A decision table

The case for illustration that people forget

Illustration has one advantage that is hard to beat: it is consistent by construction. A single illustrator working in a defined style will produce forty assets that unmistakably belong together, because the style lives in the hand that made them.

Photography does not get that for free. Consistency has to be imposed - one lighting setup, one palette, one point of view held across every frame - and most teams never impose it, which is why so many photo-led sites look worse than illustration-led ones despite starting with better raw material. If you cannot commit to a consistent photographic look, illustration is genuinely the safer choice. That is the honest version of this advice.

The way out, if you want photography, is to decide the look before you gather images and reject anything that misses it. We wrote up the method in full: how to get a consistent style out of AI image tools, and the planning half in how to build a shot list like an editor.

The case against illustration that people forget

Illustration styles date in cohorts. When a look saturates - and every few years one does - everything wearing it gets timestamped at once, and the association sticks. Photography ages too, through lighting fashions and color grades, but it usually ages into "a period" rather than "a trend everyone did."

The second cost is credibility. Illustration signals that the thing being shown was authored rather than observed, which is fine for a diagram and quietly corrosive on a page asking someone to trust you with money or data.

If you use both, assign roles

Most real sites end up with both, and that is fine as long as each medium has a fixed job that never rotates:

Write that down somewhere the whole team can see. Nearly every incoherent site is incoherent because this rule existed in someone's head and not in a document.

Mistakes worth naming

• Illustrating a feeling. A drawing of a relaxed person does not make anyone feel relaxed. Mood is photography's job.
• Photographing an abstraction. The padlock, the glowing brain, the handshake - all attempts to photograph something with no physical form. Draw it or write it instead.
• Switching mediums by page. The fastest way to look like two companies wearing one logo.
• Choosing illustration to avoid the consistency problem, then buying stock illustration. You have kept the problem and lost the credibility.
• Assuming you have nothing to photograph. If your product is software, the product is not the subject - the world around it is. That is a solvable problem, not a reason to give up on photography.

FAQ