BASE64 ENCODE ============= Use Base64 Encode to convert text to Base64. This Base64 encoder also accepts Hex bytes or Base64 input through Input Encoding: and copies standard output. Base64 Encode represents text or entered bytes as a standard Base64 string. Use this Base64 encoder to prepare test data for a field that expects Base64. Input Encoding: controls which bytes are encoded, so the same visible characters can produce different results under different settings. OVERVIEW & METADATA ------------------- Canonical URL: https://million.tools/base64-encode/ Markdown Copy (.md.txt): https://million.tools/base64-encode.md.txt Plain Text Copy (.txt): https://million.tools/base64-encode.txt API Endpoint: https://million.tools/api/v1/run/base64-encode (POST, Keyless, 60 req/min) SEO Title: Base64 Encode Online | Convert Text to Base64 Alternative Names: Text to Base64, Base64 Encoder, Text to Base64 converter, String to Base64 encoder, Standard Base64 encoder Category: Encoding (https://million.tools/encoding/) Tags: #Base64 Application Category: DeveloperApplication Platform: Web (All modern desktop and mobile browsers, requires JavaScript) Price: Free ($0.00 USD, no registration or sign-up required) Live Calculation: Supported (Auto / Live toggle enabled by default) Usage Statistics: 4 views Published: 2026-11-17 Last Updated: 2026-11-17 Author: Egor Volchenko (Developer & Author) KEY FEATURES ------------ - Encode entered text or bytes as standard Base64 - Select UTF-8 or additional text input encodings - Interpret entered bytes as Hex or Base64 - Produce standard Base64 padding where needed - Update edited input with Auto / Live or Run - Copy encoded output and clear text PARAMETERS & INTERFACE CONTROLS ------------------------------- Input Parameters & Options: - input_text: Plain Text String. - input_encoding: Hex | Hex (Ignore Non-Hex Characters) | Base64 | UTF-8 | UTF-16LE | UTF-16BE | Windows-1251 (Cyrillic) | Windows-1252 (Latin 1) | ... (42 options) Output Fields & Metrics: - result: Base64 Encoded Result. Controls: Run, Clear, Copy, Fill test data, Auto / Live INTERACTIVE EXAMPLE (TEST VECTOR) --------------------------------- Settings: - Input Encoding: UTF-8 Plain Text String: foobar Base64 Encoded Result: Zm9vYmFy HOW TO USE BASE64 ENCODE ------------------------ Follow these steps to check the input and read the result. Encode text as standard Base64: 1. Enter your input: Type or paste the text or byte representation you want to encode into Plain Text String. 2. Check the input setting: Set Input Encoding: to UTF-8 for ordinary text. Choose Hex for entered hexadecimal bytes, or Base64 when the input already represents Base64-encoded bytes. 3. Process the input: Keep Auto / Live on to update the result as you edit. To process it manually, turn Auto / Live off and click Run. 4. Review the result: Read Base64 Encoded Result and check the result before using it. 5. Copy or clear: Click Copy to copy the result. Use Clear where shown, or a field’s clear control, to clear the text before starting again. With Input Encoding: set to UTF-8, Hello produces SGVsbG8=. With Hex selected, 48656c6c6f produces the same result. Choose bytes before choosing a representation: UTF-8 converts the entered characters to bytes before Base64 encoding. Hex 48656c6c6f represents the bytes of Hello; the same digits under UTF-8 represent ten text characters. Additional text encodings are available in Input Encoding: for compatibility testing. Use standard output in the correct context: Output uses the standard Base64 alphabet and padding where needed. It is not automatically URL-safe, and the form has no output variant selector, file upload, or MIME line-wrapping control. Encode bytes from Hex: Use the input selector when you already have a byte representation rather than plain text. 1. Choose Hex in Input Encoding:. 2. Enter 48656c6c6f in Plain Text String. 3. Keep Auto / Live on or click Run, then copy SGVsbG8= from Base64 Encoded Result. FREQUENTLY ASKED QUESTIONS -------------------------- Q: Is Base64 a secure way to hide text? A: No. Base64 is encoding, not encryption. It changes the representation of bytes without a secret key and can be decoded by anyone. Q: Why does the input encoding change my result? A: Base64 represents bytes. UTF-8, Hex, and other input settings can interpret the same visible input as different byte sequences, producing different Base64 strings. Q: Can I convert Hex bytes to Base64? A: Yes. Select Hex in Input Encoding: and enter the hexadecimal bytes. For example, 48656c6c6f encodes to SGVsbG8=. Q: Does this generate Base64URL? A: No. The result uses standard Base64. There is no Base64URL, custom-alphabet, IMAP, or UTF-7 output option in the current form. Q: What happens if I select Base64 for the input? A: Valid Base64 input is decoded to bytes and then encoded as standard Base64 again. It does not encode the visible Base64 characters as ordinary text. Select UTF-8 if that is what you need. Q: Can I upload a file to this form? A: This form accepts entered text or a byte representation. It does not include file upload or file download controls. RELATED TOOLS ------------- - Base64 Decode (https://million.tools/base64-decode/): Decode a standard Base64 string to UTF-8 text. Accept padded or unpadded input, inspect the decoded result, and copy it for testing. - URL Encode (https://million.tools/url-encode/): Percent-encode a URL component or text value using UTF-8. Convert spaces, plus signs, and reserved characters before inserting a value into a URL. - URL Decode (https://million.tools/url-decode/): Decode percent-encoded text and URL components. Convert UTF-8 byte escapes to readable text while preserving literal plus signs. - JWT Decoder (https://million.tools/jwt-decoder/): Inspect a JSON Web Token’s decoded header and payload. Read claims as JSON for debugging; decoding does not verify the signature or token validity. - Base58 Encode (https://million.tools/base58-encode/): Encode text or supplied bytes with the Bitcoin-style Base58 alphabet. Choose the input representation and copy the resulting Base58 string. ABOUT THE AUTHOR ---------------- Egor Volchenko — Developer & Author Hi! I’m a WordPress developer with over 10 years of experience. I love Tailwind CSS, clean code, and intuitive interfaces. I’m currently working on million.tools — a service with convenient online tools for everyday tasks. I’m building it from scratch with great attention to detail and user experience. Links: x.com (https://x.com/egorleet) | github.com (https://github.com/egorleet) | t.me (https://t.me/egorleet) | instagram.com (https://www.instagram.com/egorleet) | facebook.com (https://www.facebook.com/egorleet/) | egorleet.blog (https://egorleet.blog/) | mastodon.social (https://mastodon.social/@egorleet) | twitch.tv (https://www.twitch.tv/egorvolchenko) | stackoverflow.com (https://stackoverflow.com/users/31679135/egor-volchenko) | reddit.com (https://www.reddit.com/user/Vegetable_Window9185/) | youtube.com (https://youtube.com/@egor-volchenko)