Skip to content
Testaroo
7z651 B

7z - Password Protected

A password-protected 7z archive (AES-256, encrypted header). The password is “novus-example”, printed here on purpose so you can test encrypted-archive extraction. Contains only harmless sample text.

7z

application/x-7z-compressed

651 B
Format
7z (AES-256)
Members
3
Encryption
AES-256, encrypted header
Password
novus-example

Binary 7z: no in-browser preview. Download it above to open in a compatible application.

Specifications

Format
7z (AES-256)
Members
3
Encryption
AES-256, encrypted header
Password
novus-example

Testing contract

Expected to pass
Scenario
Exercise 7z - Password Protected in its sevenzip workflow. A password-protected 7z archive (AES-256, encrypted header).
Expected result
3 members after reading the header with the documented fixture password when required; member paths: README.txt, records.csv, config.json; 514 uncompressed bytes. Declared feature checks: members=3; encryption=AES-256, encrypted header; password=novus-example.

What is a .7z file?

7z is the native archive format of 7-Zip, supporting high-ratio LZMA and LZMA2 compression, strong AES-256 encryption, and solid compression across multiple files. It bundles many files with a flexible header and typically outperforms ZIP on compression. It is popular for efficient archiving and distribution.

How to use this file

Use an example 7z to test 7-Zip-compatible extraction, LZMA decoding, solid-archive and multi-volume handling, and optional encrypted-archive support.

How to use this file for testing

“7z - Password Protected” is a deterministic Testaroo fixture for Conversion testing. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.

Documented properties for this file: 7z (AES-256). Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Archive fixtures are documented down to their member list (shown on this page) and are deliberately safe, no zip bombs, executables, or hidden payloads. Test extractors against nested, unicode, empty, and encrypted variants.

Generated by generation/archives.py. Free for any use, no attribution required, license.