In-browser sample file generator: custom byte sizes up to 1 GB, category ZIPs and inert stubs

Build valid sample files of any exact size from 1 KB to 1 GB directly on your device, bundle an entire category into a single ZIP archive in memory, or generate safe non-executable EXE and ISO header stubs.

1. Generate a valid file of any exact byte size (1 KB to 1 GB)

Select any format and preset or custom byte count below. Files up to 32 MB are assembled in a background Web Worker and checked against their SHA-256 digest when one is published; larger files up to 1 GB (1,073,741,824 bytes) are streamed chunk-by-chunk through this site's Service Worker directly into your browser's download manager so they never have to fit in RAM.

2. Download all samples in a category as one ZIP

Build a multi-file .zip archive containing representative fixtures for an entire category right in your browser using our client-side IEEE CRC-32 ZIP writer.

Ready to assemble ZIP bundle locally in your browser.

3. Inert non-executable stub generator (.exe and .iso)

Need to verify that an upload form blocks .exe or .iso files by extension or magic bytes? Generate an inert, non-executable header stub locally on your device. It contains the magic bytes (MZ or CD001) plus an ASCII notice and zero executable code.

Inert stubs are built locally in your browser and never hosted on the server.

Real browser memory and streaming limits explained

Understanding how browsers allocate memory and stream downloads prevents tab crashes when generating 100 MB, 500 MB, or 1 GB fixtures:

Frequently asked questions

Does generating a 500 MB or 1 GB file consume 1 GB of network bandwidth?
No. The file is synthesized locally on your CPU by our deterministic JavaScript generator using small seed assets (under 1 MB). The bytes flow from the browser's Service Worker straight to your hard drive without crossing the internet.
Why does the generator offer EXE and ISO only as inert stubs?
Serving real executable binaries on a public site triggers Safe Browsing warnings. An inert stub starts with the genuine magic bytes ('MZ' at offset 0 for EXE, or '\x01CD001' at offset 32,768 for ISO) followed by an ASCII test notice, which is everything an upload security validator inspects.