File Downloaded Successfully!

Your file is saved and ready. Thank you for using Elixuvo!

🔒 100% Client-Side Processing•Always Fast & Free
Skip to content
Elixuvo

Base64 & URL Encoder / Decoder

Encode and decode text, tokens, and web URIs to and from Base64 and percent-encoding with full UTF-8 Unicode support. 100% private in-browser tool.

Live

How to use this tool

  1. Select your target codec: Base64 or URL (Percent-encoding).

  2. Choose your conversion direction: Encode or Decode.

  3. Type or paste your text into the Input pane, or click 'Upload File / Image' to convert files directly into Base64 Data URIs.

  4. If using Base64, optionally toggle 'URL-Safe Base64' for tokens and query parameters, or 'Data URI Prefix' for HTML/CSS embedding.

  5. Inspect the real-time output generated instantaneously with live size metrics and image preview.

  6. Click 'Copy Result' or 'Download as .txt' to save your encoded or decoded payload.

Frequently asked questions

Quick answers about file privacy, processing modes, formats, and device support.

Standard browser `btoa` and `atob` functions only accept 8-bit Latin-1 characters and throw errors on Unicode characters. Elixuvo uses the TextEncoder and TextDecoder Web APIs to convert text to UTF-8 byte arrays before encoding, ensuring emojis (🚀), accented characters, and non-Latin scripts (Arabic, Chinese, Japanese) convert without corruption.
Yes! You can upload any image or file using the file selector. The tool reads the file locally using the browser FileReader API and generates a complete Data URI (e.g. 'data:image/png;base64,...') ready for inline embedding in CSS stylesheets, HTML img tags, or JSON payloads.
Standard Base64 uses '+' and '/' characters, which have special meanings in web URLs and query strings. URL-safe Base64 replaces '+' with '-' and '/' with '_', and omits trailing '=' padding to prevent URI parsing conflicts in web applications and JWT tokens.
URL percent-encoding converts reserved and non-ASCII characters into '%XX' hexadecimal escape sequences (e.g., spaces become '%20' or '+', and '&' becomes '%26'), ensuring valid query parameters and request URLs.
Decoding errors happen when the input string is not a valid Base64 string (contains illegal characters, wrong length, or corrupted padding) or contains malformed percent-escape sequences. The tool catches these gracefully and reports the syntax fault.
Zero. Everything is processed 100% locally on your computer inside your web browser sandbox. Your tokens, API keys, uploaded files, and sensitive texts never leave your device.