Counter
- Input
- BIN, 6 bytes, contador
- Expected output
- 00 01 02 03 04 05
Byte 256 wraps back to 00.
random binary file generator
Choose BIN, the size and the Padding content in Format options. The choice sets how the file behaves under compression and deduplication, not what is inside it, because the content is only a pattern.
Byte 256 wraps back to 00.
In gzip it reaches about 1,000 to 1, so 1 MB of zeros becomes a few KB.
All bits set.
The tail is cut at the exact size.
Useful for testing the rejection of empty files.
1 MB is 1,000,000 bytes and 1 MiB is 1,048,576 bytes, a 4.86% difference. The same goes for KB (1,000) and KiB (1,024), GB (1,000,000,000) and GiB (1,073,741,824). NIST notes that memory makers often use megabyte for 1,048,576 bytes and storage makers for 1,000,000, so the tool shows the size in both systems and lets you pick the unit.
Without a seed, the bytes come from crypto.getRandomValues, the browser generator. With a seed, they come from a simple deterministic generator, which is not secure. Do not use either as a key.
Because the tool builds the file by repeating the same 1 MiB block by reference, without copying bytes. A 1 GiB file of zeros is a list of 1,024 references to the same block.
Compute the SHA-256 on the file card itself and compare it with sha256sum on Linux or Get-FileHash on Windows. The two values must be identical.
1,000,000 B · 1 MB · 976.56 KiB
1 MB = 1,000,000 bytes (decimal). 1 MiB = 1,048,576 bytes (binary).
With a seed, random data, noise and CSV/JSON rows come out identical on every run.
Test files contain no real data. Use them only to test systems that are yours or that you are authorized to test.