Questions, answered

Click Get started and sign up with your email, Google or Facebook. Choose a scramble password, add your website's address, and upload an image. The dashboard gives you the code to paste into your site.

No. You copy one line into your site's header and one image tag per picture. Most website builders have a place for "custom code" or "embed HTML" where these go.

Yes, if it lets you add code to the page header and place HTML on a page: Wix, WordPress, Squarespace, Shopify, Webflow and hand-built sites all do. For places that only accept an image link, like some marketplaces and forums, use the plain image option.

Yes. Add localhost to your approved sites to try it on your own computer, or put a test page on your site. Then open the image address in a private window, or from another website, and you'll see the scrambled copy.

You sign in with your pixelsentinel.net account (email, Google or Facebook). The scramble password is separate: it keys the scrambling of your images and is needed to unscramble files offline. It can't be reset by email, so keep it safe.

The scrambled copy: shuffled tiles under a banner with your name, your copyright notice, and pixelsentinel.net.

Yes. Disabling right-click takes a few seconds to get around, and the real image is still at its address for anyone to download. With Pixel Sentinel the image address only ever gives out the scrambled copy.

Yes. Visitors on your site see the image as you uploaded it, at the size your page shows it, with no visible watermark. The invisible watermark doesn't show in photos; on large flat, dark areas of graphics, a very faint texture can occasionally be seen at full size.

Only slightly. The script is small, and each image is sent at the size your page shows it rather than full size. The first view of each image can take a fraction of a second longer while it's prepared.

It stops them from collecting your images from the web. AI crawlers are refused, anything that isn't a real visitor gets the scrambled copy, and every image says "no AI training" in the standard places. It can't stop someone who has already saved a copy some other way.

No, and no website can: once a picture is on someone's screen, their computer can capture it. What we do instead: large views carry an invisible watermark unique to each viewer, so you can upload a screenshot you find and see which visit it came from. Your site also only ever shows display-sized images, so a screenshot is never your full-resolution original.

Yes, by someone determined. It survives resizing, re-saving and small crops, but not heavy editing, tiny thumbnails or a whole-page screenshot. The watermarking technology is public, and so is a tool to remove it. It catches casual leaks, not determined ones.

Yes. Someone who writes a program that imitates a visitor on your site can rebuild the image. Domain locking makes that slow and fiddly, and stops it at scale: known bots and scraping tools are refused, and requests are rate-limited. It's strong protection against everyday copying, not a vault.

No. Without the script, a visitor on your own page can right-click and save the real image. Other sites, image search, bots and direct links still get the scrambled copy. Use the script embed wherever your site allows it.

Your pages will, but your protected images won't appear in Google Images. That's deliberate: image search is one of the main ways images get copied. Leave images you want found there unprotected.

Social networks fetch the preview picture with a bot, and bots only get the scrambled copy. Set your page's share image to an unprotected picture.

Not directly. Those sites copy your image onto their own servers, where we can't protect it. Use a smaller or visibly watermarked version there, and link to your own site.

The scrambled copy. The real image is put together by a small script, and almost every browser runs scripts. The plain image option doesn't need JavaScript.

Our systems can, because they have to show the real image on your site. The key is stored encrypted and only used to serve your images. Your password protects the copies that leave your sites, not your images from us.

Yes. Pixel Sentinel isn't a backup service. You can download full-size originals from your dashboard, but keep your own files too.

Close, not exact. Browsers keep images for a while, so a visitor who reloads a page doesn't always ask us again, and "Save image as" usually saves the copy the browser already has without asking us.

No. Only the scrambled version is stored. You can still download full-size originals from your dashboard at any time.

Click Download link next to the image. You choose how many days it works (up to 30). Each download is invisibly watermarked for that link.

Common image formats (JPEG, PNG, WebP and others) up to 25 MB. Images larger than 6,000 pixels on the long side are scaled down.

You can still sign in and download your originals. You can't change the scramble password or unscramble files offline without the current one, and it can't be reset by email, so store it in a password manager.

Pages using it stop showing it. Copies already in people's browsers or our delivery network can linger for up to an hour.

Every request for your images: real views, scrambled copies, blocked attempts and downloads, by day and broken down by site, network, browser or bot, operating system, device and image.

On your own pages the scrambled copy loads first and the real image is drawn over it, so each real view comes with one placeholder. That's expected and free.

You get the page, a shortened network address, the browser and the time of the visit. That usually points to a household, office or mobile network rather than a person. Compare it with your own site's visitor logs to go further.

Up to 180 days.

One credit covers 1,000 real-image views on your sites. Scrambled copies, blocked attempts and your own dashboard are free.

Yes. Add as many sites as you like, including every subdomain with *.yoursite.com.