Generate bytes for a binary workflow
Enter a whole decimal Byte count and choose Generate bytes. The page requests that many values from the browser's cryptographic random source and shows two text encodings of the same result: lowercase hexadecimal and standard padded Base64. Download binary saves the underlying bytes, without a text header or a byte order mark.
The initial count is 32, but nothing is generated until you press the button. A 32-byte result has 64 hexadecimal characters and 44 Base64 characters, with one trailing padding character. The values themselves are intentionally unpredictable, so a reproducible example checks lengths and decoding rather than expecting a fixed string. Generating again replaces the previous result; changing the count clears it.
Choose the representation your application expects
Hex uses two characters for each byte. Base64 uses a different alphabet and can end in equals-sign padding; that padding is encoding syntax, not additional binary data. The download contains exactly the requested number of bytes. Saving the visible hexadecimal as a text file would produce different bytes and twice as many ASCII characters.
Counts from 1 through 65,536 are accepted. Fractions, exponent notation, signs and empty input are rejected. The upper bound keeps one operation within the documented Crypto.getRandomValues byte limit. If the browser lacks that API, the page shows an error rather than falling back to another random source.
Understand the guarantee boundary
The browser supplies cryptographically strong pseudorandom values. This page does not estimate the entropy of the result, run a statistical certification suite or prove that any two outputs differ. Repeated bytes inside a sample are normal. Byte count describes storage size; treating that count as an independently measured security score would be misleading.
The generated buffer is kept in page memory for display and export. The tool does not send it to a server or persist it in browser storage. A downloaded file remains wherever your browser saves it. This utility is useful for local fixtures and raw-byte workflows, but it does not create an application-specific key container or manage key lifecycles.
Related inspections
Use the Byte Order Mark Inspector to inspect a saved file's starting bytes. Random data can coincidentally begin with a known signature; that does not turn the rest of the file into valid text. Use the UUID Inspector when the input is an identifier with defined fields rather than arbitrary bytes.





