Website Not Working on iPhone or Safari (Causes and Fixes)

Your website is not working on iPhone or Safari — layouts break, buttons do nothing, forms will not submit, videos will not play, or logins keep failing — while the same site works fine in Chrome on a computer.

Common signs of this issue

• Your website is not working on iPhone or in Safari, but it works in Chrome or Edge on a computer.
• The layout is broken only on iPhones — overlapping text, a menu that will not open, or content cut off at the bottom of the screen.
• A form, checkout, or booking widget will not submit on iPhone, or submits but nothing arrives.
• Customers say they cannot stay logged in, or a login or payment step loops back to the start in Safari.
• Background or hero videos show a play button or a blank box on iPhone instead of playing.
• Some customers with older iPhones or iPads report problems while newer devices are fine.
• It works in Chrome on an iPhone just as badly as in Safari.

Safe checks you can do yourself

None of these require sharing passwords with anyone.

• Get specifics from whoever reported it: which device, which iOS version (Settings, then General, then About), which page, and what exactly happens. "Doesn't work on iPhone" covers dozens of different problems, and the iOS version alone often explains it.
• Know that on iPhone, Chrome and Firefox usually use the same engine as Safari (WebKit). If a site breaks in Safari on iPhone, it will usually break in every iPhone browser. That is why switching browsers on the phone rarely helps, and why testing in Chrome on your PC tells you little.
• Try it with content blockers off. Ad and tracking blockers in Safari can hide buttons, block forms, embedded maps, booking widgets, and chat tools. On the iPhone, tap the page settings icon in the address bar and choose to turn content blockers off temporarily, then reload.
• Test with Private Browsing and with Hide IP Address or iCloud Private Relay turned off (both in Settings, then Apps or Safari, depending on iOS version). Safari's tracking protection limits cookies from other sites, which can break logins, payment pop-ups, and forms embedded from another service in an iframe. Private Relay can also trigger firewalls or location blocks.
• For a broken layout, look for the classic Safari trouble spots: sections set to full screen height that get cut off by the address bar, sticky headers that jump, and newer CSS features that older iOS versions do not support. Note whether the problem appears on the newest iOS or only older ones — that points to either a bug or an old-device compatibility gap.
• For videos that will not play automatically, check the video is set to muted and inline. iPhones only autoplay video that has no sound and is allowed to play inline, and they may still block it in Low Power Mode. This is a browser rule, not a fault in your site.
• For forms, check date and time fields in particular. Safari displays these with its own picker, and some form plugins or validation scripts mishandle them. Also check anti-spam checks such as reCAPTCHA or Turnstile, which can fail with strict privacy settings — see form unable to submit.
• Test without owning a Mac. Borrow any iPhone or iPad for a real-world check. For deeper testing, paid cloud services such as BrowserStack or LambdaTest let you open your site on real iPhones from a Windows PC, and many offer short free trials. Detailed Safari developer tools do require a Mac, so for a stubborn bug a developer with one is useful.
• Update WordPress, the theme, and plugins if they are behind — but on a staging copy or after a backup. Many Safari fixes arrive as ordinary theme and plugin updates.

What this usually means

Safari is not "broken", but it is different. Apple's WebKit engine sometimes implements features later or slightly differently than Chrome, and it takes a firmer line on privacy — limiting third-party cookies, tracking, and autoplaying video. A site built and checked only in Chrome can look perfect on the developer's screen and misbehave on the phones many of your customers carry. Because nearly every browser on iPhone is WebKit underneath (Apple has allowed other engines only in limited cases, such as in the EU), an iPhone problem is usually a WebKit problem, not a Safari settings problem.

The most common causes are: layout code that relies on something Safari handles differently, such as full-height sections or newer CSS; JavaScript that errors out in Safari and stops menus, sliders, or forms from working; privacy features blocking cookies needed by logins, payment windows, or embedded forms; and older iPhones stuck on an older iOS version that cannot run newer code at all. Content blockers installed by the visitor are a less common but very real cause.

This matters because iPhone users are a large share of mobile visitors for many small businesses, and they tend to leave quietly rather than report a problem. A contact form or checkout that fails only on iPhone can cut leads without any error showing up on your end. If the site also looks off in other browsers, site looks different across browsers covers the wider picture; if the whole mobile layout is poor, start with website looks bad on mobile.

What not to do

• Don't tell customers to just use Chrome on their iPhone. It usually uses the same engine and will behave the same way.
• Don't assume it is fine because it works on your Android phone or your laptop. Test on an actual iPhone or a real-device testing service.
• Don't ignore reports from customers with older iPhones. They are still customers, and older iOS versions can be a large group.
• Don't paste random Safari fixes from forums into your theme files on the live site. A small CSS or code mistake can break every device.
• Don't switch off your spam protection entirely to fix a Safari form problem. Fix or replace the check instead.
• Don't update every plugin and theme at once on the live site hoping one of them fixes Safari. Back up and go one at a time.

When to get help

If the problem involves logins, checkout, payments, or a form that loses leads, it is worth getting help quickly — every day it stays broken on iPhone is customers turned away without a word. Safari bugs also tend to need real-device testing and browser developer tools to pin down; someone experienced can reproduce the issue, read the actual error, and fix the specific line of CSS or script rather than swapping plugins until something changes. That also avoids fixes that repair iPhone but break Android or desktop.

Glenn, who runs WebsiteSelfHelp, tracks down iPhone- and Safari-only problems on small business websites. Send a short description of the page, the device, and what goes wrong, and you will get an honest answer on what is causing it and what fixing it involves — you will not need to hand over passwords to start.

Frequently asked questions

Related free guides