How to Find Leftover App Code in a Theme (Without Guessing)

“We uninstalled the app, but the widget is still there.”

If you have worked on Shopify stores long enough, you have heard this. The reason is simple: apps can touch multiple layers of a storefront, and uninstall does not always reverse every theme change.

This post is a systematic method to find leftovers without guessing.

Start with the symptoms

Write down what you see:

• a widget appears twice
• a popup still shows
• a badge is still present
• performance got worse

Knowing the symptom helps you locate the source faster.

Step 1: Check App Embeds first

Modern apps often use app embeds.

In the theme editor:

• open App embeds
• look for anything you do not recognize
• disable on a duplicate theme first

If a widget disappears, you found the source.

Step 2: Search for app snippet includes

Many older apps add a Liquid include:

• render or include in theme.liquid
• injection in product/cart templates

Search your theme for:

• the app name
• vendor namespace
• snippet names that look like app-*

If you are unsure, comment out the include and test.

Step 3: Inventory assets the app added

Common leftover files:

• assets/app-*.js
• assets/app-*.css
• snippets/app-*.liquid

Do not delete files first. Remove references first, then delete later.

Step 4: Find duplicated script sources

It is common to have the same integration loaded from:

• theme file
• app embed
• another app
• a tag manager

Quick method:

1. Open DevTools > Network
2. Filter by the vendor domain
3. Check if the same script loads more than once

If yes, find where each copy comes from.

Step 5: Check store settings outside the theme

Leftovers can live in:

• pixels and customer events
• metafield definitions and values
• discount rules created for promotions

These are not theme files, but they impact storefront behavior.

Step 6: Validate with a “known-good” version

If possible:

• compare with a previous theme version
• compare with another store that does not have the integration

The goal is to isolate what changed.

A note on safety

Do not remove code on the live theme directly. Use a duplicate, verify purchase flow, then publish.

Make it repeatable

The fastest teams use the same audit process after every uninstall. If you can track leftovers and changes over time, cleanup becomes a routine instead of a risky guess.

If you want to reduce manual searching, Checkpoint: Store Scanner helps surface leftover theme references and common risk areas so you can focus your cleanup where it matters most.