--- title: Base64 Encode and Decode: Free Online Tool | Relic description: Free Base64 encoder and decoder. Convert text to Base64 or decode Base64 back to text, with full UTF-8 support, right in your browser. Nothing is uploaded. canonical: https://relic.space/tools/base64 source: https://relic.space/llms.txt --- # Base64 Encode and Decode Encode text to Base64 or decode it back to plain text, instantly and privately. Full UTF-8 support, nothing uploaded. Runs entirely in your browser. Nothing you type is uploaded. Plain text Base64 output Result appears here… ## Base64, both directions Base64 turns any text into a safe string of letters, numbers, and a couple of symbols, which is how data tends to ride inside JSON, data URLs, email, and config files. This **Base64** tool encodes and decodes with full UTF-8 support, so emoji and accented characters survive the round trip. Flip the toggle, paste your text, and copy the result. Everything happens in your browser, so nothing you paste leaves your device. ## Stop pasting the same token twice If you decode a payload, you usually need it again an hour later. **Relic** keeps an end-to-end encrypted history of everything you copy, searchable on every device, so that token, key, or snippet is one search away instead of a scroll through your terminal. The encoder is free. The memory is the upgrade. **Learn:** why does Base64 exist at all, and why is it not encryption? Read [What is Base64 encoding?](https://relic.space/blog/what-is-base64-encoding) ## Frequently asked questions What is Base64 encoding?+ Base64 turns any data into a string of 64 safe characters (letters, digits, plus, slash) so it can travel through systems built for plain text, like email, JSON, or URLs. It is encoding, not encryption. How do I decode a Base64 string?+ Paste it into the decode box and the original text appears instantly, with full UTF-8 support, so accents, emoji, and non-Latin scripts round-trip correctly. Is Base64 encryption? Is it secure?+ No. Anyone can decode Base64, no key required, so it hides nothing. If you need actual secrecy, use real encryption, like our encrypt text tool or an end-to-end encrypted store. Why does Base64 output end with = signs?+ Base64 works in 3-byte blocks. When your input is not a multiple of three bytes, one or two = characters pad the final block, so trailing equals signs are normal and expected. Where is Base64 used in practice?+ Data URLs for inline images, email attachments (MIME), JWT tokens, basic HTTP authentication, and anywhere binary data has to survive a text-only channel. You just copied that. What if you never lost it? **Relic** remembers everything you copy, forever, searchable on every device, and end-to-end encrypted so only you can read it. 250 MB free [Download forWindows](https://relic.space/download/windows)[Download formacOS](https://relic.space/download/macos)[Download forLinux](https://relic.space/download/linux)[Download forAndroid](https://play.google.com/store/apps/details?id=relic.space.app&referrer=utm%5Fsource%3Drelic.space%26utm%5Fmedium%3Dwebsite%26utm%5Fcampaign%3Dcontent)[Download foriPhone](https://apps.apple.com/us/app/relic-clipboard-vault/id6800556025) More free tools [JSON Formatterjson formatter](https://relic.space/tools/json-formatter)[Diff Checkerdiff checker](https://relic.space/tools/diff-checker)[URL Encode / Decodeurl decoder](https://relic.space/tools/url-encode-decode)[UUID Generatoruuid generator](https://relic.space/tools/uuid-generator)[Epoch Converterepoch converter](https://relic.space/tools/epoch-converter)[Regex Testerregex tester](https://relic.space/tools/regex-tester)[All tools](https://relic.space/tools)