Convert WebP to Hex

A canonical way to display binary file contents: each row shows an offset (the byte position in the file), 8-32 bytes of data in hexadecimal, and the ASCII representation in a gutter on the right (with non-printable bytes shown as .). The 16-bytes-per-row form is what xxd and hexdump -C produce.

A 10 MB file produces ~30 MB of hex-dump text (40-50 chars per row × ~625K rows). Rendering 30 MB of text in a browser textarea is slow – not a memory or stability issue (modern browsers handle it), just a UX one. The cap protects responsiveness. For larger files, use a desktop hex editor.

Bytes 0-3 are always 52 49 46 46 (ASCII “RIFF”). Bytes 4-7 are the little-endian RIFF chunk size = total file size minus 8. Bytes 8-11 are 57 45 42 50 (“WEBP”). Bytes 12-15 are the inner chunk type, usually VP8 (lossy), VP8L (lossless), or VP8X (extended with metadata).

Flat hex is just the bytes in one of 4 layouts – for copy-pasting into code. Hex dump includes the offset and ASCII gutter – for visual inspection and structure detection. Choose flat for embedding, dump for reading.

Standard hex-dump convention: bytes outside ASCII printable range (32-126) are shown as . so each character occupies the same width as a printable byte. Most of a WebP file is non-printable image data – expect lots of dots.

No. The file is read locally with the FileReader API – nothing is sent to a server, logged, or stored, and the tool keeps working offline once the page has loaded.

Not in this tool. Modifying RIFF/WEBP bytes requires recalculating chunk sizes and (for VP8L) checksums – a proper hex editor handles this. This tool is read-only inspection.

Those are ASCII space (0x20), newline (0x0A), and tab (0x09). In the ASCII gutter, space renders as a literal space, while newline/tab are non-printable and render as . – the convention is to only show typeable graphic characters.

No, only the letter portion of hex (A-F vs a-f). The digits 0-9 are the same in both cases.

Yes, exactly 2× for continuous; 3× or 4× with separator. The hex-dump adds offset (8 chars + 2 spaces) and ASCII gutter (rowWidth + 2 chars) per row – typically ~4× the input file size.