Features

Hex Viewer & Binary Support

Not every KV value is text. KVault detects binary data and renders a proper hex viewer — and previews embedded images inline.

Overview

KV values are bytes, not strings — and KVault treats them that way. When you open a value, KVault inspects its contents and routes text-like bytes to the code editor and binary blobs to a dedicated hex viewer. The detection is automatic and based on the actual bytes, not the key name or content type.

The hex viewer renders three synchronized columns: an address column showing byte offsets, a hex column showing the raw bytes, and an ASCII column showing printable characters (with non-printable bytes rendered as dots). For common image formats, KVault sniffs the magic bytes and renders a live preview of the image above the hex view so you can confirm what you're looking at.

How to use it

There's nothing to configure. Open any key; if its value is binary, the hex viewer appears instead of the text editor. Values cross the Tauri boundary as a Vec<u8> and are rendered by KVault's native viewer — large binary payloads stay responsive.

  • PNG, JPEG, GIF — previewed inline above the hex columns.
  • Other binary — address/hex/ASCII columns only; scroll through the full payload.
  • Ambiguous values — KVault defaults to treating them as text; if that's wrong, the status bar flags the detected content type.

Tips

  • KVault's value-read response includes a size field, so the viewer knows immediately whether to stream or render in full.
  • Binary values can't be edited in place — use export/import if you need to replace a binary payload.
  • If you're storing images in KV, the hex viewer's inline preview is the fastest way to audit which key holds which asset.
  • Combine with global search on the key name to locate binary assets across accounts quickly.