GLOBAL BRIDGE LABS
← All posts/Website Development

Website not working on iPhone? The usual Safari causes

Website not working on iPhone but fine elsewhere? Eight Safari behaviours that break forms, video and layouts, how to spot each and what the fix is.

By Hojitha Weerasinghe, Co-founder / DirectorPublished 7 min read
Website not working on iPhone: key takeaways infographic by Global Bridge Labs
Key takeaways from this article. Share it with the link and credit Global Bridge Labs.
On this page

Key takeaways

A website not working on iPhone, while behaving on Android and on a laptop, is nearly always running into a known Safari behaviour. iPhones account for close to half of UK mobile web traffic, so 'it works in Chrome' leaves a great many visitors with a broken page. Eight causes explain most cases, and each has a standard fix.

  • 47% of UK mobile web traffic is on iOS (StatCounter, September 2026).
  • Safari zooms the page when a form field's text is under 16px.
  • Full-height sections are cut off by Safari's moving toolbar.
  • Video will not autoplay unless it is muted and set to play inline.

Site misbehaving on iPhones? Send us the page on WhatsApp and we will reproduce it on real devices.

Chat on WhatsApp →

Why do sites break on iPhone specifically?

Sites break on iPhone because Safari, built on Apple's WebKit engine, handles some things differently from Chrome, and because many developers and owners test only in Chrome. Browsers on iPhone have historically all used WebKit underneath, so a Safari quirk usually appears in Chrome and other browsers on the same phone as well.

There is a second factor. Safari is updated with iOS, not separately. A visitor on a phone that no longer receives iOS updates is using an older Safari that may lack features a new site relies on. That group is small but not negligible.

Which eight causes come up most?

These eight account for most 'it is broken on my iPhone' reports on business sites. Match the symptom, then pass the cause to your developer.

  • Page zooms in when a form field is tapped: field text is smaller than 16px.
  • Bottom of a full-screen section or button is hidden: the layout uses a fixed viewport height and Safari's toolbar covers part of it.
  • Video shows a play button instead of playing: it is not muted, or not set to play inline.
  • A fixed bar or button jumps or vanishes when the keyboard opens.
  • Hover effects stick after a tap, or menus that rely on hover will not open.
  • Numbers such as reference codes turn into blue phone links.
  • Date and select fields look or behave differently from the design.
  • A new layout feature is unsupported on an older iOS version.

How are the common ones fixed?

Each has an established remedy, and none requires a redesign. Most are a line or two of CSS or an attribute on an element. The skill is in recognising the cause, which is why a clear description of the symptom saves time.

  • Form zoom: set input, select and textarea text to at least 16px. Do not disable zoom.
  • Cut-off sections: use dynamic viewport units, which account for the toolbar.
  • Video: add muted and playsinline, and provide a poster image.
  • Fixed bars and the keyboard: avoid fixed elements inside forms, or hide the bar while typing.
  • Hover: make every hover-dependent feature work on tap.
  • Number detection: disable automatic phone number detection and mark up real numbers as links.
  • Older iOS: provide a sensible fallback layout for unsupported features.

Want the cause identified and fixed without a rebuild? Message us on WhatsApp.

Chat on WhatsApp →

How do you reproduce and report the problem?

Reproduce it on a real iPhone, in Safari, and record exactly what you did. A developer can fix in minutes what they can see, and may spend hours guessing at 'the form does not work'. If you do not own an iPhone, borrow one. A laptop cannot stand in for it.

  • Note the iPhone model and iOS version (Settings, General, About).
  • Note the page address and the exact steps that lead to the problem.
  • Take a screenshot or a screen recording.
  • Try in a private tab, to rule out old cached files.
  • Try with content blockers and Low Power Mode off, since both change behaviour.
  • Check whether it also happens in Chrome on the same iPhone.

What about tracking and cookies on iPhone?

Safari limits tracking more strictly than most browsers. Its Intelligent Tracking Prevention blocks third-party cookies and shortens the life of some first-party ones. The site itself works normally, but analytics may treat a returning iPhone visitor as new, and advertising platforms may under-report conversions from iPhones.

This is a measurement issue, not a fault to fix. Be aware of it when comparing iPhone and Android figures, and rely on enquiry counts from your own inbox, phone log and customer conversations alongside the dashboards.

What does it cost, and how far back should you support?

Individual Safari fixes are small, often an hour or two each, and sit comfortably within an indicative £500 to £3,000 for mobile fixes on an existing site. The cost rises only when a component, such as a custom slider or a complex form, was built in a way that fundamentally depends on Chrome behaviour.

How far back to support is a trade-off. Supporting every old iPhone adds testing time for few visitors. Supporting only the newest excludes real customers. A reasonable policy is the current iOS version and the two before it, adjusted by what your own analytics shows under Tech details.

What does this look like in practice?

A pattern we see after a new site launches: enquiries from the contact form drop, and nobody knows why. The developer and the owner both use Android phones or test in Chrome on a laptop. On an iPhone, tapping the first field zooms the page, and the submit button ends up behind a fixed bar where it cannot be pressed.

Roughly half of mobile visitors have been unable to enquire for weeks. Two small style changes fix it. Global Bridge Labs (GBL) tests every form on a real iPhone before launch for this reason, and it is the single check we would ask any business to add.

Next step

Borrow an iPhone today and submit your own enquiry form in Safari. If it zooms, jumps or hides the button, you have found a fault that is costing you leads right now.

Message us on WhatsApp and we will test your site on current and older iPhones and report every Safari issue.

Chat on WhatsApp →

Sources and further reading

Frequently asked questions

Why does my website not work on iPhone?

Usually because of a Safari-specific behaviour the site was not tested for: form fields that trigger zoom, full-height sections cut off by the toolbar, video that will not autoplay, or fixed elements that move when the keyboard opens. Each has a standard fix once identified.

Why does my website look different on iPhone and Android?

iPhones use Apple's WebKit engine and Android phones mostly use Chrome's engine. They render form controls, fonts, viewport height and some layout features differently. A site tested in only one will often show small differences, and occasionally serious faults, in the other.

Why does my page zoom in when I tap a form field on iPhone?

Safari zooms when the text size inside the field is smaller than 16 pixels. Setting the font size of inputs, selects and text areas to 16 pixels or more prevents it. Avoid disabling zoom in the viewport tag, which harms accessibility.

Does Chrome on iPhone behave like Safari?

Largely, yes. Browsers on iPhone have historically used Apple's WebKit engine underneath, so most Safari quirks also appear in Chrome on the same device. Testing in Chrome on a laptop or an Android phone does not tell you how a site behaves on an iPhone.

Written by

Hojitha Weerasinghe
Hojitha Weerasinghe
Co-founder / Director

Global Bridge Labs (GBL) is a UK–Sri Lanka partner for social media, websites and BPO. Everything here comes from client delivery, not theory.

Share this article

Reading is good.
Fixing is better.

30 minutes with our team and you'll leave knowing which of the three problems to fix first.

Book a 30-Minute Consultation →
Keep reading