Rollback is the feature that makes every other watermark decision safe to revisit. Pick a design today. Change your mind in six months. Click one button. The original photos come back, untouched, and you can run a new pass with a new design. That is the whole promise. The mechanics underneath are simple, but the edge case where rollback fails is worth understanding before you depend on it.
This guide covers what Viking Watermark stores when you apply a watermark, where it lives in Shopify, how the restore actually executes, what happens with auto-watermark, and the one situation that breaks rollback. We will be honest about the limits. Trust on this feature is the whole product.
Quick facts
Rollback in Viking Watermark means the original photo files come back exactly as uploaded, in one click, per product or in bulk. Originals are stored in Shopify Files at full resolution and are never overwritten by a watermark pass. A product at Shopify's 250-image maximum restores in a single operation. The free tier's 100 images per month is enough to stress-test the whole cycle on a small collection before trusting it with a full catalog. The one thing rollback cannot recover: originals a merchant deleted from Shopify Files by hand.
What "rollback" actually means
Rollback in Viking Watermark is the operation that replaces a watermarked product image with its original (pre-watermark) version. You trigger it from the dashboard with one click per product, or one click for the whole catalog if you want to revert everything at once.
Behind the button, the operation does two things in sequence. First, it locates the original file in Shopify Files (we store every original automatically when you apply a watermark, indexed by a metafield on the product). Second, it overwrites the active product image reference with the original file, then deletes the watermarked file from Shopify Files to free quota. From the storefront perspective, the change is immediate: next page load shows the original photo, no cache delay beyond what your CDN normally does.
Where originals are stored
Every original sits in your Shopify Files store. We do not host them on our servers. There are three reasons for this. First, it is your data. We do not want to be the only place it lives. Second, Shopify Files has the same lifetime as your store, so as long as your store exists, the originals exist. Third, you can audit Shopify Files yourself any time and confirm the originals are there.
The naming convention: each original is stored with a filename pattern like vw-original-{product-id}-{position}-{hash}.jpg. The hash is a content fingerprint so we can detect if Shopify decided to re-encode or compress the file (it sometimes does for very large uploads). The metafield on the product (viking_watermark.original_files) maps each product media position to the original file in Shopify Files. That metafield is how the restore button knows what to put back.
If you ever want to leave Viking Watermark, your originals are already in your Shopify Files. Uninstall the app, the originals stay. Run a one-click rollback before you uninstall and the watermarked versions get replaced too. There is no data hostage problem.
How the restore button executes
The technical flow when you click "Restore" on a product: we read the viking_watermark.original_files metafield to find every original. For each position in the product's media list, we issue a product image update via the Shopify Admin API, swapping the watermarked file URL for the original file URL. Then we issue a delete for the watermarked file (so it does not occupy Files quota). The whole operation usually finishes in 5 to 15 seconds per product, depending on how many photos the product has.
For a "restore the whole catalog" operation, we batch the same flow across all products, processing in parallel up to a per-store concurrency limit (so we do not get rate-limited by Shopify). A 500-product catalog rollback typically finishes in 8 to 20 minutes. You can keep working in the dashboard while it runs.
Rollback with auto-watermark on
One thing to understand if you have auto-watermark enabled: rollback restores the original, but auto-watermark is still listening for new uploads. If you roll back and a new product image gets uploaded a minute later, the new upload gets watermarked because auto is still on. This is intentional. Most merchants who use rollback want to swap designs, not stop watermarking entirely.
If you want to roll back AND stop auto-watermarking entirely, do two things: first, switch off auto-watermark in the settings panel. Then run the bulk rollback. The order matters. If you bulk roll back first and then turn off auto, any uploads that happened during the rollback window get watermarked, and your rollback is inconsistent.
Three checks before you trust rollback
Most merchants never think about rollback until they need it. By then it is too late to verify the system works. Three checks you should run on day one of using Viking Watermark, before you commit to a watermark design.
- 01Test rollback on one product. Pick one test product. Apply a watermark. Verify the watermark shows on the storefront. Click "Restore" in the dashboard. Reload the storefront. Confirm the original photo is back, pixel-identical, no compression artifacts.
- 02Verify the original is in Shopify Files. Go to your Shopify admin, Settings, Files. Search for "vw-original-". Confirm files matching your watermarked products are listed. The presence of these files is your rollback insurance.
- 03Test a bulk rollback on a tagged collection. Tag 5 products with "test-rollback". Apply watermarks. Run a collection-scoped rollback. Verify all 5 originals are restored. This catches edge cases that single-product testing misses.
The one edge case that breaks rollback
Honest framing: rollback can fail in exactly one situation. If you (or someone with admin access to your store) manually delete the original file from Shopify Files, rollback for that product can no longer restore the original. There is no copy on our servers, and Shopify Files does not have a recycle bin. The metafield still exists, but the file it points to is gone.
This happens more often than you might think. A merchant doing a Shopify Files cleanup pass deletes files that look "duplicate" without realizing the "vw-original-" pattern marks them as the rollback source. Or a third-party file-management app does a similar cleanup. Either way, the original is unrecoverable. The watermarked version stays as the active product image; rollback for that specific photo no longer works.
If this happens, here is what we can do for you and what we cannot. We cannot recover the file (it is gone from Shopify, and we never copied it). We can flag the affected products so you know which ones have lost their rollback source. We can re-enable auto-watermark for any new uploads on those products. What we cannot do is bring the original photo back from any source. If you have a copy in your own backup or your photographer's archive, you can re-upload it through Shopify admin and we will detect the new file and rebuild the rollback mapping.
The mitigation: do not let anyone clean up Shopify Files without checking for the "vw-original-" pattern first. The files cost storage quota but they are insurance against every watermark design decision you regret later.
That is the whole rollback story. Install Viking Watermark free and run the three checks above before you commit to any watermark design. The free tier covers 100 images per month, which is more than enough to stress-test rollback on a small collection.
For the broader Shopify image protection picture, including watermarks alongside web monitoring and other layers, our studio image protection guide on Aegis covers the full stack.
Frequently asked questions
Where are my original Shopify product images stored after Viking Watermark applies a watermark?
In your own Shopify Files, with a filename pattern starting "vw-original-". A metafield on each product (viking_watermark.original_files) maps each product media position to its original. We do not store originals on our servers.
How long does a rollback take?
Per-product rollback: 5 to 15 seconds. Full-catalog rollback for 500 products: 8 to 20 minutes. The bulk operation runs in the background while you keep working in the dashboard.
Does rollback work if I uninstall Viking Watermark?
Run a bulk rollback before uninstalling and you keep the originals as your active product images. If you uninstall without rolling back, the watermarked images stay live but the originals are still in your Shopify Files. Reinstall and the mapping rebuilds from the metafield.
Can I roll back just one image in a multi-image product?
Yes. The dashboard lets you target any specific media position per product. Useful when you want to keep the watermark on the hero image but restore detail shots to original.
What if a product has 250 images (the Shopify max)?
Rollback handles all 250 in one operation. The per-product time scales linearly with image count, so a 250-image product rollback takes roughly 60 to 90 seconds instead of 5 to 15.
Does auto-watermark affect rollback?
Yes. If auto-watermark is still on after a rollback, new uploads to that product get watermarked again. To stop watermarking entirely: switch off auto-watermark first, then run the bulk rollback. The order matters.
Is there a rollback history or undo for rollback?
Yes. The dashboard logs every rollback operation with a timestamp and the affected products. If you roll back and immediately regret it, you can re-apply the watermark from the same saved design without losing any quality. The watermark is deterministic on the same original image.