On this page
1. Prepare a folder to password-protect files with 7-Zip #
Use 7-Zip from the official download site. This guide covers its Windows File Manager.
Create a folder named workshop-handoff containing three harmless sample files:
| File | Example contents | What it checks |
|---|---|---|
| README.txt | Workshop starts at 10:00. | A text file opens after extraction |
| equipment.csv | item,count followed by laptop,2 | A second file keeps its contents |
| notes.txt | Bring the project files. | The archive contains the whole folder |
Use disposable data for the first run. Keep the original folder available until you've checked the extracted copy. An encrypted archive creates a protected package; it doesn't remove existing unencrypted copies elsewhere on your computer or cloud storage.
2. Open Add to Archive #
Open 7-Zip File Manager, browse to the folder's parent location and select workshop-handoff. Click Add. You should see the Add to Archive dialog.
Using the File Manager avoids differences between the old and new Windows context menus. Explorer can reach the same operation through 7-Zip's installed commands, but the dialog is the part that matters.
Set Archive to a new filename, such as workshop-handoff.7z. Choose a destination outside the source folder so you don't accidentally include an older archive in a later package.
3. Choose 7z and ordinary compression #
Set Archive format to 7z. Use Normal under Compression level for this example and leave the advanced compression settings alone.
The official 7z format page describes its AES-256 support. The 7z format also supports encrypting archive headers, which is how file names can be hidden.
A recipient needs a compatible application to open the file. PeaZip provides a graphical option across desktop systems, and Keka is a Mac option. Confirm that the recipient has one before sending a format they haven't used.
4. Enter a unique password and hide file names #
In Encryption, fill Enter password and Reenter password with a unique password generated and stored in your password manager. Don't use the example folder's name or reuse an account password.
Confirm Encryption method is AES-256. Enable Encrypt file names. These controls are separate: encrypting file contents and hiding the archive's file list aren't the same operation.
Leave Delete files after compression unchecked so the source folder remains available for the extraction check.
If you need a password manager, our free password-manager shortlist compares local and synchronized vault options. Record which archive the generated password belongs to so you can find it later.
5. Create the archive #
Click OK and let the operation finish. The new .7z file should appear at the destination you chose.
Don't judge compression by the tiny example's file size. The exercise is checking the encryption and extraction workflow. Real photographs and videos may already be compressed, so a general archive won't always make them much smaller.
Close the archive window before checking access. A newly opened session gives you a clearer check than leaving a window open after entering the password.
6. Check access with and without the password #
Open the archive again in 7-Zip File Manager. With file-name encryption enabled, it should request a password before displaying the contents.
Cancel that prompt once to confirm you can't browse the internal file list through that session. Then reopen it and enter the stored password. The three example files should become visible inside workshop-handoff.
If files appear without a prompt, don't send the package yet. Check the archive's name and location to confirm you're opening the new copy. Recreate it with 7z, a nonempty password and Encrypt file names enabled.
7. Extract into a separate check folder #
Select the archive's contents and use Extract. Choose a fresh destination such as workshop-handoff-check, then provide the password when requested.
Open all three extracted files. Check their names, text and folder structure against the source. If you are packaging real work next, include the same kind of check for the important documents before sharing.
An extraction check tests whether you can recover the package. It doesn't mean every downloaded archive is safe to open; this example uses files you created yourself.
8. Send the package and password through separate routes #
Transfer the finished archive through the method agreed with the recipient. Send the password through a separate agreed channel, and ask them to confirm that extraction works before you remove any temporary check files.
For a local device handoff, the LocalSend guide explains moving a file between devices. For other methods, compare the file-transfer shortlist.
The archive's own filename remains visible. Use an ordinary project label if the name itself would reveal information you don't want displayed in an email attachment or shared folder.
Reported problems and the fixes that matter #
In a November 2025 archive-encryption discussion, the user could still see a protected archive's contents. They confirmed that enabling Encrypt file names solved the problem. Use the separate reopen check above to verify both content access and file-list access.
A February 2026 7-Zip issue describes an archive losing password protection after its last file was deleted and new files were added. For a new handoff, create a new protected archive with explicit settings instead of recycling an emptied package. Repeat the access and extraction checks after changing its contents.
Troubleshooting #
| Problem | Likely cause | Fix |
|---|---|---|
| File names appear without a password | Header encryption wasn't enabled | Create a 7z archive with Encrypt file names |
| Recipient's built-in ZIP tool won't open it | It doesn't support the format/method | Use a compatible archive app; agree on the format first |
| Password is rejected | Wrong stored entry, typing error or damaged archive | Recheck the stored password; compare a fresh transfer copy |
| Some files are missing | Wrong source selection | Recreate from the intended folder; inspect the full list |
| Old archive opens instead | Duplicate destination names | Use a new filename and verify the full path |
| Password field differs from this guide | Another GUI or format is in use | Use Windows 7-Zip File Manager and 7z |
Variations #
Send an ordinary ZIP when secrecy isn't the goal
For public project assets, ZIP may be the easier format. Choose zip under Archive format and leave encryption out. Don't call that a protected package simply because the previous operation used a password.
Use encrypted ZIP only after a compatibility check
7-Zip supports AES encryption for ZIP too, but the recipient's software must support the method. ZIP doesn't provide this guide's 7z file-name-encryption option. If hiding names matters, keep the 7z workflow and choose compatible receiving software.
Package a large media folder
Expect compression time and output size to depend on the files. If the main goal is a smaller video, the video-converter list addresses encoding choices. An archive can bundle media without substantially reducing it.
Completion checklist #
- The correct source folder is included.
- The archive uses 7z and AES-256.
- Encrypt file names is enabled.
- The unique password is stored with a recognizable archive label.
- A fresh session requests the password before showing contents.
- Extraction into a separate folder restores every example file.
- The recipient has a compatible app and the password arrives separately.
Next steps #
Read 7-Zip vs PeaZip for other archive workflows. The free archive-tool shortlist covers additional Windows, Mac and Linux options.
For another Windows workflow, NanaZip offers modern Explorer integration. Mac users who only need extraction can consider The Unarchiver.
