What is the difference between component and full-URL mode?
Component mode calls encodeURIComponent and decodeURIComponent. Full-URL mode calls encodeURI and decodeURI, which preserve URI structure so complete URLs remain readable.
Encode and decode URLs, query parameters, and text directly in your browser.
Preparing the editor...
The guide and instructions on this page are available while the tool loads.
URL Encoder / Decoder helps transform text into a URL-safe format and decode encoded values back into readable text.
It is useful for query strings, redirects, API debugging, routing, and handling special characters in web applications.
Everything runs locally in the browser, which makes it fast and convenient for everyday developer workflows.
Typical tasks this tool is built for.
Files and inputs stay in your browser during processing.
Practical tips before you download or share the output.
Use component mode for query values and fragments. Use full URL mode when working with complete URLs.
Longer reads that pair well with this tool.
Developer guide
Fourteen In-browser developer utilities for JSON, encoding, tokens, diffs, hashes, regex, SQL, UUIDs, and timestamps — fast checks without installing anything.
Developer guide
Reduce exposure while reviewing sensitive JSON by using synthetic data, redacting credentials and identifiers, and checking browser, screen, and clipboard risks.
Business guide
Create a static URL, text, email, phone, or Wi-Fi QR code, review the generated payload and preview, then test the export in its intended use.
Common next steps after using this tool.
Automatically format and validate JSON in your browser.
Create QR codes for URLs, plain text, email, phone numbers, and Wi-Fi credentials in your browser.
Generate strong random passwords directly in your browser.
Encode and decode Base64 text directly in your browser.
Format or minify SQL queries directly in your browser.
Decode JSON Web Tokens directly in your browser.
Situations where this workflow saves time.
Component mode calls encodeURIComponent and decodeURIComponent. Full-URL mode calls encodeURI and decodeURI, which preserve URI structure so complete URLs remain readable.
Encoding uses the selected JavaScript URI function. During decoding, the Decode plus as space option replaces + with a space before the URI decoder runs; it is enabled by default and can be turned off.
The tool passes text to the browser encodeURI or encodeURIComponent implementation, which percent-encodes non-ASCII characters for URI use. The matching decode function converts valid encoded text back to JavaScript text.
The browser decoder rejects malformed percent encoding, including incomplete escapes or invalid encoded sequences. The tool shows its percent-encoding error instead of returning a partial result.
No. The tool transforms text with URI encoding functions and can inspect query-style input. It does not verify that a destination is valid, safe, reachable, or private.
For input that contains a query string or key=value text, it lists the detected parameter keys and decoded values using URLSearchParams. Each displayed value has its own Copy button.
No. The implemented controls are Copy output, Clear, and Load example. There is no result-download control.
The textarea has no configured maximum length. Very large values are still constrained by browser memory and responsiveness.
Until you manually choose a mode, it suggests Decode when it sees a percent escape such as %20 or a string that contains both ? and =. Selecting a mode manually stops that automatic suggestion.
Browse related tools or open the full workspace.