Encode and decode text as Base64, URL (percent-encoding) and HTML entities, with bulk mode, all in your browser.
Encoding text means converting characters into a format that is safe to transport or store. This tool covers the three encodings developers reach for most. Base64 turns bytes into ASCII text (A–Z, a–z, 0–9, + and /), ideal for embedding binaries in JSON, e-mail or data URIs; the URL-safe variant swaps + and / for - and _ and drops the = padding, for use in URLs and JWTs. URL encoding (percent-encoding) escapes reserved characters such as space, &, ? and accents so they travel safely in query strings, encodeURIComponent escapes a single isolated value, while encodeURI preserves the structure of a whole URL. HTML entities convert <, >, &, quotes and symbols into <, >, & and so on, preventing the browser from interpreting the text as markup (a basic defense against display XSS). Every operation handles UTF-8 correctly (accents, emoji) and a bulk mode processes each line independently.
Paste the code into your HTML and the tool shows up on your page, without J-Kit's navigation and ads. It still runs in the browser of whoever visits your site.
<iframe
src="https://jkit.tools/embed/en-US/base64-url-html-encoder"
width="100%"
height="600"
style="border:0"
loading="lazy"
title="Base64, URL & HTML Encoder"
></iframe>These references help contextualize formulas, standards, APIs and limitations used on this page. They do not replace professional validation when a result has legal, financial, medical or operational impact.
Standard Base64 uses the + and / characters and pads the end with = (padding). Because +, / and = have meaning in URLs, the URL-safe variant (defined in RFC 4648) replaces them with - and _ and removes the padding, letting you use the result in URLs, file names and tokens such as JWTs without escaping anything. Decoding here accepts both variants automatically.
All encoding and decoding happens in your browser. No text is sent to any server, safe for tokens, payloads and sensitive data.