Skip to main content
Tool Factory

Encoding & Number Bases

Bech32 Encoder

Convert input into Bech32. Enter the data, choose the input and output formats, then copy the result.

Tool workspace

Your input stays in this browser.

Add the required input to continue.

Needs input

You can run the tool again after any change.

Options

SegWit witness version (0-16). Only used in Bitcoin SegWit mode.

Your result appears here

Convert input into Bech32. Enter the data, choose the input and output formats, then copy the result.

This tool runs open-source code from CyberChef by GCHQ (Apache License 2.0). See open-source credits.

Bech32 Encoder converts data between formats in your browser. For a correct result, verify the prefix and checksum.

a checksummed Bech32 string Processing runs in the browser.

Instructions

  1. Provide text or data for this tool.
  2. Set the human-readable prefix and data.
  3. Compare the output with a known Bech32 Encoder sample.
  4. Keep the original value until the receiving system accepts the result.

Example

Input: witness data for a supported address

Settings: Bech32 Encoder: set the human-readable prefix and data

Result: a checksummed Bech32 string

Limits

  • Bech32 Encoder: Bech32 parameters depend on the application
  • Bech32 Encoder: The operation does not detect a different input format automatically.
  • Bech32 Encoder: Processing stays in the browser.

Questions

How do I encode bytes with a Bech32 prefix?

Set the Human-Readable Part and select Bech32 or Bech32m. Choose the input format that matches your data. Generic mode encodes supplied bytes without adding a SegWit witness version.

What does Bitcoin SegWit mode change?

This mode adds the selected witness version before encoding the witness program. The encoding choice must match the address format you intend to use. Generating a string does not create a wallet or prove control of funds.

Should I enter hex characters or raw bytes?

Select Hex when the input contains textual hexadecimal values. Select Raw bytes for actual byte data. Confusing those modes encodes the characters of the hex string instead of the bytes that the string describes.