To safely replace a copyrighted image, remove it from the live page, swap in a genuinely safe alternative (your own photo, a public-domain work, or properly licensed stock with a saved receipt), then purge cached copies on your CDN and request removal from search caches. Finally, preserve a record of the original file and the removal date, and re-scan your whole site to confirm no other risky images remain. Deleting the file alone is not enough, because copies often linger in places you cannot see from the front end.

Why deleting the file is only step one

When you find a risky image, the instinct is to hit delete and move on. That handles the visible page, but the internet keeps copies. The same image can still be reachable through your content delivery network, your search-engine cache, and public archives long after the original URL is gone.

This matters because enforcement firms and rights holders do not only look at your live site. Getty Images uses PicScout, a perceptual-hash crawler that fingerprints images and matches them wherever they appear. Firms like Higbee & Associates and PicRights build demand letters from evidence they capture at a moment in time, and that evidence can include archived or cached versions. So a clean live page with a dirty cache still leaves you exposed.

If you have not yet identified which images are risky, start with a scan before you start deleting. Our guide on how to audit a website for copyrighted images walks through building the full list so you replace everything in one pass instead of playing whack-a-mole.

Step 1: Remove the risky image from the live site

Begin with the obvious. Remove the image reference from every place it appears: the page or post body, the featured-image slot, theme headers and banners, sliders, and any hard-coded template calls.

On WordPress, deleting an attachment from the media library does not always remove it from pages that still reference the file by URL. Search your content for the filename, not just the media entry. Old posts, landing pages, and email templates often reuse the same asset. Our post on the places copyrighted images hide on your website covers the spots people routinely miss, including theme demo content and duplicate uploads with slightly different filenames.

Do not permanently destroy the file yet. You will want a copy for your records, which we cover in Step 5.

Step 2: Choose a genuinely safe replacement

A replacement is only useful if it does not create the same problem. Here are the categories that hold up, ranked by how defensible they are.

Replacement source	Why it is safe	What to verify
Your own photography or graphics	You are the rights holder	Nothing, as long as no one else's work appears in the frame
Public-domain works	No active copyright	Confirm the work is truly public domain in the US, not just old-looking
Properly licensed stock	You hold a valid license	The license covers your use (web, commercial, print), and you saved the receipt
Free-tier libraries (Unsplash, Pexels, Pixabay)	Permissive default licenses	Each image's specific terms, since some require attribution or restrict certain uses

Free libraries like Unsplash, Pexels, and Pixabay are generally permissive, but "generally" is doing real work in that sentence. Individual contributors sometimes upload images they did not have the right to share, and license terms can vary per image. Read the license shown on the specific photo, and keep a note of where you downloaded it and when.

If you are replacing an AI-generated image, understand that US copyright status for purely AI-created works is unsettled, and using such an image does not automatically protect you if it reproduces a protected work. Check any AI candidate the same way you would check stock, and consider our AI image detector to understand what markers a scan will pick up on the replacement.

For anyone on WordPress replacing images at scale, the WordPress plugin can scan your media library in place so you swap files without re-crawling the whole site by hand.

Step 3: Clear cached and CDN copies

This is the step most people skip, and it is the one that leaves a live claim open after you think you are done.

Removing an image from the live page does not remove cached copies on the Wayback Machine, on your CDN, or in Google's cache. Each of these needs its own action.

Your CDN and page cache

If you use Cloudflare, Fastly, a WordPress cache plugin, or a host-level cache, purge the specific image URL or run a full cache purge. Until you do, the CDN can keep serving the old file from edge nodes even though your origin server no longer has it. Confirm the purge by loading the old image URL directly in a private browser window. It should return a 404 or "not found," not the image.

Google and Bing caches

Search engines keep their own cached snapshots. Use Google Search Console's removal tools to request that the outdated content and cached copy be refreshed or removed. Bing offers a similar content-removal tool in Bing Webmaster Tools. These requests speed up what would otherwise happen slowly on the next crawl.

The Wayback Machine and public archives

Web archives are the hardest to address because they are designed to be permanent. You can submit an exclusion request to the Internet Archive, but there is no guarantee of removal. This is exactly why documentation (Step 5) matters: if an archived copy surfaces later, you want to show the image was removed promptly once discovered.

Verify with a re-crawl

After purging, request the old URL again from a few networks. A cached copy that still loads means the purge did not propagate. Do not assume; check.

Step 4: Confirm the replacement itself is clean

Swapping one risky image for another is a common and expensive mistake. Before you consider a page fixed, run the replacement through a copyright-risk check the same way you would check any image.

A scan looks at visible and invisible watermarks, stock-agency fingerprint matches, AI-generation markers, EXIF and metadata clues, and reverse-image source lookup, then returns a per-image risk score. It flags images for review and estimates risk. It does not confirm infringement, and it is not legal advice. What it does well is catch the obvious problems before they become a letter: a "free" image that still carries a Shutterstock fingerprint, or a stock file whose metadata names a rights holder.

You can check an image's copyright risk for free, with no credit card, on roughly 30 scans. That is enough to vet a batch of replacements before they go live.

Step 5: Preserve evidence and document the fix

Do not shred the original file the moment you remove it. Preserve evidence of the original file and the removal date rather than destroying it, in case a claim arises.

Keep a simple remediation record. For each image you replaced, note:

The original filename and where it appeared on your site
The date and time you discovered it and the date you removed it
The replacement you used and its license or source (with the saved receipt or license page)
Confirmation that the CDN and caches were purged

Why keep the original? If a demand letter arrives later, this record lets you show good-faith remediation and pin down the exact window the image was live. That helps you and any attorney assess exposure. US statutory damages under 17 U.S.C. 504 range from $750 to $30,000 per work, and up to $150,000 for willful infringement, so the difference between "we removed it the day we found it" and "we cannot say when it came down" is meaningful. If a claim does proceed, a documented, prompt fix is easier to defend, whether the venue is a DMCA takedown, the Copyright Claims Board, or federal court.

Store this record somewhere outside the site itself, such as a spreadsheet or a folder in your cloud storage, so it survives any future site rebuild.

Step 6: Re-scan the whole site, not just the fixed page

A single-page fix does not tell you the rest of your site is clean. The same stock file or AI image often appears across multiple pages, in old blog posts, in a secondary theme, and in staging content that got pushed to production.

Re-scanning after replacement confirms no risky images remain across pages, themes, and old posts. Treat it as the closing step of remediation, not an optional extra. Scan the live site, and if you keep a staging environment, scan that too so an old image does not reappear on your next deploy.

Set a reminder to re-scan periodically. Team members add images over time, plugins inject demo content, and a site that was clean in January can pick up risk by June.

Frequently Asked Questions

Does deleting an image from my site remove it from Google's cache?

No. Deleting the file removes it from your live pages, but Google, Bing, your CDN, and web archives keep their own copies until each is cleared separately. Use Search Console and Bing Webmaster Tools to request removal, purge your CDN, and verify the old URL no longer loads.

Are Unsplash, Pexels, and Pixabay images safe to use as replacements?

They are permissive by default, which makes them good candidates, but you should still verify each image's specific license terms. Contributors occasionally upload work they did not have rights to, and some images carry attribution or usage conditions. Save a note of the source and date for every image you use.

Should I delete the original file completely?

Not immediately. Preserve a copy of the original and record the removal date before destroying anything. If a claim arises later, that record helps establish when the image was live and shows you acted promptly once you found it.

Can PixGuard tell me if an image is definitely infringing?

No. PixGuard flags images for review and estimates copyright risk based on watermarks, stock fingerprints, AI markers, metadata, and source lookup. It returns a risk score to help you prioritize. It does not confirm infringement and is not legal advice. Treat a high-risk flag as a reason to replace the image or consult an attorney.

How do I know my whole site is clean after replacing images?

Re-scan every page, including old posts, secondary themes, and staging, after you finish replacing. A single-page fix does not account for the same image appearing elsewhere. A full re-scan confirms no risky images remain before you consider the remediation complete.

Fix it once, and confirm it stuck

Replacing a copyrighted image safely is a chain: remove it, replace it with something genuinely safe, clear every cache and CDN copy, document what you did, and re-scan to prove the site is clean. Skip a link and you can still get a letter for an image you thought was gone.

Ready to verify your replacements and confirm nothing risky is left? Run a free scan of your images with no credit card and see the risk flags before an enforcement firm does.

How to safely replace copyrighted images on your site