If you’re building or refreshing a website, at some point you’re going to face the photography question. Do you need a professional shoot? Can you use your own photos? What about stock photos?
The honest answer is: it depends. But there are some clear principles worth knowing before you make any decisions.
Real photos are almost always better… with one catch
Original photography – your team, your space, your work – will almost always outperform stock on a website. People connect with real businesses through real images. When someone lands on your site and sees your actual faces and your actual environment, it builds trust in a way that stock photos simply can’t replicate.
But here’s the catch: they have to be good quality.
Blurry photos taken on an old phone, shots with bad lighting, or images that look dated can actually work against you. In that case, quality stock photos are a better option than poor originals.
What most clients actually have
In my experience, genuinely good photography is the exception, not the rule. A small number of clients come to a project with a solid set of professional images ready to go – which makes everything easier. But most businesses have a mix of self-taken photos, old images, or shots that just aren’t up to the standard their business deserves.
That’s not a criticism – it’s just the reality. Getting good photos takes time and money, and it’s often something that gets pushed to the bottom of the list.
When a client doesn’t have what they need, my first recommendation is always to get a photographer. The return on a half-day shoot is significant. I keep a short list of photographers I trust and I’ll always make that introduction if it’s the right fit.
Where stock photos still have a role
Even clients with great original photography usually need stock images somewhere. Side images, background sections, supporting visuals – there are places on most websites where stock photos make sense, either because original images don’t exist or because the context calls for something more abstract.
Some industries can also lean on stock more heavily than others. Trades and service businesses, for example, don’t always have a visually rich environment to photograph. A plumber’s workshop isn’t the same as a restaurant kitchen. In those cases, well-chosen stock photos fill the gaps without hurting the overall impression.
On the flip side, there are industries where original photography isn’t just better – it’s important. Medical practices need photos of their actual staff and facilities. Food businesses need images of their real food. The about page, regardless of industry, almost always needs real photos of the people behind the business. That’s non-negotiable. Trust is what an about page is built on, and a page full of stock photos can undermines the whole thing.
What makes a stock photo actually work
The single biggest mistake with stock photos is choosing ones that look obviously like stock photos. You know the ones – six people around a boardroom table giving cheesy grins to the camera, someone on a headset looking thrilled to be taking calls, a group of professionals giving an enthusiastic thumbs up.
Nobody believes those images. They register instantly as fake and they erode trust rather than build it.
Good stock photography feels like it could be real. It might be a close-up, something slightly abstract, or an environmental shot. It doesn’t have to be perfect – in fact, slightly imperfect images often feel more genuine than the overly polished ones.
A few other things to watch for:
Overused images. Some stock photos are so good that they end up on dozens of websites in the same industry. If a competitor is using the same hero image as you, that’s a problem. Do a reverse image search on any photo you’re seriously considering.
Relevance. A vaguely related image is almost always worse than no image. If you can’t find something that genuinely reflects what you do, it’s worth considering whether that space needs a photo at all.
How you use them. The same stock photo can look generic as a flat image and much more considered with some thoughtful treatment – your brand colours in an overlay, a particular crop, or the way it’s paired with other design elements. Context matters.
What about AI-generated images?
This is worth addressing because it’s changed a lot recently.
As of 2026, AI-generated photography has genuinely improved to the point where the obvious tells – strange hands, unnatural skin, artifacts around edges – are far less common than they were even twelve months ago. There are AI images now that are difficult to distinguish from real photography.
That means AI images are a legitimate option worth considering, particularly in situations where original photography isn’t available and suitable stock is hard to find.
But the same principles apply. An AI image that looks synthetic, overly perfect, or just slightly off will still trigger the same subconscious response as a bad stock photo. A good quality website works because they build trust and connection – anything that makes a visitor feel like they’re being presented with something artificial chips away at that.
If you use AI images, use them sparingly, in the right contexts, and apply the same quality filter you’d apply to anything else. Authentic-feeling, relevant, and not overdone.
A simple framework
When you’re thinking about photography for your website, the priority order looks something like this:
- Original, professional photography — always the best option when budget and logistics allow
- Original photos you’ve taken yourself — fine if the quality is genuinely good
- Quality stock photos — appropriate in the right contexts and industries
- AI-generated images — a viable option when used carefully and sparingly
- Poor quality photos of any kind — worse than no photo at all
The goal, regardless of which option you’re working with, is the same: images that look real, feel relevant, and don’t make a visitor question whether your business is what it says it is.
If you’re not sure what’s right for your situation, it’s worth having that conversation before the build starts – not after.
