Reviewed November 8, 2026

Your Storefront Went Blank After an App Install: Find the Script

You installed an app, clicked save, and the storefront went white. The admin still works, the products are still there, and the storefront shows nothing. That combination points at one place: the theme's JavaScript, and almost always a script tag the app just added.

A blank storefront is not a data loss problem. It is a rendering problem, and rendering problems have a short list of causes. The most common is a script error in theme.liquid, and the fix is usually a removal, not a repair.

The one-script theory, tested in five minutes

Open the browser console on the blank page. A JavaScript error names the file and the line, and the file name usually names the app. If the console shows an error in a file from the app you just installed, you have the cause, and the fix is to remove that app's code from the theme.

The safer path is the duplicate. Duplicate the theme in the theme library, open the duplicate in the code editor, and remove the app's snippet from theme.liquid. Preview the duplicate. If the storefront renders, publish the duplicate and the store is back. The whole test takes five minutes, and it never touches the live theme.

If the console shows no error, the problem is a Liquid error instead. A Liquid error means the theme code itself is broken, usually a missing endif or a tag the app's installer mangled. Shopify shows Liquid errors in the theme editor, and the line number points at the break.

What apps actually inject, and where

Most apps add a snippet to theme.liquid, the file that loads on every page. That is why one bad script can blank the whole store instead of one page. A smaller number of apps add code to product or cart templates, which breaks only those pages, and the blank page tells you which template to check.

The old ScriptTag API is part of this story. Shopify is retiring script tags: they stopped working on the order status page in August 2026, cannot be created or updated after October 1, 2026, and stop running on storefronts on March 1, 2027. Apps that still use script tags are on borrowed time, and an app that breaks your storefront today may be one that never migrated to theme app extensions.

Roll back first, diagnose second

The theme library keeps every published version, and rolling back takes seconds. If the storefront is blank and customers are hitting it, roll back first and diagnose on the duplicate. A rollback is not giving up. It is the fastest way to stop losing sales while you find the cause.

Once the store is back, remove the app's code from the duplicate theme, test the app's replacement, and only reinstall an app whose code you have seen work in preview. An app that blanked your store once will blank it again if you reinstall it the same way.

Frequently asked questions

Why did my storefront go blank after installing an app?

The app injected a script into your theme, usually in theme.liquid, and the script has an error or conflicts with another script. The page loads, the JavaScript fails, and nothing renders. Removing the app or the script tag restores the store.

How do I find which app broke the store?

Duplicate the theme, then remove the most recently installed app's code from the duplicate and preview it. If the preview works, that app was the cause. The theme editor shows the code changes each app made, and the app's support can usually name the snippet.

Should I edit theme.liquid directly to fix it?

Only on a duplicated theme, never on the live one. Make the change in the duplicate, preview it, and publish the duplicate when it works. Editing the live theme while the store is broken risks a second break on top of the first.

Can a blank storefront cost me sales while I fix it?

Yes, every minute it is blank is lost traffic. If the fix takes more than a few minutes, put up a password page with a short message, or roll back to the last working theme version from the theme library. A theme rollback takes seconds and buys you time to diagnose properly.