Bech32 Encoder/Decoder

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from Bech32 Encoder/Decoder

Bech32 Encoder/Decoder: Encode/Decode/Validate betch32(m). Bech32 formats combine a readable prefix with encoded data and a checksum, helping detect transcription errors within applications that use the format. An encoding changes how information is represented so that another program, protocol, or document can handle it. Correct interpretation depends on the precise format and any relevant character set, byte order, or variant. Encoding does not necessarily compress data and does not make it secret. When possible, use a small known value to verify the direction of conversion, then perform a round trip back to the original representation. Preserve leading zeros and other structural characters because a visually minor change can alter the underlying bytes.

Guide updated October 13, 2026

How to use this tool

1. Begin with a representative input. For a practical test, use: A human-readable prefix, a hexadecimal payload, and Bech32 or Bech32m. Replace demonstration values only after you understand the output.
2. Choose the appropriate conversion direction and format options, then provide a short known value before processing your full input.
3. Check the returned representation, especially leading zeros, separators, character encoding, and any format-specific prefix or checksum.
4. Where a reverse operation is available, convert the result back and compare the recovered content with the original.

SEE IT IN PRACTICE

A worked example

a12uel5l

Variant: Bech32
Human-readable prefix: a
Payload: empty
Checksum: valid

This minimal checksum example illustrates format validation with an empty payload. It is not a usable cryptocurrency address; real applications impose their own prefix, version, and payload rules.

Read prefix, data, and checksum separately

The human-readable prefix identifies a context chosen by the application. The encoded data uses a restricted alphabet and a checksum helps detect errors. Converting a hexadecimal payload into the data representation does not by itself create a valid application object. Additional rules can constrain payload length, version, and prefix, especially in address protocols.

Validation has more than one level

A checksum check answers a narrower question than application validity. After confirming the representation, verify the expected prefix, variant, and payload rules in the receiving system. Do not infer ownership, account existence, or network suitability from a syntactically valid string. Keep test vectors and real payment or identity values separate, and verify a round trip before using a conversion in automation.

When this tool is useful

• Inspect a Bech32 payload
• Check checksum variants
• Test an application-specific prefix

Tips for a better result

• A valid checksum does not establish that a cryptocurrency address belongs to the intended person or network.
• Treat bytes and displayed characters as different layers; the same visible text can have more than one byte representation.
• Keep the format name and selected variant with the converted value so another person can decode it consistently.

Frequently asked questions