ENCODING WORKSPACE
URL Encoder / Decoder
Encode or decode URL text.
Input is processed on this site only when you run the tool. The application does not save inputs or results.
input.txt
Result result.txt
A little clarity goes here.
Run the tool to see your result.
Result preview
UTF-8 text, at most 262144 bytes per input. Tab leaves the editor. Plain text disables syntax colors. Browser textareas may normalize line endings to LF.
{"encode":{"inputMode":"text","options":{"mode":{"type":"enum","values":["component","form"],"default":"component"}}},"decode":{"inputMode":"text","options":{"mode":{"type":"enum","values":["component","form"],"default":"component"}}}}{"encode":{"input":"a+b &\/?","output":"a%2Bb%20%26%2F%3F","options":{"mode":"component"}},"decode":{"input":"a%2Bb%20%26%2F%3F","output":"a+b &\/?","options":{"mode":"component"}}}A QUICK WALKTHROUGH
A familiar workflow,
with room to focus.
Enter UTF-8 text or percent-encoded text.
Choose URL component or form/query mode, then Encode or Decode.
Use the result as one component; swap moves output back to input for an explicit next operation.
When to use URL Encoder / Decoder
Prepare one query value or path component that contains spaces, plus signs or reserved punctuation.
Read the result
Choose component mode for literal plus signs, or form mode when spaces map to +. Decode exactly once; the result is not a fetched address or a complete URL-safety check.
SEE IT IN PRACTICE
Worked examples
Sample input. A result you can inspect.
Encode example
Input
a+b &/?
- URL mode
- URL component
Expected result
a%2Bb%20%26%2F%3F
Decode example
Input
a%2Bb%20%26%2F%3F
- URL mode
- URL component
Expected result
a+b &/?
Formats, limits and common errors
Check every % escape. Select form mode only when + means a space in form data.
- This encodes one component, not an entire URL. Form mode converts spaces to +; component mode preserves literal + during decoding.
- Decoding is one pass. Percent escapes require two hexadecimal digits; decoded binary/non-UTF-8 is unsupported.
- Output expansion may exceed the shared output ceiling even when input fits.
- Input: 262,144 UTF-8 bytes per text field. Output: at most 524,288 UTF-8 bytes; serialized responses have a separate 1 MiB ceiling. Size/work failures return no partial result.