URL Encoder / Decoder and Query String Editor
Encode or decode URLs the right way, with an explicit choice between component and full-URI escaping, and edit any query string as a table of key/value pairs. Everything runs in your browser, nothing is uploaded.
Encode or decode
Escapes the reserved characters like & = ? / so the text is safe inside one query value or path segment.
Query string editor
Paste a URL or a query string, edit each parameter as a row, and copy the rebuilt link.
Splits the URL into its base, its parameters and its fragment. Press Enter or Parse.
Your text and URLs stay on your device. Nothing is uploaded.
What this tool does
URL Encoder / Decoder does the two jobs that actually trip people up. First, it escapes and unescapes text with the mode you choose: component escaping (encodeURIComponent) makes a value safe inside a single query slot or path segment by escaping the reserved characters like &, =, ? and /, while full-URI escaping (encodeURI) leaves those delimiters alone so a whole address stays a working link. Second, it opens any URL as an editable table: paste a link, see every query parameter as a key and value row, edit, add or remove them, and read the rebuilt URL back. It even gets the form detail right, where a space can be written as + or as %20. Nothing is uploaded; the whole tool runs in your browser.
Debugging an API? Base64 handles the credentials in an Authorization header, and a token you lift out of a URL usually goes straight to the JWT decoder.
What you can use it for
- Escape a value that goes inside a query parameter without breaking the rest of the URL.
- Decode a percent-encoded link to read what it actually points to.
- Edit, add or remove query parameters on a long tracking URL as a simple table.
- Fix a double-encoded URL where & turned into %26 and broke the link.
- Decide whether a space should be a + or a %20 for the backend you are calling.
How to use it
- For a single value, pick encode or decode and choose component or full-URI escaping.
- Paste your text and copy the result from the output box.
- To edit a URL, paste it into the query editor and press Parse.
- Change the base, edit the parameter rows, or add and remove pairs.
- Toggle spaces as + or %20, then copy the rebuilt URL.
Everything runs inside your browser. No file is uploaded to any server. See more tools in this field.
Pairs well with
Other tools people reach for in the same flow.
Related tools
DeveloperBase64 Encoder and Decoder
Encode and decode Base64 text online, with an optional URL-safe alphabet. Runs in your browser, nothing is uploaded to a server.
JWT Decoder: Read Token Payload
Decode the header and payload of a JSON Web Token online. No signature verification, free and in your browser, nothing leaves your device.
URL Slug Generator (Slugify)
Turn any text into a clean URL slug online, ready for permalinks and SEO. Free, instant and in your browser, no upload to any server.
Regex Tester and Debugger
Test and debug regular expressions online in real time, with capture groups and live match highlighting. Free and in your browser, no upload.
Frequently asked questions
What is the difference between component and full-URI encoding?
encodeURIComponent (component) escapes the reserved URL characters, so : / ? # & = + and others become percent codes. Use it for a single value that sits inside a query parameter or a path segment. encodeURI (full URI) assumes you are encoding a whole address, so it leaves those delimiters intact and only escapes spaces and other unsafe characters. Encoding a full URL in component mode double-escapes its separators and breaks it; encoding a single value in full-URI mode leaves an & or an = that corrupts the query. Picking the right mode is the whole point of the switch.
Why does a space sometimes become + and sometimes %20?
Both mean a space in a query string, but they come from different rules. In the form-urlencoded format that HTML forms use, a space is written as +. In a generic URL a space is written as %20. Most servers accept either one in the query, but some are strict, so the editor lets you choose. When decoding, a + in the query is read back as a space.
Does the query editor keep repeated keys and their order?
Yes. A query like tag=a&tag=b is common and meaningful, so each pair is kept as its own row in the order it appeared. Editing, adding or removing a row never reorders or merges the others, and the rebuilt URL preserves that exact sequence.
Will it break my URL if it has a fragment or no query at all?
No. The editor splits a URL into its base, its query and its fragment, and only rewrites the query. A fragment after the # is preserved as its own field, and a URL with no query never gains a dangling ?. You can also paste a bare query string like a=1&b=2.
Is anything uploaded?
No. All the encoding, decoding and query editing happen locally in your browser using the platform's own functions. Nothing you paste is sent anywhere.