URL Encoder

Percent-encode URLs or query string values for safe use in links, forms, and APIs. Choose between encoding a full URL or just a query string value. See also: URL Decoder.

Runs in your browser · No data sent anywhere
Input
Encoding mode
Encoded output
Copied!
Related Tools
URL Decoder
encode
Decode percent-encoded URLs and query strings back to readable text. Handles %20, Unicode escapes, and malfor…
Base64 Encoder
encode
Encode text or files to Base64 online for free. Instant results, no signup, no limits. Supports URL-safe Base…
URL Slug Generator
text
Convert any text to a clean URL slug instantly. Handles accents, special characters, and spaces. Free online …
Hash Generator
encode
Generate MD5, SHA-1, SHA-256, and SHA-512 hashes from text or files online. Free, instant, runs in your brows…

Query value vs. Full URL mode

  • Query value — encodes everything including /, ?, &, =. Use for individual parameter values.
  • Full URL — preserves /, ?, &, = and other URL structure characters. Use for encoding an entire URL for embedding.

Common encoded characters

  • Space → %20 (or + in forms)
  • @ → %40
  • # → %23
  • & → %26
  • = → %3D
  • + → %2B

Frequently Asked Questions

What's the difference between %20 and + for spaces?

Both represent a space in URLs, but in different contexts. %20 works everywhere. The + sign is only valid in query strings (application/x-www-form-urlencoded format) and won't be decoded as a space in URL paths.

Which characters don't need encoding?

Unreserved characters never need encoding: A–Z, a–z, 0–9, hyphen (-), underscore (_), period (.), and tilde (~).

Why would I need to URL encode something?

URLs can only contain certain safe characters. Special characters in parameter values (like & or = or non-ASCII text) must be percent-encoded to avoid being misinterpreted as URL syntax.