Zum Inhalt springen
Toolza

Diese Seite ist noch nicht vollständig übersetzt, daher erscheinen einige Texte auf Englisch.

URL Encoder and Decoder

Percent-encode text so it's safe to put in a URL, decode garbled links back into readable text, and break a URL into its parts to inspect its query parameters.

Ihre Dateien bleiben auf Ihrem Gerät. Ihre Eingaben hier werden nicht an unsere Server gesendet.

So verwenden Sie URL kodieren / dekodieren

  1. 1Paste the text or URL you want to work with.
  2. 2Choose component encoding for a query value, or full-URL encoding for a complete address.
  3. 3Click Encode or Decode.
  4. 4Use the parser to see the protocol, host, path and every query parameter in a table.

Wichtigste Funktionen

URLs can only contain a limited set of characters. Anything else, such as spaces, accented letters, many symbols or non-Latin scripts, has to be percent-encoded: converted to UTF-8 bytes, with each byte written as % followed by two hex digits. Characters like ?, & and = also have special meaning in a URL, so they must be encoded when they appear inside a value rather than as structure.

Choosing the right mode prevents subtle bugs. If you encode a whole URL with component mode, its slashes and colons become %2F and %3A and the link stops working. If you build a query string with full-URL mode, an & inside a value isn't encoded and will be mistaken for the start of a new parameter.

The parser is useful for debugging marketing links, redirects and API calls. Seeing each query parameter decoded in a table makes it easy to spot a missing value, a double-encoded string or a tracking parameter you didn't expect.

Häufig gestellte Fragen

Use component encoding for a single piece that goes inside a URL, such as a search term or a parameter value. Use full-URL encoding when you have a complete URL with spaces or special characters and want to keep its slashes, colons and question mark working.

Spaces aren't allowed in URLs, so they're replaced with %20, the hexadecimal code for a space. Some forms use + for spaces in query strings; that's a different convention.

The text contains a % that isn't followed by a valid two-digit hex code, or a sequence that isn't valid UTF-8. Check for stray % signs or a link that was cut off partway.

Characters outside basic ASCII take several bytes in UTF-8, and each byte becomes a %XX code. For example, é becomes %C3%A9.

No. Encoding, decoding and parsing all happen in your browser.