ToolForge Online

Developer tool

URL Encoder/Decoder

Encode and decode URL text, query values and special characters locally in your browser.

Input

Encoding mode

Result


            
This tool runs locally in your browser. It does not send URLs to a ToolForge Online server.

          

        



          
          
What is URL encoding?
URL encoding converts spaces, accents and special characters into a format that can be safely used inside URLs.

          
When to use it
Use it when preparing query parameters, testing links, debugging encoded strings or checking how a value will appear in a URL.

          
Full URL vs query value
Encode query value is best for a parameter value. Encode full URL keeps common URL separators readable while encoding spaces and special characters.

          
Local browser processing
Encoding and decoding happen with browser JavaScript on your device. Avoid pasting sensitive URLs if your policy does not allow it.

          
Practical guidance
What this tool does
URL Encoder/Decoder encodes URL text and decodes encoded URL components into readable text.
When to use it
Use it when preparing query values, debugging a link, checking encoded characters or cleaning URL snippets.
Example use
For example, paste a search phrase with spaces and special characters, encode it as a query value and copy the result into a test URL.
How it works
The tool uses standard browser URL encoding functions and separates full-URL handling from query-value style encoding where available.
Limitations
The output does not verify whether a destination URL is safe, reachable or correct; it only changes how characters are represented.
Privacy note
The tool runs encoding and decoding in the browser and should not receive private links if your policy does not allow it.

          
FAQ
When should I encode a full URL vs a single value?
Encode a single value (like a search phrase) when it goes into one query parameter, and use full-URL encoding only to fix spaces and unsafe characters without touching separators such as ? and &.
Why do spaces become %20?
URLs cannot contain raw spaces, so encoding replaces them with %20 (or + in some legacy form encodings) to keep the address valid across browsers and servers.
Why does decoding show an error?
Decoding fails on malformed percent sequences, such as a % not followed by two hexadecimal digits. Check for truncated values or double-encoded text and decode step by step.
Are my links sent to a server?
No. Encoding and decoding use the browser's built-in URL functions on your device, and the text is not uploaded to a ToolForge Online server.