Add your source
Paste a full HTML document or upload a local file. The browser reads the content locally.
Client-side HTML protection
Create password-protected self-decrypting HTML files, encode HTML without a password, protect public email addresses, generate .htaccess code, and create strong passwords.
<!doctype html>
<html>
<body>
<main>Private page</main>
</body>
</html>
Password HTML tool
Use this tool when you want visitors to enter a password before the HTML page opens. Your source code and password are not sent to a server.
Free web tools
Use no-password HTML encoding, email protection, password pages, .htaccess code, or a secure password generator.
Process
Designed for quick distribution of private demos, protected HTML notes, and lightweight offline pages.
Paste a full HTML document or upload a local file. The browser reads the content locally.
Your password is processed through PBKDF2 with a random salt to derive an AES key.
The HTML is encrypted with AES-GCM and embedded into a self-contained unlock page.
Send the generated HTML file and share the password through a separate trusted channel.
Before you publish
These tools help with lightweight HTML protection and code generation. For true logins, private records, or sensitive business data, use server-side security.
Encryption and code generation run locally in the browser. Your HTML and passwords are not uploaded by this static site.
Do not send the encrypted HTML and its password in the same email, ticket, or chat thread.
Do not use client-side self-decrypting files for regulated records, production credentials, keys, or highly sensitive data.
FAQ
No. The password is not stored by the site. If it is lost, the encrypted file cannot be decrypted through Code Encryptor.
Yes. The generated encrypted HTML file contains its own unlock interface and JavaScript. It can be opened locally in modern browsers that support Web Crypto.
Usually yes, as long as the decrypted page and its assets are kept in the expected folder structure. This tool encrypts the HTML source, not external asset files.
Yes, but test the generated file before sending it. Some scripts may depend on server paths, headers, cookies, or assets that are not included in the encrypted HTML.
Ready
Use password protection when visitors must unlock the page. Use no-password encryption when you only want to hide the HTML source from casual viewing.