Base64, Hex & URL Encoder–Decoder — Local UTF-8

Base64 Hex URL encoder decoder — VH Original

Encode or decode UTF-8 text as standard Base64, hexadecimal bytes or a URL component in your browser. No external API, account or saved history.

Convert text between readable UTF-8 and common transport encodings. Select Base64, Hex or URL component, choose Encode or Decode and enter your input. The result can be copied or downloaded as a plain text file. This tool processes text locally; it does not send the input to an API.

How to use

The sample contains English, Hindi and an emoji so you can check Unicode handling. Generate an encoded result, copy it back into Input text, switch to Decode and generate again. Changing any input or option clears the old result, so a previous conversion cannot be mistaken for the current settings.

Base64 Hex URL encoder decoder — VH Original
Tool illustration — VH Original

Calculation and process

Base64 mode uses the standard alphabet with + and /, and requires canonical padding on decode. It is not a Base64url JWT decoder. Hex mode represents each UTF-8 byte with two hexadecimal digits. It accepts upper or lower case and ignores whitespace when decoding, but rejects odd digit counts and invalid digits.

Output and downloads

URL component mode uses encodeURIComponent and decodeURIComponent. It is intended for a single parameter value or path component. It does not parse a whole URL or produce application/x-www-form-urlencoded data. A plus sign remains a plus sign during decode; use %20 for a space.

Limits

Decoded Base64 or Hex must contain valid UTF-8 text. Binary images, archives and arbitrary bytes are outside this text tool’s scope and can trigger an error. Malformed percent escapes, noncanonical Base64 and unpaired Unicode surrogates are rejected instead of silently returning misleading text. The input limit is 200,000 UTF-16 units.

Advice

Encoding changes representation; it is not encryption, password protection or anonymization. For a round trip, keep the same format and select the opposite direction. Choose the dedicated JWT inspector for three-part JWTs. Validate the result against the consuming application’s expected encoding before using it.

Frequently asked questions

Is Base64 encryption?

No. Anyone can decode it without a secret key.

Does it support Hindi and emoji?

Yes. Valid Unicode text is converted through UTF-8 bytes.

Why does a binary Base64 file fail?

This tool decodes text only and rejects bytes that are not valid UTF-8.

Does URL decode turn + into a space?

No. It decodes URL components; %20 represents a space.

More free tools