Skip to content
uencoder
PIPELINE Encoding & Decoding Beginner 2 steps

Convert Base32 to Base64

Base32 is used in DNS-based authentication (DKIM, SPF) and TOTP secrets because it is case-insensitive and safe in URLs. Base64 is roughly 20% more compact. This chain decodes Base32 to bytes then encodes as Base64, useful when migrating secrets or tokens into a system that prefers Base64.

What it solves

Decode a Base32-encoded string into raw bytes and re-encode as Base64 for more compact representation.

Input → Output

Base32 Decoder input → Base64 Encoder output across 2 steps.

Runs in

1–2 minutes · fully local in your browser.

Before you start

  • A valid Base32-encoded string (A-Z, 2-7, optional padding)

The pipeline

  1. 1 Base32 Decoder base32-decode

    Decode Base32 (RFC 4648) back to readable text online. Free, private, and 100% client-side.

  2. 2 Base64 Encoder base64-encode

    Encode text or binary data to Base64 online. Free, private, and 100% client-side.

Open in Toolchain

Runs locally in your browser. The recipe defines the pipeline only — your input never leaves this tab.

▶Run this workflow

Enter your input below and click Run. All processing happens locally in your browser — nothing is uploaded.

Pipeline progress

  1. Base32 Decoderbase32-decode
  2. Base64 Encoderbase64-encode

Sample input

JBSWY3DPEHPK3PXP

Expected output

SGVsbG8h3q3vv73vv70=

This pair is executed against the real tools at build time (tests/unit/recipes.test.ts) — the expected output is verified, not illustrative.

Related workflows

You might also need

Workflows sharing tools or topics with this recipe.

Learn more

Tools used