Shopify Theme Not Working? Common Issues and How to Fix Them

A Shopify theme stops working for a small set of reasons: a Liquid code error, an app conflict, a stale browser cache, a theme update that broke a customization, or a setting in the wrong place. The fix depends on which one. This post walks through the 10 most common theme failures we see, in the order you should check them, with the exact path through the admin to fix each.

We detect themes and apps on real Shopify stores every day, which means we see which apps most commonly cause theme conflicts and which themes break the most often after updates. The diagnostic flow below is built from that pattern, not from theory. Start at the top of the list and stop at the first match.

What Do I Try First When My Shopify Theme Stops Working?

Try the cache and browser fix before anything else. Clear the browser cache, open the storefront in an incognito window, and check the site on a phone on cellular data. About 30% of “my theme is broken” reports are stale local cache that resolve on a clean session. If the issue is still there in incognito and on mobile, it is a real theme problem and the sections below cover where to go next.

If the issue passed the cache test, the next question is whether the theme editor itself loads. If the editor opens but the storefront is broken, the published theme has a problem (skip to the relevant H2 below). If the editor will not load, the problem is upstream of the storefront, and the next section is where to start.

Why Won’t the Shopify Theme Editor Load?

The editor fails to load when there is invalid Liquid code in the theme, a network or CDN issue on Shopify’s side, or a browser/extension blocking the editor’s JavaScript. Liquid errors are the most common cause and Shopify’s code editor highlights them in red on the file that broke.

Fix steps in order:

1. Try a different browser. Chrome, Safari, and Firefox handle Shopify’s editor slightly differently. If the editor loads in one but not another, the failure is browser-side and the production theme is fine.
2. Open Shopify’s code editor. Online Store > Themes > the broken theme > Edit code. If there is a Liquid error, the file with the bad code shows a red error indicator. Open it and look for the syntax issue (most often an unclosed `{% if %}` or missing `{% endfor %}`).
3. Roll back the file. In the code editor, click “Older versions” on the broken file. Shopify keeps the last several Liquid versions. Pick the most recent working one and restore.
4. Check the Shopify status page at status.shopify.com. If editor failures are widespread, you are not the only one and waiting is the fix.

If the editor still will not load after these steps, the theme has structural damage that needs a developer. Skip to the “When to Call a Shopify Expert” section at the bottom.

Why Aren’t My Theme Changes Showing on the Live Site?

Theme changes do not appear on the live site for three reasons: you edited an unpublished duplicate instead of the published theme, the CDN is serving a cached version, or the change was made on a different theme template than the one rendering for that page type. The fix is identifying which.

Check in this order:

• Confirm you edited the published theme. Online Store > Themes > the theme with the green “Current theme” badge is what visitors see. If you edited a different theme, your changes are live in that copy but not on the storefront.
• Check the right template. If a product page change is not showing, you may have edited the default `product` template when that product uses `product.custom-variant` template. Open the product in admin > Online store > Theme template and check what is assigned.
• Force-clear the CDN. Shopify’s CDN caches static assets for several minutes. Add `?test=1` to your URL to bust the cache, or wait 5-10 minutes.
• Check market-specific content. If you sell into multiple markets, content is per-market in the editor. Switch the Market dropdown at the top of the editor to see what is rendering for which audience.

Why Did a Theme Update Break My Customizations?

A theme update overwrites theme files with the new version. Any custom Liquid, CSS, or JavaScript edits you made directly to the theme files are replaced. Settings and section configurations are preserved (because they live in `settings_data.json`), but anything you edited in the code editor is gone.

The recovery options depend on what you had backed up:

1. If you have a duplicate from before the update, that copy has your customizations. Publish it and re-apply the update to it manually, or revert and apply customizations to the new version.
2. If you used Shopify’s “Older versions” Liquid history, open the file that broke in the code editor, click “Older versions”, and restore. This only works for Liquid files, NOT for CSS or JavaScript.
3. If you have neither, the customizations are gone and you need to rebuild them. This is the case that should never happen and the prevention section below covers how to avoid it.

The takeaway: never apply a theme update directly to the published theme. Duplicate the published theme, apply the update to the duplicate, test it, then publish. Out of the Sandbox calls this a “duplication approach” and it eliminates the single biggest cause of theme emergencies.

Why Does the Theme Look Different on Mobile vs Desktop?

Themes are responsive, which means sections move, resize, or change layout on mobile to fit the smaller screen. The most common “broken” mobile reports are not broken at all, just the responsive layout doing its job. Use the theme editor’s screen-size toggle (the device icons at the top) to preview each size before publishing.

Real mobile-specific issues:

• Image grids misaligned. Products with inconsistent aspect ratios stack unevenly on mobile. Use 2048×2048 square product images for the cleanest grid.
• Text overlaying behind images. Some themes move text overlays below the image on mobile for readability. If a text block disappears on mobile, check the section’s mobile-specific settings.
• Sticky elements covering content. Sticky headers and add-to-cart bars eat space on small screens. Toggle them off for mobile in the section settings if they cover important content.

Why Are Products or Collections Missing from the Storefront?

Products and collections do not appear on the storefront when their status is wrong, the sales channel is wrong, or a collection filter is excluding them. Each has a specific fix.

• Product is missing. Open the product in admin. Status must be Active. Sales channels must include “Online Store”. If either is wrong, fix it and reload the storefront after the CDN clears.
• Collection is empty. Check the collection’s “Filter collection with tags” field. A leftover tag filter excludes everything that does not match. Remove the filter or fix the tags.
• Collection is not in the menu. Navigation > the relevant menu > add the collection. Collections only show in navigation if you add them.
• Variants missing. Each variant has its own active/inactive toggle. If a size is missing, check the product’s Variants tab.

Why Am I Getting a Liquid Error in My Theme?

Liquid errors show up when there is a syntax problem in a `.liquid` file: an unclosed tag, a malformed expression, or a reference to a variable that does not exist. The code editor shows the file with a red error indicator and the error message tells you the line number.

The common causes:

• Unclosed conditional. A `{% if condition %}` without a matching `{% endif %}`. Every `if`, `for`, and `case` needs its closer.
• Malformed Liquid expression. `{{ product.title }` with one closing brace instead of two. The editor highlights this in red.
• Wrong filter syntax. `{{ product.title | upper }}` works, `{{ product.title | upper: ‘arg’ }}` works for filters that take args, but bad arg structure fails.
• Reference to nonexistent variable. Pasting code from a different theme often references variables that do not exist in yours. The fix is replacing the variable with one from your theme’s variable set.

If the Liquid error is in a section template, the section disappears from the page but the rest of the site keeps working. If it is in `theme.liquid` (the layout file), the whole storefront breaks. The fix in both cases is the same: open the file, fix the syntax, save. Use the “Older versions” history if you cannot find the error.

Did an App Conflict Break My Theme?

App conflicts are the second-most-common theme failure. Apps inject code into the theme to add functionality (reviews, popups, currency converters, page builders), and that injected code can clash with the theme’s own code or with another app’s. The symptoms vary: a section disappears, the cart will not open, variant selectors stop working, the checkout button does nothing.

Diagnostic flow:

1. Identify recently installed or updated apps. Apps > sort by date. If anything was installed or updated in the last 7 days, that app is suspect.
2. Disable apps one at a time. Disable the most-recently-changed app first. Test the broken behavior. If it fixes, that app is the cause. If not, re-enable it and try the next.
3. Check for leftover code. When you uninstall an app, sometimes the code it injected into the theme remains. Open the code editor and search for the app’s name or signature script tags. Remove them.
4. Contact the app developer. If the app is the cause, the app developer needs to ship a fix. Most respond to support tickets within a day.

We see app conflicts most often on stores running 8+ apps, especially when two apps target the same section (e.g., two cart-drawer apps). Audit your app stack: if an app’s job overlaps another, remove one.

Why Is My Theme Suddenly Slow?

Themes get slower over time as you add apps, install image-heavy sections, and accumulate custom code. Sudden slowness usually has a specific recent cause: an app that loads heavy scripts, a hero image that did not get compressed, or a customization that loaded a synchronous library.

The diagnostic checklist:

• Run PageSpeed Insights on the slow page. The biggest contributor by ms is usually the culprit.
• Check your app stack. Apps installed in the last month? Disable one at a time and re-test.
• Check the largest images on the page. Anything over 200KB is too big. Compress and re-upload.
• Check for synchronous third-party scripts. Anything loaded with `