ztfile / Create ZIP

Browser ZIP security: what local encryption protects

Understand local ZIP processing, AES-256 passwords, visible filenames and recipient compatibility before using a browser-based archive tool for sensitive documents.

A clear guide to the security boundary

01

Does browser-based mean my files are uploaded?

Not necessarily. ztfile uses the browser to read selected files, build archives and decrypt supported ZIP entries on your device. File contents and archive passwords are not sent to our servers for those operations. Loading a website still involves ordinary network requests for the page and its resources, so local file processing should not be confused with a claim that your browser never communicates with the internet.

02

What does the password protect?

With encryption enabled, ztfile creates an AES-256 encrypted ZIP. Its password protects the archived file contents, but the practical protection also depends on password strength, secrecy and device security. By default, the tool generates a random 20-character password. Keep that password in an approved password manager rather than in the same folder or message as the archive. There is no password-recovery service if you lose it.

03

Which information remains exposed?

ZIP encryption does not hide filenames. Avoid putting personal information, customer names or sensitive project details into archive entry names. Encryption also does not protect the unencrypted original files or copies created after extraction. Handle those copies using your usual access restrictions, backup controls and retention rules. A malicious browser extension or compromised endpoint can undermine an otherwise strong encryption workflow.

04

Will every recipient be able to open it?

AES ZIP support varies across archive tools and operating-system versions. Before a time-sensitive transfer, confirm that the recipient has an AES-compatible extractor, such as ztfile or another suitable archive application. Password protection alone does not prove that an archive uses AES: older ZIP files can use legacy ZipCrypto. A wrong password, unsupported compression method or damaged archive can still prevent extraction.

05

When should I use a different workflow?

Use your organization's approved secure-sharing platform when you need recipient identity checks, expiring access, access revocation, centralized audit records or managed retention. An encrypted ZIP is a portable file, not an access-management system. Browser encryption can be one part of a risk-based protection process, but it cannot replace an information security management system or independently establish ISO 27001 compliance.