Skip to main content
FetchToolKit logoFetchToolKitFetchToolKit

URL Encoder & Decoder

Safely encode special characters in query parameters and web addresses, or decode percent-encoded URLs into readable text.

Free to useNo sign-up requiredWorks in your browserPrivacy focused

URL Encoder & Decoder Workspace

How to use

  1. 1

    Step 1

    Select Encode URL or Decode URL and choose either URI Component (for single parameter values) or Full URL (to keep https:// and slashes intact).

  2. 2

    Step 2

    Check the '+' space option if you are working with HTML form query strings where spaces are represented as '+'.

  3. 3

    Step 3

    Paste your text or URL into the input box, then copy or download the converted result.

Key features

  • URI Component mode encodes all special characters (including &, =, ?, /, and parentheses) for safe query parameters
  • Full URL mode encodes spaces and unsafe characters while keeping https://, slashes, and ?/& separators working
  • Optional '+' space toggle for form-encoded query strings
  • Displays decoded URLs safely as plain text and warns you if a link contains a suspicious script prefix

Supported formats

URLUTF-8

File limits & notes

Processes URLs and query strings up to 5 MB in your browser. Decoded URLs are always shown as plain text rather than clickable links so you can inspect unknown or shortened redirect URLs safely.

Frequently asked questions

View all FAQs
When should I use URI Component mode versus Full URL mode?

Use URI Component mode when encoding a value that goes inside a parameter (such as a search query or redirect URL that contains '&' or '='). Use Full URL mode when you want to fix spaces or special characters in a complete web address without breaking 'https://' or '/'.

What is the difference between %20 and + for spaces?

Standard URL paths use %20 for spaces, while traditional HTML form submissions often replace spaces with a '+' sign in the query string. You can toggle between both behaviors with one checkbox.

Why is the decoded URL shown as plain text instead of a clickable link?

Showing decoded URLs as plain text lets you safely inspect unfamiliar or encoded links without the risk of accidentally clicking a harmful address.

Practical Example: Encoding a Search Query Parameter with Special Characters

Sample Input
A search filter parameter containing spaces, ampersands (&), and parentheses that would break a URL query string.
Result
Cleanly percent-encoded so it can be passed safely as a single URL parameter without breaking the link.