// Troubleshooting · Checkout
Why is your Shopify checkout blank?
Last updated 28 September 2026.
A blank or white checkout is almost always something between the customer's browser and Shopify's checkout, not Shopify itself: a browser extension or content blocker, a stale cache, a proxy or firewall in front of your domain, or a legacy checkout customisation that errors before the page paints. Rule out the browser first (a private window on a second device — thirty seconds), then Shopify's status page (ten seconds), then your domain: if checkout works at your-store.myshopify.com and not on your custom domain, it's DNS, a proxy or SSL. Only then look at checkout apps, custom pixels and any checkout.liquid customisation you still carry.
A blank checkout is frightening in a way a slow page isn't: the customer has decided to buy, and the store answers with nothing. It is also, mercifully, one of the easier symptoms to run down — because Shopify's checkout is a heavy JavaScript application served by Shopify on your primary domain, and a white page nearly always means one specific script was blocked, cached wrongly or failed before the page could paint. The job is to find where it was blocked.

The 60-second order of checks
- Browser, thirty seconds. Open the checkout in a private window, then on a second device over mobile data. If either works, the problem is in the first browser: an extension, a content blocker, or a stale cache.
- Shopify, ten seconds. shopifystatus.com — an incident on Checkout means it's the platform. Change nothing; wait.
- The two-URL test, twenty seconds. Add a product at
your-store.myshopify.com(Settings → Domains lists it) and click Checkout. Works there but not on your domain? It's your domain: DNS, a proxy in front of it, or SSL. - Then, and only then, customisations. Disable checkout apps, custom pixels and any legacy checkout.liquid customisation one at a time, re-testing after each.
A blank Shopify checkout is nearly always something between the browser and Shopify — an extension, a cache, a proxy, or a customisation that errored before paint — and the private-window test on a second device settles the first question in thirty seconds.¶
Cause 1: the browser
Content blockers and privacy extensions can block the scripts the checkout needs to render; privacy-first browsers ship some of that blocking by default; a very old browser can fail to run the checkout at all; and a cached service worker or stale asset can serve a broken shell. Signature: works in a private window or on another device. Fix: for you, clear the cache and disable extensions one at a time. For customers who report it, ask which browser and whether a private window works — and if a specific blocker is the cause, there is nothing on your store to change; the checkout is Shopify's.
Cause 2: something in front of your domain
Shopify's domain setup expects your DNS records to point directly at Shopify — the A record and the www CNAME in Shopify's domain documentation. A proxy in front (Cloudflare's orange-cloud proxy is the common one, but any CDN or security layer counts) can interfere with the SSL handshake, and checkout is the page that suffers first because it insists on a clean secure connection. Corporate firewalls and some VPNs do the same to the customers behind them. Signature: the .myshopify.com checkout works; your domain's doesn't. Fix: set the records to DNS-only, then give the certificate time to re-issue.
Cause 3: a checkout customisation
Modern checkout customisations — checkout UI extensions and custom pixels — run in Shopify's sandbox, so a broken one is far less likely to blank the page than it used to be. Two things still can: a legacy checkout.liquid customisation on a Shopify Plus store that hasn't been migrated, and a script an app injected with permission you granted long ago. Signature: blank for everyone, on every domain, starting when something changed. Fix: in Checkout settings and your app list, disable the most recent change first and re-test. If checkout paints again, you've found it. Our app-code scanner lists every third-party script your storefront loads, which shortens the list.
Cause 4: Shopify
Rare, loud, short — and nothing you can fix. If the status page shows an incident on Checkout, the right move is the hardest one: change nothing. Mid-outage "fixes" are how a one-hour platform problem becomes a self-inflicted three-day one.
Cause 5: domain and SSL
After a domain change or a DNS edit, Shopify's documentation gives the SSL certificate up to 48 hours to issue. In that window the storefront may load while the checkout — which requires the certificate — does not. Signature: a certificate warning, or a checkout that fails only on the new domain. Fix: confirm the records, then wait; there is no way to hurry a certificate.
If the checkout renders at your-store.myshopify.com and not on your custom domain, the fault is the domain — DNS, a proxy in front of it, or an SSL certificate still issuing — and no theme or app change will fix it.¶
Frequently asked questions
Why is my Shopify checkout page blank or white?
Checkout is blank for customers but works for me. Why?
Does a Cloudflare proxy break Shopify checkout?
How do I catch a blank checkout before customers do?
Keep reading: Is Shopify down, or is it just my store? · Did a theme update break my checkout? · Add-to-cart not working? · The Watch check
// The click that matters most
Does your checkout
load tonight?
Bilby clicks Checkout from a clean browser every night, desktop and mobile, and screenshots anything that doesn't render. One free scan, no signup.
Thin or missing product content is the other half of this problem, and it is the half search engines and AI assistants see. Navaal: AI SEO, AEO & GEO audits a Shopify catalogue for it free, and writes what is missing for review.