Contents

Introduction
Overview
Key Benefits
Key Features
How does it work?
Revision History
Working with HTMLProtector
Getting Start with HTMLProtector
Using HTMLProtector
"Input" Tab
"Output" Tab
"Encryption" Tab
"Meta Tag" Tab
"Script" Tab
"Password" Tab
"Image" Tab
"Source Code" Tab
"Tags to Skip" Tab
"Result" Tab
Buttons
Command Line
Private HTML Comment Tag
FAQ
Registration
Registration
Unregistered Copy Limitation
License
Online Support

 
Home
HTML Protector Web Online Help
Prev Page Next Page
 
 
Click here to download free trial version and learn more information about the program.

HTMLProtector

The "Image" tab is used to provide advanced options to protect image files of your website from being stolen; the interface is illustrated below.



First, you should check "Enable advanced image protection" option to make all advanced image protection options work for your protected pages.

"Only protect image bigger than X * X pixels": In many websites there are a lot of small images for which there is no need of whatever protection. Here you can specify the minimum image size that does not need protection. If you specify here 50 * 50 pixels as a minimum image size, any image with a width less than 50 pixels or a height less than 50 pixels will not be protected. All images outside this range will be protected, like 100 * 30 pixels images.

"Output image quality": Specify the quality of output JPEG image. We suggest leaving the default value of 85, which will preserve the original image quality without increasing the image size greatly.

"Protect image by using server-side script": As most of web browsers store embedded images in their caches, these image files can be captured from there easily. Unfortunately this can't be avoided by a simple source code modification. Therefore HTMLProtector gets around this problem by using a server-side script that loads and displays all images. If this option is checked, all links to images within the source code will be changed to server-side script calls and a server-side script file "hp_image.php(.perl/.asp)" will be generated in output directory. To make it work, your web server needs to be able to execute specified server-side script. Furthermore, the generated server-side script file "hp_image.php(.perl/.asp)" must be uploaded to your server. Since the script can only be executed on server-side, the embedded images within pages that have been protected in this way will probably not be loaded correctly on your local computer. With current version of HTMLProtector, three script types (PHP, Perl and ASP) are available for apply. You need select one of them which your web server supports.

"Protect image by converting it into Flash movie": This option converts all embedded images into Macromedia Flash movies. Images are stored in Flash movies after protection so that visitors will be unable to save images by right clicking on them. This option also prevents images being captured from web browser cache. Converted Flash movies will be generated in the output directory, and their file names will derive from original image files. For example, if original image file is "image1.jpg", the generated Flash movie will be "image1.jpg.swf" accordingly. Meanwhile, a text file "hp_image.txt" will also be created in the output directory. After protection, all these Flash movies and "hp_image.txt" need be uploaded to your web server to make protected pages work correctly.

"Protect image by splitting it into pieces": This option splits your images into pieces and generate the appropriate HTML code to display those pieces in your pages as if this is an integral, non-splitted image. This will make image theft nearly impossible - if someone wants to get some of your images, he will not be able to get the entire image, only a pieces of it saved under random, meaningless names. It will be very hard to determine that a certain piece is a part of a certain image. Let's say your website has 10 images, and you configured HTMLProtector to split them into 3 * 3 = 9 pieces each - this will result in 90 image pieces with random names, mixed with a lot of images from other websites visited. A determined person may still be able to find all the pieces of a certain image, but finding them and joining them together to recreate the original image will require a lot of time, knowledge and expensive image editing programs(like Photoshop or similar). In most cases this will also lead to a decreased image quality. There are two ways to define how to split the protected images - you can choose to split them always into fixed number of pieces regardless of their size (check "Split image into X * X pieces") or you can choose to fix the size of the pieces, in which case bigger images will be splitted into more pieces (check "Split image into pieces with X * X pixels"). The pieces of the protected image will be saved in output directory under random, meaningless names. In order to get protected pages work, you must upload all of them to your web server.

"Protect image by adding watermark": Adding a semi-transparent watermark overlay to pictures you will be posting on the web is a good way to identify the source and discourage people from copying your photos and claiming them as their own. You are allowed to customize the watermark's transparency. If it's 0%, the watermark will have no transparent attribute, otherwise when it is at 100%, the watermark will hide itself. HTMLProtector supports both text-based watermark and image-based watermark. With text-based watermark, you need enter the text for your watermark, and font, color, size and rotation angle of the watermark can also be customized; With image-base watermark, you should fist choose an image file for your watermark, then set the transparent color - which is in the watermark image but will not be showed when creating watermark. The protected image which contains watermark will be saved in output directory under name generated based on original image file. For instance, if name of original image is "image1.jpg", then the protected image will be created with name of "image1.jpg.jpg" after protection. All protected images in output directory should be uploaded to your web server; otherwise images in your protected pages will probably not be shown correctly.