Guide

Protect Wix Product Photos: A Catalogue Workflow

Marking one photograph may not cover a catalogue. Identify the files used in product cards, detail views, variants and sharing areas.

Quick answer and first checks

Keep originals separate and prepare web copies for their display context. Use a consistent catalogue rule for watermark appearance. Recheck scope after adding products or variants, and do not describe browser restrictions as complete protection.

  • Separate original files and web copies
  • Check cards, details and product variants
  • Verify the rule on newly added products
Close-up of a photographer holding DSLR cameras during a photo shoot outdoors.
Quick answer

Do not serve the original high-resolution file directly. Use consistent watermarks across the catalogue, discourage easy saving and archive original source files separately.

1. Keep the original file separate

There is no need to use the highest-resolution file supplied by the photographer or studio directly as the web version. Create a web-optimised copy and keep the original in a secure archive.

This improves performance and avoids giving everyone access to the highest-quality source file.

2. Use visible ownership marks across the catalogue

Watermarks are particularly meaningful on original product photos you have taken, rather than distributor images. A brand mark keeps the source visible.

Keep density low enough to preserve product details; otherwise protection can harm the shopping experience.

3. Reduce easy saving methods

Discouraging simple methods such as right-clicking or dragging to save can reduce casual copying. It is important to acknowledge that this is not absolute protection against advanced users.

Combining this layer with watermarks is more useful than browser restrictions alone.

4. Define one catalogue policy

Randomly varying protection settings between product groups can undermine brand consistency. Define one or two standard layouts for different photo types.

Check whether the policy continues to apply when new products, variants or categories are added.

5. Track sources and usage

Recording the source file, photographer and usage locations for original product photography makes ownership management easier.

If images are also sent to third-party marketplaces, plan their sizing and watermark policies separately.

6. Product-focused protection with Filigrunner

Filigrunner helps bring product-image targeting, watermarks and browser-level deterrence together in one dashboard.

Before going live, check the most-viewed products on both desktop and mobile.

A Vebixo Studio product: Filigrunner

Manage watermarks and image-protection settings centrally.

Open Filigrunner in Wix App Market ↗

Frequently asked questions

Can product photos be made completely impossible to download?

No. Content displayed in a browser can technically be captured in different ways. The aim is to make casual copying harder and preserve ownership marks.

Is reducing the original photo's size enough?

Not on its own, but avoiding unnecessary distribution of high-resolution source files is a good basic practice.

Should every product use the same watermark?

Consistency is useful, but significantly different compositions may need limited exceptions for placement or density.

Related guides

Adding watermarks to products ↗Making image copying harder ↗Right-click protection ↗Filigrunner features and setup scope ↗

Sources and methodology

The official sources below describe built-in Wix behaviour. App-specific features are explained separately on the relevant product page. Verify the result on your own published site.

Developed by Vebixo Studio

Manage watermark settings with Filigrunner

Explore Filigrunner to manage watermark placement, opacity and coverage for product and site images in one place. Protection controls are deterrents; they cannot completely prevent copying or screenshots.

Search the site

Optional analytics helps us understand website use. You can use the site without accepting.

Read the cookie policy ↗