Online Base64 Encoder

    Encode text or files to Base64. Choose Standard, URL-safe, or MIME output.

    Levels
    1
    Input
    1234567891011121314
    OutputBase64
    1234567891011

    JsonifyTools · Base64 Encoder

    Encode text or files. Get the format your workflow expects.

    Encode UTF-8 text or files to Base64 online. Choose Standard, URL-safe, or MIME output, check the size, then copy or download the result.

    Base64 encoder onlineText to Base64File to Base64Base64URLMIME Base64UTF-8 Base64

    The format in a minute

    What is Base64 encoding?

    Base64 represents bytes as printable text for text-only fields and transports, such as a binary file value in JSON or an email attachment. It does not compress data: three input bytes become four output characters, so the result is about one-third larger.

    Standard uses letters, digits, plus, and slash; equals signs may pad the end. URL-safe swaps plus and slash. MIME adds mail-compatible line breaks.

    Text is converted through UTF-8 first, so accents and emoji are encoded as bytes rather than rejected as non-ASCII input.

    Byte groups become text

    A simplified view of the conversion

    Input bytes (hex)

    48 · 69

    Base64 output

    SGk=

    Two bytes need one padding character here. Padding helps represent the final partial group.

    Choose a variant

    Standard, URL-safe, or MIME Base64?

    Choose the alphabet and line format expected by the receiving system.

    +/=

    Standard

    Use the common alphabet for JSON fields and systems that specify standard Base64.

    -_ =

    URL-safe

    Replaces + with - and / with _. This tool retains any = padding.

    76 chars / line

    MIME

    For mail workflows expecting MIME output, lines wrap at 76 characters with CRLF.

    Input → output

    Base64 encoder examples

    Examples show padding, JSON text, and URL-safe character changes.

    Text to Base64

    Encode a short message

    Input

    Hello, world!

    Encoded

    SGVsbG8sIHdvcmxkIQ==

    The final equals signs are padding for the last partial byte group.

    JSON to Base64

    Carry a compact JSON value as text

    Input

    {"id":42}

    Encoded

    eyJpZCI6NDJ9

    It encodes the text as entered; it does not validate the JSON.

    URL-safe characters

    Encode Unicode using URL-safe Base64

    Input

    ÿÿ

    Encoded

    w7_Dvw==

    Standard output is w7/Dvw==. URL-safe replaces / with _; this tool keeps padding when present.

    A quick workflow

    How to encode text or a file to Base64

    The encoder updates as you type or load a file, so there is no separate conversion step.

    1. 01

      Choose Text or File

      Paste text or select a file up to 50 MB using the File tab.

    2. 02

      Set the output format

      Choose Standard, URL-safe, or MIME. Keep Levels at 1 unless your workflow requires repeated encoding.

    3. 03

      Copy or download

      Review size stats, then copy the full value or download it as a .b64 file. Expand long previews when needed.

    Built into the encoder

    A practical Base64 tool for developer workflows

    Text and files

    Encode UTF-8 text or files up to 50 MB.

    Variants and levels

    Choose Standard, URL-safe, MIME, or one to five passes.

    Size and preview

    Review byte counts and long output; inputs over 1 MB use a background worker when available.

    Copy or download

    Copy the full result or save a .b64 file.

    A developer workflow

    When a URL breaks an otherwise valid payload

    An image API accepts Base64 inside JSON, but another workflow puts a value in a URL. Standard Base64 characters + or / can be interpreted as URL syntax, so only some requests fail.

    They choose URL-safe for the URL field and check the API contract. The bytes stay the same; the alphabet changes. They confirm padding and size requirements before shipping.

    Same bytes, URL-safe alphabet

    Standard

    w7/Dvw==

    URL-safe

    w7_Dvw==

    This encoder swaps the alphabet characters and retains = padding. Follow the target service’s exact Base64URL requirements.

    Where Base64 fits

    Common Base64 encoding use cases

    Use Base64 when a receiving format asks for encoded bytes, not as a replacement for ordinary files or text.

    API payloads and token tests

    Encode binary data for API fields that require it, or test JSON in URL-safe form. This encoder does not assemble or sign JWTs.

    Small files and data URIs

    For inline assets, prepend the correct media type, such as data:image/png;base64, to the image output.

    MIME and email workflows

    Choose MIME for mail workflows that expect 76-character lines; use Standard for a single-line value.

    QA and multi-pass pipelines

    Repeat encoding up to five passes to reproduce nested payloads or test decoders. Extra passes add no security.

    Base64 is not encryption

    Encoding only changes how bytes are represented. It does not hide or protect them, require a key, or prove where a value came from. Do not put credentials or private information in Base64 as a security measure. For a Basic Authentication header, Base64 is only the representation; protect the connection with HTTPS and follow the API’s authentication guidance.

    Quick answers

    Base64 encoder FAQs

    What does a Base64 encoder do?

    It converts bytes to printable characters for text-based formats. This page encodes text and files; decoding is a separate operation.

    Is Base64 the same as encryption?

    No. It uses no secret key and anyone can reverse it. Do not use Base64 to hide passwords, tokens, or private data.

    What is the difference between Standard, URL-safe, and MIME Base64?

    Standard uses + and /; URL-safe substitutes - and _. MIME wraps lines at 76 characters. This encoder retains URL-safe padding; check the receiving format.

    Can I encode Unicode text such as accents or emoji?

    Yes. Text is converted to UTF-8 before encoding. Decode as UTF-8 to recover the same accented characters or emoji.

    Can I encode a file here?

    Yes. Choose File and select or drop a file up to 50 MB. Copy the full output or download it as a .b64 file.

    Why is Base64 output larger than the input?

    Each 3 input bytes become 4 output characters, plus any padding. The result is roughly one-third larger before line wrapping.