
Your pages load, your text shows, but the images are broken. Open an image address directly, and the browser answers: 403 Forbidden. When wordpress media files returning 403 error strikes, readers see empty boxes where your pictures should be, and the images you uploaded seem to have vanished — even though they are still on the server.
The good news is that a 403 error means “forbidden”, not “missing”. The file is usually still there, and something — permissions, a security rule, a plugin, or a firewall — is refusing to serve it. This guide works through those causes in order, from the simplest check to the deeper server fixes. Before you change any file or setting on the server, take a full backup of the site, including the database, so you can restore it if anything goes wrong.
Table of Contents
- Why This Error Happens
- Quick Checks
- Diagnosing the Problem
- Fix 1: Check the File URL and Clear the Cache
- Fix 2: Fix the File and Folder Permissions
- Fix 3: Reset the Permalinks and Check the Main .htaccess File
- Fix 4: Check the .htaccess File Inside the Uploads Folder
- Fix 5: Deactivate Security Plugins and Test Again
- Fix 6: Turn Off Hotlink Protection Temporarily
- Fix 7: Check CDN and Firewall Rules
- Fix 8: Fix HTTPS Redirects and Mixed Content
- Fix 9: Ask Your Host to Check File Ownership
- Fix 10: Ask Your Host to Check the Server Firewall
- Fix 11: Restore from a Backup and Rebuild the Media Library
- What to Avoid
- Frequently Asked Questions
- Conclusion
- Helpful Official Resources
Why This Error Happens
A 403 error is the server saying no. The browser asks for an image, the server finds the file, and then a rule decides the request is not allowed. The file is not deleted and the page is not broken — the request is refused. These are the reasons a request gets refused most often.
1. The File or Folder Permissions Are Wrong
Permissions are numbers that control who can read files on the server. If an image file has permissions that block reading, or the folder holding it blocks entry, the server refuses the request with a 403 error. Wrong permissions often appear after moving a site, restoring a backup, or changing hosts, when the move resets the numbers to values that do not suit WordPress. This is the most common cause of wordpress media files returning 403 error.
2. A Rule in .htaccess Blocks the Request
The .htaccess file holds rules that control how the server handles requests. A rule meant to block malicious requests can also block legitimate image requests, especially rules that block hotlinking, block certain file types, or deny access to the uploads folder. One wrong rule in .htaccess can block every image on the site at once.
3. A Security Plugin Blocks Image Requests
Security plugins inspect requests and block ones that look suspicious. A rule that is too strict, or a plugin that misreads normal image requests as attacks, blocks the images along with the threats. The block often starts after a plugin update changes the rules, so images that worked yesterday fail today with no other change to the site.
4. Hotlink Protection Blocks Your Own Site
Hotlink protection stops other websites from using your images, by checking where the request came from. If the protection is misconfigured, it can block requests from your own site too — especially after changing domain names, switching to HTTPS, or adding a content delivery network. Your own pages then show broken images, because the server thinks your own site is an outsider.
5. A CDN or Firewall Rule Blocks the Files
A content delivery network, often called a CDN, serves your images from servers around the world, and a firewall inspects requests before they reach your site. A CDN rule that blocks a file type, a firewall rule that blocks a pattern in image addresses, or a CDN cache holding an old 403 response can all refuse image requests. The files on your server are fine — the block happens before the request reaches them.
6. The Server User Does Not Own the Files
Even with correct permissions, the server can refuse files it does not own. After a migration, files sometimes end up owned by a different account, and the web server cannot read them. The result is a 403 error on every affected file, while files with correct ownership load normally. Only the hosting provider can fix ownership safely, so wordpress media files returning 403 error after a move usually needs the host’s help.
Quick Checks
Two minutes before the deep fixes.
- Open one broken image address directly in the browser — does it show 403, or a different error?
- Check whether all images fail, or only images in certain folders or months.
- Open the site in a private browsing window — do the images load there?
- Check your hosting control panel for a hotlink protection or security setting that was recently changed.
- Think about when it started — did wordpress media files returning 403 error begin after moving hosts, adding a CDN, or updating a security plugin?
- Check Tools, then Site Health, for warnings about file permissions or security settings.
Diagnosing the Problem
| Symptom | Cause | Go to Fix |
|---|---|---|
| All images show 403 | Wrong permissions or a blocking rule | Fix 2 |
| Only some folders show 403 | Permissions wrong in those folders | Fix 2 |
| Images fail after a security update | Security plugin blocking requests | Fix 5 |
| Images fail after adding a CDN | CDN or firewall rule | Fix 7 |
| Images fail after moving to HTTPS | Redirect or mixed content rule | Fix 8 |
| Images fail after moving hosts | File ownership is wrong | Fix 9 |
| Images load in private browsing only | Stale cache holding a 403 response | Fix 1 |
| Images fail only when embedded elsewhere | Hotlink protection too strict | Fix 6 |
Fix 1: Check the File URL and Clear the Cache
Start with the address and the cache, because both are quick checks and both can fake a 403 error. A wrong address, or a cached copy of an old error, looks exactly like a server block.

- Right-click a broken image on your site and choose Open image in new tab, or copy the image address.
- Look at the address: it should start with your domain and include wp-content/uploads and the year and month folders.
- If the address names an old domain or a wrong folder, the page is pointing at the wrong place — note the address for Fix 8.
- If the address looks right and still shows 403, clear your browser cache and reload the image address.
- Clear the site cache too, through your caching plugin or your host’s control panel, if you use one.
- If you use a CDN, purge the CDN cache for the image address, or purge the whole cache.
- Test the image address again in a private browsing window, where no cache interferes.
Caches hold old responses, including old errors. If an image returned 403 once — during a brief permissions problem, for example — the cache can keep serving that 403 long after the problem is fixed. Clearing the browser cache, the site cache, and the CDN cache removes every stale copy at once. The private browsing test is the honest one: it fetches the image fresh, with no cached response in the way. If the image loads in private browsing but not in your normal browser, the cache was the whole problem. If it shows 403 everywhere, the block is on the server, and Fix 2 checks the permissions that most often cause it.
Fix 2: Fix the File and Folder Permissions
Permissions control who can read a file. If an image file, or the folder holding it, has permissions that block reading, the server answers every request with 403. Setting the standard WordPress permissions fixes this at once.
- Before you start, take a full backup of the site, including the database, so you can restore it if needed.
- Open your host’s File Manager and go to the wp-content/uploads folder.
- Right-click the uploads folder and choose Permissions or Change Permissions.
- Set folders to 755 and files to 644 — these are the standard WordPress permissions.
- Apply the change to the folder and all the folders and files inside it, if the File Manager offers that option.
- Never set permissions to 777 — that gives everyone full access and leaves the site open to attack.
- Test a broken image address again and check whether it loads.
The numbers 755 and 644 are the standard values WordPress expects. In plain language, 755 on a folder means the owner can read, write, and enter it, while others can read and enter it. 644 on a file means the owner can read and write it, while others can only read it. Those values let the server serve images to readers while keeping the site reasonably safe. Setting 777 removes all protection and is never the right fix, even if it seems to work — it invites abuse, and many hosts will flag or revert it. Some hosts offer a permissions repair tool in the control panel that sets the standard values safely; use that if your host provides it. Check a few folders, not just the top one: permissions can be wrong in one month folder while the rest are fine, which explains why only some images fail. If the permissions are already correct and images still show 403, a rule in .htaccess is the next suspect, and Fix 3 checks it. For pages that show a different error, our guide to WordPress 404 error fix covers missing pages.
Fix 3: Reset the Permalinks and Check the Main .htaccess File
The .htaccess file in the site’s main folder holds the rules that route requests. A damaged or outdated .htaccess file can block image requests, and resetting the permalinks rebuilds it with fresh, correct rules.
- Before you start, take a full backup of the site, including the database, so you can restore it if needed.
- Go to Settings, then Permalinks, in the WordPress dashboard.
- Without changing anything, click Save Changes — this rebuilds the .htaccess rules.
- Test a broken image address and check whether it loads now.
- If it still shows 403, open your host’s File Manager and find the .htaccess file in the site’s main folder.
- Download a copy of .htaccess to your computer before editing it, so you can restore it if anything goes wrong.
- Read the file for rules that deny access, block file types, or mention the uploads folder — if you find one and are unsure what it does, ask your host to review it before changing it.
Resetting permalinks is safe and quick, and it fixes .htaccess problems caused by incomplete updates or failed saves. The file itself deserves care: it controls how the server handles every request, and a wrong edit can take the site down. Save a copy before opening it, change one thing at a time, and test after each change. Rules added by security plugins are the usual suspects in .htaccess — a rule meant to block bad requests can match image addresses by mistake. If you did not write the rules yourself, ask your host to review them. They can tell in seconds whether a rule blocks images. If the main .htaccess file is clean, a second .htaccess file inside the uploads folder may be the block, and Fix 4 checks that.
Fix 4: Check the .htaccess File Inside the Uploads Folder
Some sites have a second .htaccess file inside the wp-content/uploads folder, placed there by a security plugin or by the host. Its rules apply only to the uploads folder, so it can block every image while the rest of the site works perfectly.

- Before you start, take a full backup of the site, including the database, so you can restore it if needed.
- Open your host’s File Manager and go to the wp-content/uploads folder.
- Turn on the option to show hidden files, if the File Manager has one — .htaccess files are hidden by default.
- Look for a file named .htaccess inside the uploads folder.
- If there is no such file, skip this fix — the block is elsewhere.
- If there is one, download a copy to your computer, then rename the original to
.htaccess-backupto disable it temporarily. - Test a broken image address — if it loads now, the rules in that file were blocking the images, and your host or security plugin author should review them.
Do not delete the file outright. Renaming it disables it while keeping it recoverable, so you can restore it in seconds if the test proves it innocent. Security plugins place this file to stop scripts from running inside the uploads folder, which is a sensible protection — but a rule that is too broad blocks images too. The right fix is usually to keep the protection but correct the rule, and that is a job for the plugin author or your host, not a guess. If renaming the file changes nothing, rename it back at once, so the protection stays in place. If there is no second .htaccess file, the block may come from a security plugin’s other rules, and Fix 5 tests that. For a Media Library that will not load, our guide to WordPress media library not loading covers that problem.
Fix 5: Deactivate Security Plugins and Test Again
Security plugins can block image requests with rules that are too strict, or with firewall features that misread normal requests. Deactivating them temporarily shows whether one of them is the block.
- Before you start, take a full backup of the site, including the database, so you can restore it if needed.
- Go to Plugins, then Installed Plugins, in the WordPress dashboard.
- Deactivate the security plugins first — one at a time — testing an image address after each one.
- If an image loads after deactivating a plugin, that plugin is the block — leave it deactivated for now.
- Check the plugin’s settings for firewall rules, blocked request patterns, or an uploads protection option.
- Look for an update to the plugin, since the block may be a known fault fixed in a newer version.
- If the plugin is essential, ask the plugin author for help through the official support forum, and describe the 403 error.
Deactivate security plugins one at a time rather than all at once, so you know exactly which one is responsible. Keep the test short: deactivate, test, and reactivate or replace within the same session, so the site is not left unprotected. A security plugin that blocks images is usually misconfigured rather than broken — a firewall rule, a country block, or a rate limit that catches normal readers. The plugin’s own logs often show the blocked requests, with the rule that blocked them, which makes the fix obvious. If no plugin is the cause, hotlink protection is the next suspect, and Fix 6 tests it. For a broader guide to plugin problems, our guide to WordPress plugin conflict fix covers the full process.
Fix 6: Turn Off Hotlink Protection Temporarily
Hotlink protection stops other websites from displaying your images, by checking the referring page of each request. If it is misconfigured, it blocks requests from your own site too, and your own pages show broken images.
- Open your hosting control panel and find the hotlink protection setting — it is often under Security or HotLink Protection.
- Note the current setting before changing it, so you can restore it afterwards.
- Turn hotlink protection off temporarily.
- Test a broken image address, and test a page that shows broken images.
- If the images load now, hotlink protection was the block — the allowed list needs your own domain on it.
- Turn hotlink protection back on, and add your own domain, including the version with and without www, to the allowed list.
- If you use a CDN, add the CDN domain to the allowed list too, then test again.
Hotlink protection breaks most often after a domain change, a move to HTTPS, or adding a CDN, because the request now arrives looking different from what the allowed list expects. A request from the HTTPS version of your site can be blocked by a list that only allows the HTTP version. A request served through a CDN can arrive with the CDN domain as the referrer, which the list does not recognise. The fix is to keep the protection on but to list every domain your site legitimately uses. If your host has no hotlink protection setting, the protection may live in .htaccess rules instead — ask your host to check for hotlink rules there. If hotlink protection is off and images still show 403, the CDN or firewall is the next suspect, and Fix 7 checks those.
Fix 7: Check CDN and Firewall Rules
A CDN and a firewall sit between readers and your server, and either can refuse image requests before they reach WordPress. A rule that blocks a file type, a cached 403 response, or a firewall pattern that matches image addresses can all produce this error.

- Log in to your CDN or firewall dashboard, if you use one.
- Purge the CDN cache completely, so no stale 403 response is served.
- Check the firewall rules for any rule that blocks image file types, the uploads path, or a pattern in image addresses.
- Check the firewall event log for blocked requests to image addresses, and note which rule blocked them.
- Temporarily set the CDN or firewall to bypass mode, if it offers one, and test an image address.
- If the image loads in bypass mode, a CDN or firewall rule is the block — correct or remove that rule.
- Turn bypass mode off again after the test, so the site is protected, and purge the cache once more.
The firewall event log is the fastest evidence here. It shows each blocked request, the address requested, and the rule that blocked it. A rule that blocks a pattern like a file extension, or a rule that blocks requests without a certain header, can catch image requests by mistake. CDN caching adds a second layer: even after the rule is fixed, the CDN can keep serving the cached 403 until the cache is purged. Purge after every change, and test in a private browsing window. If you do not use a CDN or a firewall service, skip this fix — the block is on the server itself. If the CDN and firewall are clean, the HTTPS setup is the next suspect, and Fix 8 checks it.
Fix 8: Fix HTTPS Redirects and Mixed Content
After moving to HTTPS, redirect rules can send image requests in circles, or block requests that still use HTTP. A redirect loop or a strict transport rule can turn image requests into 403 errors, especially when the site address and the image addresses disagree about HTTP and HTTPS.
- Go to Settings, then General, in the WordPress dashboard.
- Check that the WordPress Address and Site Address both start with
https://and name the correct domain. - If either still uses
http://, change it tohttps://and save — take a backup before changing these settings. - Check that your SSL certificate is valid: open the site in a browser and look for the padlock symbol.
- Test an image address with HTTPS directly, and then with HTTP, and note which one fails.
- If HTTP image addresses fail but HTTPS ones work, ask your host to check the redirect rules in .htaccess or the server settings.
- Clear all caches — browser, site, and CDN — after any address change, and test the images again.
Mixed content is a related problem: a page loaded over HTTPS that asks for images over HTTP. Browsers may block those images, and the result looks like broken images even though the server would serve them. Fixing the site address to HTTPS usually fixes new content, but older posts may still hold HTTP image addresses in their content. A search-and-replace of the old address, done by your host or with a reputable plugin, updates those older addresses safely. Do not edit the database by hand to fix addresses — the data format breaks easily. If the addresses are correct and the certificate is valid, the file ownership may be the cause, and Fix 9 asks your host to check it. For HTTPS problems more broadly, our guide to WordPress HTTPS not working properly covers that fix.
Fix 9: Ask Your Host to Check File Ownership
Ownership decides which server account can read a file. If the image files are owned by a different account than the one the web server runs as, the server refuses them with 403, even when the permissions look correct. Only the host can fix ownership safely.
- Note which images fail and which load — a pattern by folder or date helps the host find the cause.
- Contact your hosting provider’s support and describe the 403 error and the fixes you have already tried.
- Ask them to check the ownership of the wp-content/uploads folder and the files inside it.
- Ask them to set ownership so the web server user can read the image files.
- Ask them to confirm the permissions at the same time, so ownership and permissions are fixed together.
- After they confirm the change, test several image addresses, including ones from different months.
- Keep a note of what they changed, so the same problem is faster to solve if it returns after a future move.
Ownership problems almost always follow a site move. When files are copied from one server to another, they can arrive owned by the account that copied them, rather than by the account the web server uses. The result is a site whose pages load fine but whose images are refused. Do not try to change ownership yourself with server commands unless you know the server well; a wrong ownership change can lock you out of your own files. Your host changes ownership routinely and can do it in minutes. When you contact them, mention that the problem started after a move, if it did — that single detail points them straight at ownership. If ownership is correct and images still show 403, a server firewall may be the block, and Fix 10 asks your host to check it.
Fix 10: Ask Your Host to Check the Server Firewall
The server firewall inspects requests before WordPress sees them. A firewall rule that is too strict, or a security module that misreads image requests, can refuse them with 403. These rules are invisible from the dashboard, and only your host can see and change them.

- Note the exact image addresses that fail, and the time you tested them.
- Contact your hosting provider’s support and describe the 403 error and the fixes you have already tried.
- Ask them to check the server firewall and security modules, such as ModSecurity, for rules blocking image requests.
- Ask them to check the server error log for the exact reason the requests were refused.
- Ask them to test one failing image address from the server side, to confirm the block.
- Apply whatever fix they recommend, and test the image addresses while they are still helping you if you can.
- Ask them to confirm the fix in writing, so you have a record if the problem returns.
ModSecurity is a firewall that inspects requests and blocks ones that match attack patterns. A pattern that matches part of an image address, or a rule triggered by a query string on the image address, can block legitimate images. The error log shows exactly which rule fired, which makes the fix obvious to the host. Do not try to disable the firewall yourself — it protects the whole site, and the right fix is to correct the one rule, not to remove the protection. If the host finds no firewall block and images still show 403, the last resort is a clean restore, which Fix 11 covers.
Fix 11: Restore from a Backup and Rebuild the Media Library
When every fix has failed, restoring from a backup taken before the problem started removes whatever change broke image serving. Rebuilding the media setup cleanly, with the host’s help, gives the site a fresh start.
- Before you start, take a fresh backup of the site as it is now, so nothing is lost by restoring.
- Find the most recent backup from before the 403 problem started.
- Ask your host to restore that backup, or restore it through your backup plugin, following its instructions.
- After the restore, check that the uploads folder has permissions 755 and the files have 644.
- Test several image addresses, including ones from different months, and confirm they load.
- If the restore fixes the images, reapply any changes made since the backup — new posts, new settings — one at a time, testing images after each.
- If the restore does not fix the images, ask your host to check the server itself, since the fault must be outside the site files.
Restoring is a bigger step than the earlier fixes, which is why it comes last. It can undo recent work, so the fresh backup in step 1 matters: it lets you recover anything the restore removes. The step-by-step reapplication in step 6 is how you find the change that broke image serving — if images fail again after one particular change, that change is the cause. If wordpress media files returning 403 error survives a restore and a rebuilt folder structure, the fault is on the server itself, and your host must fix it or move the site to a healthy server. Keep the record of everything you tried, because it shows the host that the site side has been fully checked. Do not keep changing settings at random after a restore — each untested change adds a new possible cause.
What to Avoid
- Do not set permissions to 777 — it leaves the site open to attack and most hosts will flag it.
- Do not delete the .htaccess file to fix the error — back it up and rename it to test, so you can restore it.
- Do not leave a security plugin deactivated after testing — reactivate it or replace it the same day.
- Do not leave a CDN or firewall in bypass mode after testing — turn protection back on.
- Do not edit the database by hand to fix image addresses — use your host or a reputable plugin instead.
- Do not ignore the backup step before server changes — a backup turns a risky edit into a safe one.
- Do not change server firewall rules yourself unless you manage the server — ask your host instead.
Frequently Asked Questions
Why do images show 403 but pages load fine?
Because the block applies to the image files, not to the pages. Permissions, an .htaccess rule, or a firewall rule can refuse image requests while page requests pass. The page loads, the image request is refused, and the browser shows a broken image box. Fixes 2, 3, and 10 cover the three layers.
Why do only some images show 403?
Because the cause affects only some folders or some files. Permissions can be wrong in one month folder, a rule can match only certain file names, or ownership can be wrong for files copied at a certain time. Compare a working image address with a failing one and look for the folder or date pattern. Fixes 2 and 9 help you follow the pattern.
Is a 403 error the same as a 404 error?
No. A 404 error means the file was not found — it is missing. A 403 error means the file was found but the server refuses to serve it. That distinction matters: a 404 needs the file restored, while a 403 needs the block removed. Do not re-upload images for a 403 error until the block is fixed, or the new uploads may fail the same way.
Can a CDN cause a 403 error on images that work without it?
Yes. A CDN rule, a cached 403 response, or a CDN configuration that blocks a file type can refuse images that load fine directly from the server. Purge the CDN cache, check the CDN rules, and test in bypass mode to confirm. Fix 7 walks through those checks.
Why did the error appear after I changed my domain name?
Because hotlink protection, CDN rules, and firewall lists may still name the old domain. Requests from the new domain look like outsiders and get blocked. Update the allowed lists with the new domain, and update the site address in Settings, then General. Fixes 6 and 8 cover both updates.
Should I re-upload all my images to fix this?
No, not before the block is found. Re-uploading while the block is active produces new files that fail the same way, and it creates duplicates in the Media Library. Find and remove the block first, then re-upload only the images that are genuinely missing.
Conclusion
When wordpress media files returning 403 error turns your pictures into empty boxes, the fix is almost always the permissions, a rule in .htaccess, a security plugin, or a firewall — not deleted images. Check the address and clear the cache first, then fix the permissions and the rules, then check the CDN and the HTTPS setup, and finally ask your host to check ownership and the server firewall. Finish with a simple test: open several image addresses directly and watch them all load. That visible row of working images is the proof that counts. Find the block, remove it, test it, and let your pictures show again.
