Home About Contact
Back to Home

URL Encoder / Decoder

Encode or decode URLs and query parameters for safe transmission.

Input
Output

      

      

    

  

    
Overview
Encode or decode URLs so special characters travel correctly.
Best for
  • Build query strings with spaces or symbols.
  • Decode tracking links to read parameters.
  • Encode query parameters before sharing links.
Step-by-step
  1. Choose encode or decode mode.
  2. Paste the URL or component.
  3. Copy the normalized result.
Examples

        
Example 1

        

          

            
Input

            
hello world

          

          

            
Output

            
hello%20world

          

        

        
Spaces become %20.

      

        
Example 2

        

          

            
Input

            
q=ai%20tools&lang=zh

          

          

            
Output

            
q=ai tools&lang=zh

          

        

        
Decoded parameters are readable.

      

        
Example 3

        

          

            
Input

            
name=alice & bob

          

          

            
Output

            
name=alice%20%26%20bob

          

        

        
Spaces and & are safely encoded.

      
Common mistakes
  • Encoding the whole URL vs a component uses different rules.
  • Double-encoding breaks links.
  • Encoding the full URL when you only need a parameter.
Pro tips
  • Encode only parameter values when possible.
  • Test the link in a browser.
FAQ
Why does + appear for spaces?
In query strings, spaces may be encoded as '+'; %20 is also valid.
Does this upload my data?
No. Everything runs locally in your browser.
Can I use it offline?
Yes. After the page loads, most tools work offline. Some assets (like fonts) may need a connection.
Data & privacy
All processing happens locally in your browser. No data is uploaded or stored.

    

    
Why this page is useful in real work

    
The widget gives you a fast result. This review section explains where that result is genuinely useful and where a second check still matters before you act on it.

    

      

        
Real workflow fit

        
People building query strings, debugging callbacks, cleaning redirect targets, and documenting reproducible URLs.

      

      

        
What this output still does not decide

        
Correct encoding does not guarantee that a route exists or that an application will parse each parameter the way you expect.

      

      

        
Review before you share or ship

        
  • Whether you should encode a single component or the full URL.
  • Duplicate parameters, redirect targets, and fragment behavior.
  • How the final URL behaves in the actual app, not just in a text field.

      

      

        
A practical workflow that keeps this page useful

        
  1. Start with the failing URL or the raw value that needs encoding.
  2. Encode only the piece that is unsafe, then decode it once to sanity-check the result.
  3. Test the final link in the destination page, callback flow, or browser history path.
  4. Document the exact variant you used so teammates can reproduce it.

      

      

        
Best next step

        
Treat this page as a transport-prep tool, then confirm the finished URL in the product or service that consumes it.