The photo you found on Google is somebody's invoice waiting to happen

How an image-rights letter finds a small business site

A letter arrived last week about a single photograph on your services page. You had no idea, standing there rereading it, where that photograph had even come from.

That's the common shape of these letters. Nobody remembers adding the image, because nobody who's still around actually did.

A stock library or a photographer's agency runs automated crawls of the open web. It matches an image against its own database. Then it sends a letter to whoever's domain is hosting it now — regardless of who uploaded it, or when, or why.

The business gets the bill either way. The letter doesn't care about your staff turnover.

Some letters come from a legitimate rights holder with a real claim. Others are speculative, sent in bulk, hoping a small business pays quietly rather than checking. Either way, the underlying question is the same: can you prove where the image came from.

That single question decides how the rest of the conversation goes. A clear receipt ends it in one reply. No receipt means a longer, more expensive back and forth, with a lawyer involved on at least one side of it.

Free, royalty-free, and licensed are three different things

The words get used like synonyms and they are not. "Free" means no cost and, ideally, an explicit license saying so. Read the actual terms — some "free" images only permit personal use.

"Royalty-free" does not mean free at all. It means you pay once and don't pay again per use, which is a licensing model, not a price of zero.

"Licensed" covers a wider range still, from a broad commercial license down to one that names a single specific use and nothing beyond it.

None of these labels are interchangeable. A lot of the disputes start with someone assuming they were. A photo bought for a print brochure, for instance, may never have been cleared for a website at all.

The license a designer bought, and whether it followed the site

A designer buys a stock photo license under their own account, for a specific project. That license does not automatically transfer when the relationship with the designer ends.

The image stays on the site. The paperwork proving the right to use it does not. That gap is where the trouble starts.

Without a receipt or a license certificate on file, there's no way to prove the image was ever properly licensed in the first place. Not to a letter-writer, and not to yourself either.

This is the single most common gap owners discover when a letter forces the question. Nobody was hiding anything. The receipt simply lived in an account nobody still has access to.

Fonts and icons carry licenses of their own

A font downloaded from a free-looking site can carry the same problem as a photo. Free to view is not the same as free to embed in a commercial website. Web-embedding rights are sometimes sold separately from desktop-use rights entirely.

Icon sets carry the same layered licensing. A set that's free for a printed flyer isn't automatically clear for an unlimited-traffic website. Check the license file that came with the font or icon set before assuming it's covered.

A font is easy to swap once you know it's a problem. Plenty of well-licensed alternatives exist, and switching one rarely touches anything else on the page.

A font pairing chosen for the brand can be matched closely, in nearly every case, by something properly licensed. The visual difference, once swapped, is rarely something a customer would ever notice.

Photographs of customers, staff, and other people's premises

A photo you took yourself avoids the licensing problem and creates a different one: the people and places inside it. A customer photographed at your shop. A staff member's face on the team page. Another business's storefront used as a before-and-after comparison.

All of these can need permission from the person or business in the photo. That's separate from any copyright question about who took it.

A quick verbal yes at the time is worth turning into something in writing. Even a short email, sent before the photo goes on the site, is enough. It costs almost nothing and it settles the question for good.

A staff photo is worth revisiting when someone leaves the business, too. Consent given while they worked there doesn't automatically carry the same weight once they've gone from the payroll.

Replacing an image you are no longer sure about

If a letter arrives, or you simply can't account for where an image came from, the safest move is to swap it rather than argue about it. Replace it with a photo you took yourself. Or a licensed image with a receipt on file. Or one from an open-license library that publishes clear, checkable terms.

Keep a folder — even a simple one — of the license or receipt for every image the site uses going forward. It's the single easiest habit that prevents this from happening again. Five minutes per image, saved once, beats an afternoon spent guessing later.

This sits inside a wider legal-adjacent set of pages worth knowing about — the accessibility, privacy, and cookie questions a small site also touches cover similar ground. The images you're cleared to use still need a description a screen reader can announce, which is a separate step from clearing the rights.

The copyright notice on your own original material belongs on the terms of use page, and who actually owns the artwork and files on the site at all is answered in full at who owns your website once it's built.

More from the blog

All posts