How to Fix Website Images Not Showing on iPad

Images that do not appear on an iPad are usually caused by a content blocker, a network or VPN filter, disabled JavaScript, stale Safari website data, or a problem limited to the website itself. Start by checking whether the problem affects one page, one site, or many sites. Then change one setting at a time so you can identify the cause.

1. Identify whether the problem is local or site-specific

Open several pages on the same website, then try two unrelated websites that normally contain images.

One image or one page: the image URL, page code, or that site’s delivery service may be failing.
Every page on one site: investigate the site’s cookies, permissions, content blockers, VPN, or Private Relay.
Many sites: focus on Safari settings, your network, VPN or filtering software, and iPadOS.

Test the affected site on another Wi-Fi network, or on cellular data if your iPad supports it. Apple recommends trying another network for Safari loading problems. If images work elsewhere, the original network or its filtering configuration is the strongest lead. A VPN can also cause some websites to block content.

2. Temporarily disable Safari content blockers

Apple describes content blockers as third-party apps and extensions that can block “cookies, images, resources, pop-ups and other content.” That means a blocker can remove an image request even when the website is working.

Open Settings.
Tap Apps > Safari > Extensions.
Turn off each listed content blocker temporarily.
Return to Safari and reload the page.

If images return, re-enable blockers one at a time to find the one responsible. Then adjust its site rules or contact its developer. Do not install another blocker as a fix; blockers themselves can prevent images from loading. See Apple’s Safari history, cache, cookies, and content-blocker guidance.

3. Check JavaScript

Many modern sites insert images after JavaScript runs. A disabled JavaScript setting can therefore leave empty spaces or image placeholders.

Open Settings > Apps > Safari.
Tap Advanced.
Turn on JavaScript.
Return to Safari and reload the page.

Apple lists this as a general Safari loading step, not a guarantee for every image-only failure. If JavaScript was already enabled, leave it enabled and continue with the next test.

4. Test VPN, filtering software, and Private Relay

VPNs, DNS filters, security apps, and network firewalls can block image hosts, tracking domains used by image CDNs, or requests that look unusual.

VPN and security software

Temporarily disconnect the VPN or pause web filtering, reload the page, and compare the result. Apple says some apps or websites might block content when a VPN is turned on. Re-enable the VPN after the test if it was not the cause.

iCloud Private Relay

If only one website is affected, check whether iCloud Private Relay is enabled. Apple recommends temporarily turning it off in iCloud settings when a site-specific Safari problem continues. Test once, then restore the privacy feature if it made no difference.

Change only one of these variables at a time. Otherwise you will not know which setting changed the result.

5. Restart the iPad and reload without stale page state

Restart the iPad, open Safari again, and load the page from a new tab. A fresh process can clear a transient Safari or network state.

If the page still fails, clear Safari website data:

Open Settings > Apps > Safari.
Tap Clear History and Website Data.
Confirm the action.

Clearing website data also removes browsing history, cookies, and permissions granted to websites. You may need to sign in again and revisit permissions. Apple documents these effects in its Safari data-clearing instructions.

6. Check the page and image itself

When the failure affects one page or one website, try these quick checks:

Open the image URL directly if the page provides one.
Reload using a private Safari tab. If it works there, stored cookies, permissions, or extensions are likely involved.
Try Request Desktop Website from Safari’s page menu. A desktop and mobile layout can request different image files.
Look for a broken-image icon, an empty box, or a spinner. These clues help the website owner distinguish a missing file from a blocked request.
Ask whether the site recently changed its image host, CDN, login flow, or consent banner.

Do not assume that a blank image proves the iPad screen or camera is defective. Website images are downloaded resources, so the failure can occur in the page, the network, Safari, or the image server.

7. Use the symptom to choose the next test

Symptom	Most useful next test	What the result means
Images missing on every site	Try another network, then disable VPN/filtering	A network or device-wide setting is likely involved
Images missing only with one Wi-Fi network	Use cellular data or another Wi-Fi network	Investigate the original router, DNS, or filter
Images missing only on one site	Disable content blockers and test Private Relay	The site’s resources or privacy configuration may conflict
Text loads but images remain blank	Check content blockers and JavaScript	Image requests or client-side rendering may be blocked
Images appear after clearing data	Sign in again and restore permissions carefully	Stale cookies, cache, or permissions were involved

8. Troubleshooting common errors

Only ads or tracking images are missing

A content blocker may be working as designed. Disable it briefly to confirm, then allow only the site’s required resources if the blocker supports per-site rules.

Images show on cellular but not Wi-Fi

Check the Wi-Fi network’s DNS filtering, parental controls, firewall, or captive portal. Contact the network administrator if you cannot change those settings.

Images show in another browser

Compare Safari extensions, JavaScript, website data, and Private Relay. The other browser’s success points to a Safari configuration difference, not necessarily a problem with the website.

Clear the site’s website data, sign in again, and verify that cookies are not being blocked. Some sites use authenticated image URLs that require the same session as the page.

Nothing changes after every Safari step

Try another network and another device. If the site fails everywhere, contact its developer. Apple recommends contacting the website developer when a problem continues to affect only a particular website or webpage after its general steps.

9. When to contact the website developer

Contact the site owner when other websites work normally and the affected site still has missing images after you have tested blockers, JavaScript, VPN or Private Relay, another network, and cleared website data.

Include:

The exact page URL and the image URL, if visible.
Your iPad model and iPadOS version.
Whether the problem occurs in private browsing, another browser, another network, or cellular data.
Whether disabling content blockers, VPN, or Private Relay changed anything.
A screenshot showing the missing image or placeholder.

This information lets the developer investigate its image host, permissions, responsive markup, authentication, or CDN configuration.

10. Capture a comparison screenshot without configuring a browser

If you maintain the website and need to see what a page returns outside the iPad, ScreenshotNeo can capture the URL through its screenshot API. This gives you a server-side image to compare with the iPad result; it does not change Safari settings or repair a broken image server.

Or skip the browser setup

ScreenshotNeo accepts one GET request and returns PNG, JPEG, WebP, or PDF. Its capture can remove cookie-consent banners, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and the response identifies the page verdict and billing status in headers. An MCP server lets Claude, Cursor, and other MCP clients use screenshot, page-info, and PDF tools. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.

See the ScreenshotNeo API documentation for all options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Create a free ScreenshotNeo account to get 1,000 screenshots a month with no card.

11. Performance, reliability, and privacy considerations

Change one variable at a time: this preserves a useful diagnosis.
Prefer a second network test before resetting settings: it is quick and does not erase data.
Expect sign-ins after clearing data: cookies and site permissions are removed.
Restore privacy controls: turn VPN, Private Relay, and content blockers back on after testing unless the site owner requires a different configuration.
For repeated developer checks: cache a known-good screenshot and compare it with a current capture. ScreenshotNeo supports a TTL you choose, async jobs, signed webhooks, bulk capture, and usage reporting; select these according to how often you need checks and how many URLs you monitor.

12. FAQ

Why do pictures load on my iPhone but not my iPad?

The devices can have different Safari extensions, website data, VPN or Private Relay state, network paths, or iPadOS settings. Compare those variables one at a time.

Will restarting delete my photos or files?

No. Restarting only reboots the iPad. Clearing Safari website data is the step that removes browser history, cookies, and site permissions.

Should I reset all iPad settings?

Not as an initial fix. Identify whether the issue is site-specific, network-specific, or Safari-wide first. A website developer or Apple Support can advise on broader resets if the narrower tests fail.

Can a website owner fix images that fail only on iPad?

Yes, if the cause is in its responsive markup, image format, CDN, authentication, consent flow, or browser-specific code. Provide the developer with the URL, device details, network comparison, and screenshot evidence.