The Shopify App Store has a dozen watermark and badge apps and their feature lists read almost identically. Feature count is not what separates them. Five things do: whether the app edits your original files, whether badges are driven by rules or by hand, whether campaigns can end by themselves, how it behaves on a translated or multi-currency store, and what it does to page weight. This is how to check each one, so you can evaluate any app rather than trusting a comparison table that will be out of date by the time you read it.
1. Does it touch the original file?
The single most important question, and the one least often answered plainly on a listing page.
Two architectures exist. One edits and stores a new image: the badge is burned into a file that replaces or sits alongside your original. The other renders at the display layer: the storefront draws the badge over the unmodified image, and nothing in your media library changes.
The difference decides three things at once — whether you can undo a campaign in one click, whether your Google Shopping feed submits a badged image, and whether you still have a clean original in six months.
How to test it: install, badge one product, then open that product's media in Shopify admin and download the file. If the badge is in the downloaded image, the app is editing originals. If it is not, the badge is display-layer. This takes two minutes and tells you more than any feature list.
Ask also what happens on uninstall. A display-layer app removes the overlay and leaves your images as they were. An editing app may leave every file permanently altered.
2. Rules, or one product at a time?
Manual badging works for ten products. At a hundred it becomes a task that is never finished and never undone.
What to look for, in rough order of value:
- Compare-at price. Badges anything genuinely discounted and unbadges it when the discount ends. Self-maintaining, and the closest thing to a set-and-forget sale badge.
- Inventory level. "Only a few left" that is actually true.
- Collection and tag. Follows the merchandising you already maintain.
- Product type or vendor. Useful for catalogues organised that way.
How to test it: set up a compare-at rule, then remove the compare-at price from one product. The badge should disappear without you touching the app. If it does not, the rule was evaluated once rather than continuously, which is a different and much weaker feature.
3. Can a campaign end without you?
Every store has carried a Black Friday badge into January. Removal is a separate task from creation and only one of them has a deadline in anybody's mind.
Scheduling — a start date and an end date set at the same time — fixes this structurally. Without it you are relying on a calendar reminder, and reminders during a busy trading period are the ones that get dismissed.
How to test it: set a badge to end in ten minutes and watch it go. Some apps accept an end date and apply it only when something else triggers a refresh, which is not the same thing.
4. What happens on a translated or multi-currency store?
A badge is text on an image, which makes it the element most likely to stay in English after everything else has been translated.
Two questions:
- Does the badge text follow the customer's language, or is it one string for all markets?
- Does the badge layout survive a longer word? "SALE" is four characters; its German and French equivalents are not. A badge sized exactly to the English string breaks the moment it is translated.
Currency has the same shape: "SAVE £40" is wrong for a shopper being shown euros. On a multi-currency store, percentage badges avoid the problem even where an absolute saving would normally read better.
How to test it: switch your storefront to a second market and look. This is where apps built for single-market stores show themselves.
5. What does it cost in page weight?
An overlay rendered as part of the image request adds no extra requests. An overlay drawn as HTML over the image adds markup but little weight. Neither is a Core Web Vitals problem at badge sizes.
What would be a problem is an app that generates and stores a second copy of every image, doubling your media library and CDN footprint in order to say "20% off" — or one that loads a large script on every page to decide whether a badge applies.
How to test it: run a Lighthouse or PageSpeed check on a badged collection page before and after installing. Look at total page weight and request count, not the score alone.
The questions that matter less than they look
Three things listings emphasise that rarely decide the outcome:
- Badge library size. "200+ pre-made badges" sounds substantial. You will use three, and they need to match your brand, which usually means editing one anyway.
- Animation. Animated badges attract attention and look cheap on most storefronts. If you want one, check it renders as a static image in the cart and in social previews, where animation does not survive.
- Analytics. Most badge apps report impressions, which tells you nothing. Whether badges are working is answered by a collection-level click-through test, not by an app's own dashboard.
What free plans usually hide
Most of these apps have a free tier, and the limit is almost always the number of active products rather than the number of badges. That is the right thing to check: a free plan covering three products lets you see how a badge sits on your own photography, which is what you need before paying for anything.
What tends to sit behind the paywall: scheduling, rule-based targeting, and trust badges as distinct from promotional ones. Those are the features that separate a badge you maintain from one that maintains itself, so price the paid tier on whether it includes them rather than on the headline number.
Watermark puts text, image and watermark overlays on the free plan for three active products, with unlimited products, trust badges, scheduling and smart rules at $4.99 a month.
A five-minute evaluation
- Install. Badge one product.
- Download that product's image from admin. Is the badge in the file?
- Set a compare-at rule, then clear a compare-at price. Does the badge go?
- Set an end time ten minutes out. Does it end?
- Switch markets. Does the text translate and still fit?
- Check the collection page and the cart drawer. Is the badge cropped?
Any app that passes all six is a reasonable choice. Most will fail at step two or step four, and those are the failures that cost you later.
Where to go next
The reason step two matters most is the feed: Google Merchant Center disallows promotional overlays on the image your feed submits, so an app that edits originals puts your Shopping listings at risk every time you run a promotion.
The wider picture — how badges, trust marks and watermarks differ, and where each belongs — is in the guide to watermarking Shopify product images.
