You can't fully stop someone from copying an image off the web—right-click still exists, and screenshots are unlimited. What you can do is stop other sites from burning your bandwidth, reduce casual theft, and keep Google seeing you as the original source.
Understand what you're protecting
- Bandwidth: other sites embed your image URLs directly (hotlinking)
- Brand: competitors reuse product photos
- SEO: duplicate images ranking in image search
Different problems need different tools. Watermarks help brand recognition; they don't stop downloads.
Block hotlinking at the server or CDN
On Apache, .htaccess rules can allow your domain and search engines while blocking empty referrers or foreign sites. Cloudflare Hotlink Protection does similar with less server config. WordPress plugins like All In One WP Security include hotlink toggles for beginners.
Disable right-click (optional, limited value)
JavaScript that blocks context menu annoys legitimate users and doesn't stop DevTools. Use sparingly on portfolio sites if clients insist—know it won't stop determined copiers.
Watermark and metadata
Semi-transparent logos on corner of product shots discourage reuse in ads. Embed copyright in EXIF/IPTC where workflows allow. Document ownership for DMCA requests if a marketplace seller steals your catalog.
Lazy load and lower-res public versions
Serve full-resolution files only when needed (lightbox, download purchase). Public blog images can be compressed 1200px wide—good for speed and slightly less attractive to resellers.
Search engine and AdSense context
Google Image search respects canonical pages when you use descriptive alt text and structured data on the page hosting the image. For AdSense sites, stolen images rarely cause disapproval, but duplicate content across your own posts can. Use unique featured images per article.
Legal and practical escalation
Keep source files and publish dates. For commercial theft, a DMCA notice to the host often works faster than public arguments. For WordPress specifically, disable direct browsing of uploads if you're not using those URLs publicly—some security guides recommend it; test breaks before enforcing.
Realistic summary
Combine CDN hotlink protection, sensible image sizes, clear alt text, and visible copyright in footer or image captions. That covers 90% of what small publishers need without chasing impossible "100% protection" plugins.
CDN configuration examples
On Cloudflare, enable Hotlink Protection under Scrape Shield. Allow your domain and Google image cache referrers if images appear in search. Test RSS readers and newsletter tools that embed images—they may need referrer exceptions.
WordPress media library hygiene
Rename files on upload with descriptive slugs (wordpress-header-edit.webp) for image SEO. Disable attachment pages if your theme creates thin /attachment/ URLs that compete with posts.
Commerce and product photography
WooCommerce stores should use consistent aspect ratios and watermarks on catalog shots sold elsewhere. Document shoot dates for DMCA; marketplaces respond faster with EXIF proof.
Monitoring unauthorized use
Google reverse image search and TinEye monthly on hero product shots. Set alerts for brand name plus file name in Google Alerts—low signal but occasionally catches scrapers.