How to Create an Encrypted ZIP Archive on Android and Share It Securely with Nearby Share

Why encrypt before sharing?

When you send files directly through Nearby Share, the transfer itself is encrypted, but the files remain in plain text on the receiving device. If the recipient’s device is compromised or you later need to store the archive, the data stays exposed. Wrapping the files in an AES‑256 encrypted ZIP guarantees that only someone who knows the password can open the archive, even if the file falls into the wrong hands.

Before you start

• Charge your phone to at least 50 % (encryption can be CPU‑intensive).
• Connect to a stable Wi‑Fi network – you’ll be downloading a few packages.
• Identify the files you want to protect (photos, PDFs, etc.). Keep them in a single folder for easier archiving.
• Choose a strong password (minimum 12 characters, mix of letters, numbers, symbols). Write it down somewhere safe; forgetting it makes the archive unrecoverable.
• If you plan to use the command‑line method, enable Termux storage access: open Termux and run termux-setup-storage.

Method 1 – Command‑line with Termux

This approach gives you full control over encryption parameters and works on any device that can run Termux.

Step 1: Install Termux and required packages

Step 2: Prepare the source folder

Step 3: Create the encrypted ZIP

Step 4: Verify the archive (optional but recommended)

Step 5: Share via Nearby Share

Method 2 – GUI with ZArchiver (no command line)

If you prefer a visual approach, ZArchiver provides a straightforward way to create AES‑256 encrypted ZIPs.

Step 1: Install ZArchiver

Step 2: Create the archive

Step 3: Verify (optional)

Step 4: Share with Nearby Share

Understanding the encryption choices

Both methods use AES‑256, the current industry‑standard for symmetric encryption. The ZIP format stores the password‑derived key in the file header, but the actual file contents remain unreadable without the password. This is different from password‑protected ZIP implementations that rely on weaker ZipCrypto – our steps explicitly request AES‑256.

Troubleshooting

• “Password incorrect” when opening the archive: Verify you typed the exact same password when creating the ZIP. Passwords are case‑sensitive and spaces count. If you used Termux, remember that the command line does not hide the password; a stray space can cause a mismatch.
• File not found / permission denied: On Android 11+ the app may be restricted by scoped storage. Ensure you granted Termux the MANAGE_EXTERNAL_STORAGE permission (Settings > Apps > Termux > Permissions) or keep the files inside the ~/storage/shared directory created by termux-setup-storage.
• Nearby Share shows “Device not visible”: Both devices must have Bluetooth and location services enabled. Turn them on, then retry. Also, make sure the receiving device is set to receive files from “Everyone” or “Contacts only” as appropriate.
• Archive size seems larger than original files: AES‑256 adds a small overhead (about 12 bytes per file plus padding). If the increase is dramatic, double‑check you didn’t accidentally compress an already‑compressed file (e.g., a video) with the -mx=9 flag, which can inflate size.
• Unable to open the ZIP on Windows: Use a recent version of 7‑Zip or WinRAR that supports ZIP AES‑256. Older built‑in Windows zip utilities may not recognise the encryption.

Safety warnings

Alternative ways to encrypt files on Android

• Cryptomator – creates a virtual vault with transparent AES‑256 encryption. Good for cloud‑synced folders.
• OpenKeychain + GnuPG – for PGP‑style encryption, useful when you need asymmetric keys.
• VeraCrypt (via Termux) – creates encrypted containers larger than 4 GB, but requires more setup.

When to use this workflow

This method shines in scenarios where you need to:

• Send confidential documents to a colleague without exposing them to the recipient’s OS.
• Back up personal data to a shared cloud folder while keeping the contents unreadable to the cloud provider.
• Archive sensitive screenshots, receipts, or private media before handing the device to a technician.

By combining a strong AES‑256 ZIP with Android’s peer‑to‑peer Nearby Share, you get both transport‑level encryption and at‑rest protection, covering the two most common attack vectors for file sharing.