Troubleshooting
WordPress Not Working on Safari: Causes and How to Fix It

Short answer
WordPress usually breaks in Safari because of old cached files, mixed content or SSL errors, blocked cookies, content blockers, or features older Safari versions cannot run. Test in a private window, clear your site's data in Safari, then check the Web Inspector console for errors.
Key takeaways
- Test in a private Safari window first to rule out cached files and cookies.
- Remove only your site's data under Manage Website Data in Safari settings.
- Safari's Web Inspector console shows the script or file that is failing.
- Mixed content and certificate problems often break styles in Safari.
- Login loops usually come from cookies or a www and non-www mismatch.
- Background videos must be muted and set to play inline to autoplay.
Why is WordPress not working on Safari?
WordPress usually fails on Safari because of stale cached files, mixed content or SSL problems, blocked cookies, content blockers, or code that an older Safari version cannot run.
The problem can show up in two places. Visitors may see a broken front end, or you may be unable to log in or use the editor in Safari while Chrome works fine.
Safari uses the WebKit engine, while Chrome and Edge use Chromium. Most sites look the same in both, but WebKit handles some cookies, scripts, video and image formats differently.
The good news is that the cause is almost always something you can find with Safari's own developer tools. Start with the quick checks below before you change anything on the server.
How do you confirm the problem is Safari-specific?
Open the same page in a Safari private window, then in Chrome or Firefox, and on another Apple device; if only regular Safari fails, the cause is local to that browser.
Use this quick test order:
- Private window in Safari. Private browsing ignores most saved cookies and cached files. If the page works here, clear Safari's cache and cookies for your site.
- Another browser on the same Mac. If Chrome works but private Safari still fails, the cause is likely WebKit behavior or a Safari setting.
- Another Apple device. Test an iPhone or iPad. If every Safari fails, the problem is on your site.
- Logged out. Compare logged-in and logged-out views. Admin-only scripts sometimes break only for you.
Write down exactly what you see: a blank page, a security warning, a login loop, missing images or a layout that falls apart. Each points to a different cause.
How do you clear Safari's cache and cookies for your site?
On Mac, open Safari Settings, go to Privacy, choose Manage Website Data, remove your site, then reload; on iPhone, use the Safari section of the Settings app.
Old CSS and JavaScript files are the most common cause of a broken layout in one browser. Clearing only your own site's data avoids logging you out everywhere else.
On a Mac:
- Open Safari > Settings (called Preferences on older versions).
- Go to the Privacy tab and click Manage Website Data.
- Search for your domain, select it and click Remove.
- Close the window and reload the page.
On iPhone or iPad, open the Settings app, find Safari (inside Apps on newer iOS versions), then use Advanced > Website Data to remove your site.
Also clear any cache on the site side. Purge your caching plugin and CDN so Safari does not download the old files again. Our guide on how to clear cache in WordPress covers the common plugins and hosts.
How do you find errors with Safari's Web Inspector?
Turn on Safari's developer features under Settings > Advanced, then right-click the page, choose Inspect Element, and read the Console tab for red errors.
- Open Safari > Settings > Advanced.
- Tick Show features for web developers (older versions say Show Develop menu in menu bar).
- Load the broken page, right-click and choose Inspect Element.
- Open the Console tab and reload the page.
Look for messages that name a file. A JavaScript error in one plugin's file can stop every script after it, which breaks menus, sliders and forms.
The Network tab helps too. Files shown in red failed to load, often because of a wrong URL, a blocked request or an SSL issue.
If an error points to a plugin file, see our guide to fixing a plugin conflict to confirm which plugin is responsible.
Can mixed content or SSL issues break WordPress in Safari?
Yes, Safari blocks insecure HTTP files on HTTPS pages and shows strong warnings for certificate problems, which can remove styles and scripts or stop the page loading.
Mixed content means the page loads over HTTPS but some images, scripts or stylesheets still use HTTP. Browsers block many of those files to protect visitors. MDN's mixed content guide explains which types are blocked.
Common signs include a missing stylesheet, a page with no layout, or the padlock icon showing a warning.
To fix it:
- Make sure both URL fields under Settings > General use https.
- Search and replace old http:// links in the database.
- Check theme options and page builder settings for hardcoded HTTP image URLs.
Our guide to fixing mixed content warnings has the full process. If Safari says the connection is not private, the certificate itself may be expired or not cover the www version of the domain.
Why can't you log in to WordPress on Safari?
Login problems on Safari are usually caused by blocked or stale cookies, a mismatch between www and non-www addresses, or cross-site cookie limits in embedded content.
WordPress uses cookies to keep you logged in. If Safari cannot store or send them, the login page simply reloads.
Check these causes:
- Old cookies. Remove your site's website data, as shown above, and try again.
- Domain mismatch. If your site address uses www but you log in on the non-www address, the cookie may not match. Keep both URL fields consistent.
- Embedded logins. Safari limits cookies inside iframes from other domains. WebKit describes these rules in its tracking prevention documentation.
- Mixed HTTP and HTTPS. Secure cookies are not sent over plain HTTP.
If the login form keeps refreshing, our guide on fixing the login page refreshing and redirecting walks through every fix.
Can an old Safari version cause problems?
Yes, older Safari versions may not support newer JavaScript, CSS features or image formats, so parts of a modern theme, plugin or the block editor can fail.
Safari updates come with macOS and iOS updates. Visitors on old iPhones or Macs that no longer get updates may run Safari versions that are several years old.
Features that sometimes cause trouble include newer CSS layout rules, some image formats like AVIF on older versions, and modern JavaScript syntax.
Check support for a specific feature on Can I use. If a plugin relies on a feature your visitors' Safari lacks, ask the developer for a fallback or choose a different plugin.
For your own admin work, keep Safari up to date. WordPress supports the latest versions of major browsers, and the block editor may not work well in outdated ones.
Do extensions and content blockers break WordPress in Safari?
Yes, Safari content blockers and privacy extensions can block scripts, fonts, embeds and forms, especially files with names that look like ads or tracking.
Turn off content blockers for your site and reload. On Mac, choose Safari > Settings for This Website and untick Enable content blockers. On iPhone, tap the page menu in the address bar to find similar options.
If the site works with blockers off, rename or self-host the blocked file, or accept that some visitors use blockers and make sure the core page still works without the blocked script.
iCloud Private Relay can also cause issues. It changes the visitor's IP address, which can trigger country blocks or rate limits in security plugins and firewalls.
Why do videos or animations not work in Safari?
Safari only autoplays video when it is muted and set to play inline, and it handles some animation and video formats differently from Chrome.
If a background video does not play on iPhone, check that the video is muted, has the playsinline setting, and uses a widely supported format such as MP4 with H.264.
Page builders usually have Mute and Play on mobile options for background video. Turn on mute and test again. Heavy scroll animations can also stutter on older devices, so consider disabling them on mobile.
What is the quickest checklist for Safari problems?
Work from the visitor's side to the server: clear Safari data, disable blockers, check the console, fix SSL and mixed content, then test plugins and theme.
| Symptom | Likely cause | First fix |
|---|---|---|
| Layout broken only in Safari | Cached CSS or JS | Clear site data and plugin cache |
| Not secure warning | Certificate or mixed content | Check SSL and HTTPS URLs |
| Login page reloads | Cookies or www mismatch | Remove site data, match URL fields |
| Menu or slider does nothing | JavaScript error | Read Console, test plugins |
| Background video does not play | Autoplay rules | Mute video and enable inline play |
| Only old iPhones fail | Unsupported feature | Check support, add fallback |
If nothing on this list helps, turn on WordPress debugging to catch PHP errors that only appear under certain conditions. The WordPress debugging documentation shows the settings, and our guide on enabling debug mode explains them step by step.
Frequently asked questions
Why does my WordPress site look different in Safari than in Chrome?
Safari uses the WebKit engine, which handles some CSS, fonts and image formats differently from Chromium. Cached files are the most common cause, so clear site data first. If the difference remains, check the Console for errors and test whether a theme or plugin uses an unsupported feature.
Why can I not log in to WordPress admin on Safari?
Safari may be holding old cookies or refusing cookies that do not match the site address. Remove your site's website data, make sure the WordPress and Site Address fields use the same www and https form, and try again in a private window.
Does the WordPress block editor work in Safari?
Yes, the block editor supports current versions of Safari. Problems usually come from outdated Safari versions, content blockers or plugin conflicts. Update macOS or iOS, disable extensions for your site and test with other plugins turned off.
How do I clear Safari cache for just one website?
On a Mac, open Safari Settings, go to Privacy, click Manage Website Data, search for the domain and remove it. On iPhone or iPad, open the Settings app, find Safari, then use Advanced and Website Data to remove the site.
Why does my background video not play on iPhone Safari?
Safari only autoplays video that is muted and allowed to play inline. Turn on the mute and play-on-mobile options in your page builder, use an MP4 file with H.264 video, and check that Low Power Mode is not stopping playback.
Sources
- Tracking Prevention in WebKit WebKit
- Mixed content MDN Web Docs
- Can I use caniuse.com
- Debugging in WordPress WordPress Developer Resources
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


