These three operations all change how text looks, but they solve different problems. A URL component needs escaping, Base64 represents bytes with a limited alphabet and a slug creates a readable path label. Choose the operation for the destination you are using.
Encode a component, not an entire URL
The URL tool uses encodeURIComponent. A query value containing spaces, accents or an ampersand can be encoded without confusing it with the URL’s separators. Encoding a complete URL would also escape its colon and slashes, so start with the individual value you need to pass.
Decoding uses decodeURIComponent and rejects malformed percent escapes or invalid UTF-8. A plus sign is not converted to a space; that convention belongs to form-urlencoded data, which has different rules.
Use Base64 for representation
The Base64 tool encodes UTF-8 text using the standard alphabet and padding. Decoding validates the format and requires the result to be valid UTF-8 text. It is designed for text rather than arbitrary binary files or Base64URL strings.
Base64 is easy to reverse. Do not use it to hide credentials or claim that encoded information has been encrypted. For sensitive information, choose an appropriate security workflow beyond these formatting tools.
Use a slug for a title-like path
The Slug Generator removes combining accents, lowercases text and uses hyphens between letter and number groups. “España: una guía útil” becomes “espana-una-guia-util”. Unicode letters from other scripts remain supported.
A generated value does not change a live link
The slug is a suggestion in a text box. It does not check uniqueness or update WordPress. If you change an already published permalink, manage any necessary redirects and check incoming links through your normal site administration process.