Skip to content
Docs navigationBrowse tools →

Tool docs

Base64 Encoder / Decoder

Encode and decode Base64 or Base64URL strings entirely in your browser. This guide explains where the tool helps, what can still go wrong, and how Birdor treats text, padding, and URL-safe variants.

Loading

Tool

Overview

01

Base64 Encoder / Decoder

Use the Base64 tool for quick text transforms, header and token debugging, config values, and URL-safe payloads. It keeps the workflow local and predictable, so you can inspect encoded values without copying them into another service.

Guide

Common usage patterns

01

Quick encode and decode workflow

  • Paste the raw text or encoded value you want to inspect.
  • Switch between standard Base64 and URL-safe Base64URL when the integration requires it.
  • Use encode or decode, then copy the result back into your code, headers, or config.
  • Double-check whether the other system expects UTF-8 text or raw bytes before treating the output as interchangeable.

Guide

Edge cases & common pitfalls

01

Padding, bytes, and invalid input

  • Some systems require padding with = while others omit it, especially in Base64URL flows.
  • Base64URL replaces + and / with - and _, so the same payload can look different across systems.
  • Binary payloads need byte-aware producers and consumers; text copy-paste is not always enough.
  • Invalid length or characters usually mean the value was truncated, escaped, or was never Base64 to begin with.

Internals

How it works internally

01

UTF-8 and browser-native transforms

Birdor treats the raw side as UTF-8 text, normalizes between Base64 and Base64URL locally, and prefers explicit errors over silent coercion. Nothing leaves the browser tab.