Encode and decode URLs
Paste a URL or query string to encode it, or paste an encoded URL to decode it back to readable form.
Settings
Choose mode and encoding type.
Encoded output
Output will appear here.
Why this tool exists
Vultio URL Encoder / Decoder encodes plain text and URLs using standard percent-encoding, or decodes percent-encoded strings back to readable form, entirely in your browser.
URL encoding is essential when working with query parameters, API request building, link sharing, and debugging HTTP requests where special characters must be safely represented.
Common use cases
- Encode query parameter values before appending them to a URL to avoid breaking the URL structure.
- Decode a percent-encoded URL you received in an API response or browser address bar.
- Encode a full URL for use as a redirect_uri or callback parameter in OAuth flows.
- Debug API endpoints by decoding complex encoded query strings into readable parameters.
- Prepare safe URLs for embedding in HTML href attributes or HTTP headers.
Example input / output
Encode a query parameter value (Component mode)
Input
Output
Encode a full URL (Full URL mode)
Input
Output
Decode a percent-encoded query string
Input
Output
Common errors
Error: input is not a valid encoded URL.
Cause: The string contains a malformed percent sequence such as %GH or a lone % character that is not followed by two valid hex digits.
Fix: Check that all percent signs are part of valid sequences (% followed by exactly two hex characters A–F or 0–9). Switch to Encode mode if you meant to encode the text.
Encoded output breaks the URL structure unexpectedly.
Cause: Using Component mode on a full URL encodes the / and ? characters, which destroys the URL structure.
Fix: Switch to Full URL mode when encoding a complete URL. Use Component mode only for individual query parameter values or path segments.
Space appears as + instead of %20.
Cause: Some older systems and form submissions use application/x-www-form-urlencoded format, which replaces spaces with +.
Fix: This tool follows the standard RFC 3986 percent-encoding spec (%20 for spaces). If you need + encoding for form data, replace %20 with + after encoding.
Related guides
A practical reference for diagnosing and resolving the most frequent URL encoding mistakes in APIs and web applications.
Understand when Base64 is the right encoding choice compared to URL encoding.
Related tools
Encode text to Base64 or decode Base64 back to plain text, entirely in the browser.
Format raw JSON to make it easier to inspect.
Generate passwords, API keys, and JWT secrets.
Frequently asked questions
What is URL encoding?
URL encoding replaces special characters with percent-encoded sequences so they can be safely included in URLs. For example, a space becomes %20.
What is the difference between component and full URL encoding?
Component encoding (encodeURIComponent) escapes all special characters including /, ?, and &, making it suitable for query parameter values. Full URL encoding (encodeURI) preserves structural characters like /, ?, and & that have meaning in the URL.
Does URL encoding send data to a server?
No. This tool processes everything client-side in your browser. Nothing is sent to any server.
When should I use URL Encoder?
Use it when building query strings, debugging encoded API endpoints, or when you receive a URL with percent-encoded characters and need to read it clearly.