Base64 & URL encoder
ClientThis workspace handles Base64 (UTF-8 bytes) and URL component encoding (encodeURIComponent / decodeURIComponent) so query keys and values round-trip safely. For whole URLs, encode only the values that need it—not the full URL string.
Part of encoding tools.
Workspace
Paste text, run an action—output replaces the field for a quick copy. Decoding Base64 assumes UTF-8 text; binary that is not valid UTF-8 will show an error.
Base64
?
Encode or decode using UTF-8 bytes so Unicode text round-trips correctly. Processing is local in your browser.
Decoding arbitrary binary to UTF-8 may fail if the payload is not text.
URL encoding
?
Uses encodeURIComponent and decodeURIComponent for query strings and path segments. Runs entirely on the client.
For full URLs, encode only the pieces that need escaping—encoding an entire URL can break the scheme.
Nearby workflows on Toolcore
- Base64url — when JWT segments or URL-safe alphabets forbid + and /.
- Data URL — when inline data: URIs wrap Base64 payloads.
- URI encoding — when you must choose encodeURI vs encodeURIComponent.
- JWT decode — after transport encoding reveals header and payload JSON.
Common use cases
- Encode query parameter values safely before appending them to URLs.
- Convert UTF-8 text to Base64 for transport or test fixtures.
- Decode Base64 text that represents UTF-8 strings—not arbitrary binary blobs.
Common mistakes to avoid
Encoding entire URLs with component functions
Use component encoding for parameter values, not for the full URL. Encoding separators can break routing.
Confusing Base64 with encryption
Base64 is reversible encoding for transport, not a security mechanism.
Ignoring UTF-8 assumptions during decode
Decoding binary payloads as text can fail. Use text-oriented Base64 only when the source is UTF-8 content.
FAQ
When should I use URL encoding here?
Use it when a value contains spaces, symbols, or non-ASCII characters and will be placed in a query string.
Can I use this page for cryptographic protection?
No. This page handles encoding and decoding. Use the encrypt/decrypt tool when you need cryptographic operations.
Does encoding run on the server?
No. Base64 and URL operations in this workspace run in your browser tab.
Can assistants open this page with text already filled in?
Yes. Copy agent link creates a prefilled Toolcore URL for the current text, then the browser page handles Base64 or URL actions locally.
Common search terms
Phrases people search for that match this tool. See the full long-tail keyword index.
- base64 encode online
- base64 decode online
- url encode decode online
- encode uri component online
More tools
Related utilities you can open in another tab—mostly client-side.
HMAC (SHA-256 & more)
ClientHMAC-SHA-256/384/512/1 in the browser—hex or Base64 for webhooks, signing, and API docs.
Encoding tools
ClientHub index: Base64 & URL, Base64url, Base32, Crockford, LEB128, ASCII85, Z85, Base58, base-36, bencode, Morse, quoted-printable, URI, Punycode/IDN, Unicode escapes, data URLs, MIME, hex, HTML entities, JWT, JSON helpers, crypto.
Base64url (URL-safe) encode & decode
ClientUTF-8 ↔ Base64url (RFC 4648: -, _, padding optional on decode)—same bits as Base64, JWT-segment style; client-side.
Subresource Integrity (SRI)
ClientSHA-256/384/512 base64 integrity tokens for script and link tags—UTF-8 paste or local file; Web Crypto only.