Developer Tools

URL Encoder & Decoder

Encode or decode URL components, complete URI text and form-style values. You can also inspect query parameters without opening or fetching the URL.

Component and full URI modesForm encodingQuery inspector

Encode, decode or inspect URL text

URL Encoder & Decoder

Transform URLs and query text without navigating to or fetching them.

Input and options
Only used in Query String Parser.

How this tool works and limits

Component mode uses encodeURIComponent/decodeURIComponent; full URL uses encodeURI/decodeURI and retains reserved URL structure. Only form/query decoding treats + as a space. Decode once. UTF-8 input limit 1 MB; result length is measured in Unicode code points. Query duplicates remain separate rows; up to 5,000 parameters.

Your input is processed locally in your browser and is not uploaded or stored by this tool.

Browser-local text processing

Input is processed locally in your browser. The tool does not visit the entered address, test whether it exists or send it to ToolHub.

How to use the URL encoder and decoder

  1. 1

    Choose URL Component, Full URI, Form or Query Inspector mode.

  2. 2

    Select Encode or Decode when the chosen mode supports both actions.

  3. 3

    Paste the text, URL or query string into the input field.

  4. 4

    Run the conversion and review any invalid percent-encoding error.

  5. 5

    Copy the output or inspect decoded parameter names and values.

URL component encoding versus full URI encoding

Component mode follows the browser’s encodeURIComponent and decodeURIComponent behavior. It is designed for one dynamic value such as a search term, path segment or query value, so reserved separators are encoded. Full URI mode follows encodeURI and decodeURI, which preserve structural characters such as the colon, slash, question mark and ampersand where appropriate.

URL encoding example

Encoding the component summer sale & shoes produces summer%20sale%20%26%20shoes. If the same value is being sent as form data, spaces are represented by plus signs, producing summer+sale+%26+shoes.

For a full address such as https://example.com/search?q=red shoes, Full URI mode keeps the URL structure and encodes the space in the query value.

Form encoding and plus signs

HTML form-style encoding commonly uses + for spaces and percent escapes for other special bytes. A literal plus sign must therefore be encoded as %2B when it is part of a value. Component decoding does not automatically treat a plus sign as a space; choose the correct mode for the data format.

Using the query-string inspector

The inspector separates parameter names and values for easier review. It preserves repeated keys instead of silently replacing earlier values. Optional decoding helps inspect encoded text. This is a parser only: it does not request the page, validate the domain, follow redirects or confirm that a parameter is safe.

Important technical notes

  • Decoded once: percent-encoded text is decoded one layer per operation.
  • Invalid input: incomplete percent escapes or invalid UTF-8 sequences return an error.
  • Not encryption: URL encoding makes text safe for a syntax position; it does not protect secrets.
  • Limits: input is limited to 1 MB and query inspection to 5,000 parameters.
  • Context matters: encode dynamic values separately instead of encoding an entire URL as one component unless that is intentionally required.

Related tools

Base64 Encoder & DecoderEncode Unicode text or files as Base64 or Base64URL.Open tool →HTML Entity Encoder & DecoderEncode special characters or decode entities safely as text.Open tool →JSON Formatter & ValidatorFormat, validate, minify and inspect JSON.Open tool →Regex TesterTest browser JavaScript regular expressions and review matches.Open tool →

URL Encoder & Decoder FAQ

What is URL encoding?

It represents characters with percent escapes so text can be used safely in a particular URL syntax position.

Should I encode a full URL or only a component?

Usually encode dynamic values as components; use Full URI mode when preserving URL structure is required.

Why does form encoding use plus signs?

The form-urlencoded format represents spaces as plus signs and literal plus signs as %2B.

Is URL encoding the same as encryption?

No. Encoded text can be decoded and should not be treated as secret.

Does the tool open or fetch the URL?

No. It only transforms or parses the text in your browser.

Why does decoding return an error?

The input may contain an incomplete percent escape or bytes that do not form valid UTF-8 text.

Explore the complete Shopshubb Tools directory or return to Developer Tools.

Scroll to Top
WhatsAppChat with Shopshubb