Hotlink Protection can restrict other sites from embedding selected files hosted on your account. It can reduce unwanted bandwidth use, but it is not digital-rights protection and cannot prevent someone from downloading and republishing a public image.
IN THIS ARTICLE
What you need before you begin
List every legitimate hostname that embeds your files, including www, subdomains, a shop frontend and any required preview or CDN domain. Record the current settings before changing them, because disabling the feature can clear its allowlist.
01 Prevent unwanted image hotlinking with cPanel
- Open Hotlink Protection in cPanel and enable the feature when appropriate.
- Review the allowed URLs and include the legitimate website variants. A missing secure or alternate hostname can cause your own pages to show broken images.
- Select only the extensions you intend to protect. Consider feeds, newsletters and external business integrations before blocking a file type broadly.
- Decide whether direct requests should be permitted. This affects visitors opening an image URL without an ordinary referring page, so test that use case deliberately.
- Save the configuration, then test images from your own pages and from an unauthorised external embedding page. If using a cache or CDN, clear only the relevant cached test objects when necessary.
Confirm the expected result
Your website should display its assets normally while the unwanted embedding request is restricted according to the saved rule. Test mobile and private browser sessions as referrer handling can differ.
Why are legitimate website images blocked by Hotlink Protection?
If legitimate images fail, review allowed URLs and referrer policy rather than changing file permissions to 777. Temporarily restore the previous hotlink settings to isolate the cause. Keep a copy of the allowlist before disabling the feature for troubleshooting.