Base64 & Base32 Encoder/Decoder Tools
Base32 Converter
Encode and decode Base32 for TOTP 2FA secrets, DNS records, and Tor addresses. RFC 4648 compliant. Free online Base32 converter.
Base64 Decode
Decode Base64 strings to text or download as file. Supports UTF-8, binary data, and data URIs. Auto-detects content type. Free, private, works offline.
Base64 Encode
Encode any text to Base64 format instantly. Supports UTF-8, Unicode, emojis, and special characters. Real-time encoding with size stats. Free and private.
Base64 To Image
Convert Base64 strings to images and download as PNG, JPG, or other formats. Paste data URI or raw Base64, preview instantly, and save. Free, private, offline.
File To Base64
Convert any file to Base64 encoding. Encode PDFs, documents, audio, video, or any binary file. Get data URI or raw Base64 for APIs. Private, offline.
Image To Base64
Convert images to Base64 data URIs for embedding in HTML and CSS. Supports PNG, JPG, WebP, SVG, GIF. Get instant data URI, raw Base64, or ready-to-use code.
Inline Image Email
Create inline Base64 images for email templates. Generate data URIs, HTML img tags, and Outlook-compatible VML code. Check email client compatibility instantly.
Base64 Encoding
Base64 converts binary data into a text string using 64 safe characters (A-Z, a-z, 0-9, +, /). This enables binary data like images and files to be embedded in text-only contexts like HTML, CSS, JSON, and email.
Data URIs
Data URIs embed files directly in HTML or CSS using the format data:[mediatype];base64,[data]. For example, a small icon can be embedded directly in CSS, eliminating an HTTP request:
background-image: url(data:image/png;base64,iVBORw0KG...)
Base32 Encoding
Base32 uses 32 characters (A-Z, 2-7) for case-insensitive encoding. It avoids confusing characters like 0/O and 1/I, making it ideal for manual entry.
TOTP/2FA Secrets
Two-factor authentication apps (Google Authenticator, Authy) use Base32 for secret keys. The 16-32 character keys you enter manually are Base32-encoded binary secrets used in HMAC-SHA1 code generation.
Other Base32 Uses
- Tor .onion addresses: 56-character v3 addresses are Base32-encoded public keys
- DNSSEC NSEC3: Uses Base32hex for hashed domain names
- File systems: Case-insensitive systems use Base32 for compatibility
Base32 Variants
RFC 4648: Standard alphabet (A-Z, 2-7) with = padding
Base32hex: Uses 0-9, A-V to preserve sort order
Crockford: Excludes I, L, O, U to avoid ambiguity and profanity