Lock a whole file before you email it
Email carries readable attachments on many servers. Encrypt the file first, then send the password another way.
Why email alone is not a vault
Ordinary email stores copies on the sender server, the recipient server, and often on phone sync services. Anyone with mailbox access can open a plain attachment. Encrypting the file before you attach it changes what those servers hold: a locked bundle instead of a readable document.
This page is the email-first entry into Vidzilla’s file encryptor. The crypto still runs locally in the browser through the same encrypt tool. Your goal here is a portable encrypted file you can attach to Gmail, Outlook, or any client that accepts a binary attachment.
Contracts, ID scans, payroll exports, and medical forms are common candidates. If the content would hurt someone when forwarded by mistake, lock it before the compose window. Treat encryption as a habit for sensitive sends, not as a rare emergency step.
Encryption does not hide that you sent a file. It hides the contents until the password is known. That is the trade you want for attachment workflows: the email still arrives, but the payload stays closed without the key.
Sibling of the local encrypt tool
The working surface is /tools/encrypt. This page points you there with an email-focused framing. Choose Encrypt mode, add the whole file, pick AES for new work, set a strong password, and download the encrypted result.
Processing uses the browser’s crypto APIs on your device. The file and password are not uploaded to Vidzilla for this job. That matches the encrypt page’s local design: you leave with a locked file you control.
You can also encrypt short text on the encrypt page when you only need a ciphertext string. For email attachments, use the file upload path so the entire document or archive becomes one protected download.
Decrypt mode on the same tool opens a file you previously locked, once you enter the matching password. Confirm decrypt works on your machine before you delete the clear working copy you still need for records.
- Open File Encryptor from this page.
- Select Encrypt, then add the file you plan to attach.
- Choose AES for new shares, set a password, download the locked output.
- Send the file by email and the password on a different channel.
Password on a second channel
A locked attachment is useless if the password rides in the same message. Put the file in email. Put the password in SMS, a phone call, Signal, or another thread the recipient already trusts.
Write the password into a password manager entry titled for that shipment. You will need it again if the recipient asks for a resend or if you must reopen your own copy months later.
Rotate passwords between shipments. Reusing one phrase for every encrypted attachment turns a single leak into access to the whole habit. Fresh passwords cost little time and cut that risk.
If the recipient cannot open the file, walk them through decrypt on the same encrypt tool or a compatible AES workflow. Do not weaken the password to make support easier; teach the decrypt steps instead.
Whole files, folders, and PDFs
Encrypt one file at a time when that is all you are sending. For a set of documents, pack them into a ZIP first with the archive tool, then encrypt the ZIP so one attachment covers the packet.
PDF-only password gates inside a PDF reader are a different control. This encryptor locks the bytes of whatever file you feed it. Use password-protect PDF when a portal demands a PDF that opens with a PDF password; use this path when you need a general encrypted container for email.
Name the output so it is obvious the file is locked—client-name-contract-encrypted.bin or a clear .enc style name your team already uses. Vague names lead people to open the wrong copy.
Keep an unencrypted internal copy when regulations require readable retention. The encrypted send copy is for transport. Do not treat the emailed file as your only archive.
What free use covers
File encryption on Vidzilla runs within the daily tools quota. Ordinary document and archive sizes process without an account. Large video masters may hit browser memory limits; encrypt those on a desktop with more RAM or split the work.
Prepared outputs are not long-term storage. Download the encrypted file promptly, move it into a folder you control, and only then close the tab. Leaving mid-download can leave a half-written file in Downloads.
Company policy may forbid uploading certain records to any third-party site. This encrypt path is local crypto in the browser, but still follow your workplace rules for classified material and regulated data.
Pro raises daily tool limits and removes advertising on Vidzilla. It does not change the local nature of the encrypt step or invent a password recovery service. Lost passwords stay lost.
Encryptor versus a shared link
A passworded file works on any channel that can carry a binary: email, USB, or a generic cloud folder. A browser-encrypted share link is a different product path aimed at link delivery. Choose the encryptor when the recipient expects an attachment plus a password you dictate out of band.
If both sides already use Vidzilla links for zero-knowledge sharing, you can still encrypt first for defense in depth. The attachment habit remains useful when the other party has no Vidzilla account and only checks email.
Do not mix workflows in one message. Either send a locked file with an out-of-band password, or send a share link with its own access rules. Stacking unclear instructions causes failed opens and support threads.
After the recipient confirms the decrypted file opens and matches what you intended, clean intermediate encrypted copies from shared drives if policy requires a short retention window.
After the locked download
Open decrypt once yourself with the password you chose. Confirm the restored file matches the source. Only then attach the locked copy to email.
Tell the recipient which tool opens the file and that the password arrives separately. Vague “here is the file” messages create failed opens and password requests in the same inbox you tried to protect.
If something fails, change one variable at a time: the input file, the algorithm choice, or the password entry. Note what changed so the next attempt is a measured test.
After you finish, move keepers into a folder you control and only then close this tab. That sequence keeps half-written files and lost downloads out of your next session.
Questions about encrypting files for email
Does this upload my file to Vidzilla?
The encryptor runs AES in your browser on the encrypt tool. Keys and file bytes stay on your device for that job unless you later choose to share the encrypted output yourself.
Where do I send the password?
Use a different channel than the email that carries the file—SMS, a call, or a separate messenger thread. Never put the password in the same message as the attachment.
Can I encrypt a whole folder?
Zip the folder first with the archive tool, then encrypt the ZIP so one locked file covers the set.
What if I lose the password?
There is no recovery path. Store passwords in a manager. Without the password, the locked file stays unreadable.
Is this the same as password-protect PDF?
No. Password-protect PDF adds a PDF-reader password. This path locks any whole file through the general encryptor for email and other channels.
Which algorithm should I pick?
Choose AES for new shares. Legacy ciphers exist for old material that already used them, not as upgrades for fresh attachments.