What is URL encoding?

URL encoding (percent-encoding) replaces unsafe characters with a % followed by two hex digits. For example, a space becomes %20 and an ampersand becomes %26. This ensures special characters don't break URL parsing.

Which characters need to be URL-encoded?

Characters that have special meaning in URLs must be encoded: spaces, &, =, ?, #, /, @, and non-ASCII characters. Letters, digits, and - _ . ~ are safe and don't need encoding.

How do I encode a URL parameter?

Paste the parameter value (not the entire URL) and click Encode. For example, if your search query is 'hello world & more', encoding produces 'hello%20world%20%26%20more', which is safe to use in a URL query string.

What's the difference between encodeURI and encodeURIComponent?

encodeURI encodes a full URL but preserves URL-structural characters like :, /, ?, #, &. encodeURIComponent encodes everything except letters, digits, and - _ . ~ — use it for individual parameter values.

URL kodieren / dekodieren

URL-Komponenten sicher kodieren und dekodieren

Input

Loading editor...

Output

Loading editor...

Encode URL components without breaking your queries

Special characters — spaces, ampersands, slashes, non-ASCII letters — break query strings if they're not percent-encoded. The right tool for the job depends on whether you're encoding a full URL or a single component, and choosing wrong is a frequent source of bugs. This tool handles both cases and shows you exactly what each character becomes.

Use the tool when you need to

Encode a query parameter value

Percent-encode a search term, slug, or special string before slotting it into a query string.

Decode a URL from a log

Reverse %20, %2F, and other escapes to read what the request actually contained.

Audit an OAuth or callback URL

Check that the redirect, scope, and state parameters are encoded correctly before debugging the flow.

How to encode or decode URL components

1
Paste the URL or component into the input area.
2
Click Encode or Decode based on which direction you need.
3
Copy the result and slot it back into your URL or test request.

Keep going

Encode binary as Base64

Pick Base64 when the goal is binary safety rather than URL safety.

Format JSON URLs

Pretty-print payloads that contain encoded URLs as values.

Decode JWTs

Decode auth tokens that may travel through URL parameters.

Validate JSON

Validate JSON bodies that include URL fields.

Common URL-encoding workflows

Build a search redirect

Encode the user's query before constructing the destination URL to avoid breaking on spaces or symbols.

Read a redirect from logs

Decode a logged URL to confirm what the user clicked and which parameters arrived.

Verify an OAuth state parameter

Decode the state to confirm it round-trips through the auth provider untouched.

Häufig gestellte Fragen

URL-Encoding (Percent-Encoding) ersetzt unsichere Zeichen durch ein % gefolgt von zwei Hex-Ziffern. Zum Beispiel wird ein Leerzeichen zu %20 und ein kaufmännisches Und (&) zu %26. So wird verhindert, dass Sonderzeichen das Parsen von URLs kaputt machen.

Zeichen mit spezieller Bedeutung in URLs sollten encodiert werden: Leerzeichen, &, =, ?, #, /, @ sowie Nicht-ASCII-Zeichen. Buchstaben, Ziffern und - _ . ~ gelten als sicher und müssen nicht encodiert werden.

Füge den Parameterwert ein (nicht die komplette URL) und klicke auf Encode. Beispiel: Aus 'hello world & more' wird 'hello%20world%20%26%20more' — das ist sicher für eine Query-String-Parameter-Value.

encodeURI kodiert eine komplette URL, lässt aber strukturelle URL-Zeichen wie :, /, ?, #, & stehen. encodeURIComponent kodiert alles außer Buchstaben, Ziffern und - _ . ~ — das ist die richtige Wahl für einzelne Parameterwerte.