Your Editors Are Using Images They Shouldn’t. You Already Know It.

This article is for general informational purposes only and does not constitute legal advice. Copyright law is complex and fact-specific. If you have received a demand letter or believe you may be facing an infringement claim, consult a qualified intellectual property attorney.

---

You know it is happening. You have seen the screenshots in Slack, the images in stories that look like they came straight from a Getty watermarked search result, the wire service photos that somehow made it into the CMS without a license number attached to anything. You have not said anything because what exactly would you say, and to whom, and what would change.

Nothing would change. That is the problem.

The Workflow Is the Problem, Not the People

Editorial staff are not stealing images. They are doing their jobs under conditions that make checking image licenses an unreasonable ask. They have thirty minutes to get a story live. The photo desk is understaffed or does not exist. Nobody ever sat them down and explained the difference between a Creative Commons license and a royalty-free stock image and an AP wire photo that costs $400 to license properly.

They grab the image that looks right. They move on. The story goes live. Nothing happens. So they do it again.

This is not a character problem. It is a systems problem. The workflow has no friction at the point where friction would actually matter. By the time a copyright enforcement firm finds the image, weeks or months have passed, the story is buried in the archive, and the editor who uploaded it has no memory of where it came from.

You cannot fix that with a memo. You cannot fix it with a policy. You can only fix it by putting a check in the workflow before the image goes live.

Why You Have Not Said Anything

There is a specific kind of organizational discomfort that comes from being the person who sees a problem that nobody else wants to acknowledge. You are the IT director, the web editor, the person who manages the CMS. You are not the publisher. You are not the editor in chief. You do not set editorial policy.

Telling a reporter or an editor that they are doing something wrong feels like overstepping. Escalating to the publisher feels like making a mountain out of something that has not blown up yet. So you say nothing, and you watch it keep happening, and you carry the low-grade anxiety of knowing that one of those images is going to cost somebody a significant amount of money.

That anxiety is not irrational. The exposure is real. AP and Getty run active enforcement programs with automated tools that crawl the web continuously. The settlement letters they generate do not distinguish between a small regional paper and a major media company. The math is the same.

What You Actually Need

You need a system that takes the conversation out of the interpersonal and puts it into the workflow. Not a policy document that editors acknowledge and ignore. Not a training session that people forget by the following Tuesday. A technical intervention that fires automatically every time an image is uploaded and creates a record that the check happened.

That way the conversation is never “I told you not to grab images from Google.” It is “the system flagged this image before it went live and here is the log entry showing what the editor did with that information.” That is a defensible position. That is documentation. That is the difference between an organization that took reasonable steps and one that did not.

PhotoCheckWP is a WordPress plugin that does exactly that. Every image upload triggers an automatic reverse image search. If potential matches are found, the editor sees them and has to make a decision before the image can be inserted. Every upload, every match, every acknowledgment is logged with a timestamp and the editor’s name. Nothing gets through silently.

The Conversation You Can Now Have

Once the plugin is running, the conversation changes. You are not the person pointing a finger at editorial staff. You are the person who installed a system that protects them and the organization. The log is not a disciplinary tool. It is a paper trail that demonstrates due diligence.

If a demand letter ever arrives, you have documentation. You checked. The editor acknowledged. The decision was made with information in front of them, not in the dark. That matters in any dispute about whether the infringement was willful.

And most of the time, the system just runs. Editors go about their work. Images get checked. The ones that look clean go through. The ones with matches get a second look. The organization is protected and nobody had to have an uncomfortable conversation about it.

That is the system you have been waiting for someone to build. It exists now.

The Bottom Line

You are not wrong about what you are seeing. The images that should not be there are probably there. The exposure is probably real. The letter that has not arrived yet is not evidence that the problem does not exist.

You do not have to be the person who makes it a political issue inside your organization. You can be the person who quietly installed the tool that fixed it.

That is a better story to be in.

---

---

The PhotoCheckWP Team writes about image copyright, editorial workflow, and the real cost of unlicensed images in digital publishing. We built this tool because we watched the problem happen from inside newsrooms — and because we paid for it ourselves.