In1.

URL encoder and decoder

Percent-encode text so it is safe to put in a URL, or decode an encoded URL back into readable text. Choose between encoding a full URL or a single component, and process everything instantly in your browser.

Loading tool…
All Web tools

How to use URL Encoder / Decoder

  1. 1

    Choose encode or decode

    Pick whether you want to encode text or decode an encoded URL.

  2. 2

    Pick the scope

    Choose component encoding for a single value, or full-URL encoding to preserve structure.

  3. 3

    Enter your text

    Paste the text or URL you want to convert.

  4. 4

    Copy the result

    The converted output appears instantly — copy it with one click.

Why URLs need encoding

URLs are only allowed to contain a limited set of characters. Spaces, accented letters, and many symbols — ampersands, question marks, slashes, plus signs, hash marks and more — have special meaning or are simply not permitted, so they have to be represented in a safe form when they appear in a link or a query string. That safe form is percent-encoding, where each disallowed character is replaced by a percent sign followed by its hexadecimal byte value: a space becomes %20, an ampersand becomes %26, and so on. Without it, a search term containing a space or a parameter value containing an ampersand would break the URL or be misread by the server. This tool does the encoding and decoding for you, so you can take any text and make it URL-safe, or take an encoded URL full of percent signs and turn it back into something a human can read. It removes the need to remember the codes or do the substitution by hand.

Encode a full URL or a single component

Not all encoding is the same, and choosing the wrong kind is a classic mistake. When you encode an entire URL, the characters that structure it — the slashes between path segments, the colon after the scheme, the question mark before the query — must be left intact, or you destroy the URL's meaning. But when you encode a single value that will go inside a URL, such as a query parameter or a path segment, those very same characters need to be encoded so they are treated as data rather than structure. In1 gives you both modes. The component mode encodes everything that is not safe, which is what you want for an individual parameter value. The full-URL mode preserves the reserved structural characters, which is what you want when encoding a complete address. Being able to pick the right one means your encoded output behaves correctly whether you are building a whole link or just escaping a single piece to slot into one.

Decode encoded URLs back to readable text

Encoded URLs are everywhere, and they are nearly impossible to read at a glance. A link copied from a search engine, an analytics tracking URL, a redirect parameter or an API request can be a dense string of percent signs and hex digits that hides what it actually contains. Decoding turns it back into plain text so you can see the real values: the actual search query, the destination of a redirect, the human-readable parameters behind the codes. This is invaluable when you are debugging, auditing where a link really points before you click it, or simply trying to understand a URL someone sent you. In1 decodes both full URLs and individual components, reversing the percent-encoding and restoring spaces, symbols and accented characters to their normal form. If the input is malformed and cannot be decoded cleanly, the tool tells you rather than producing garbage, so you know the string itself is the problem rather than the tool.

Private by design — handled in your browser

The URLs and values people encode or decode are frequently sensitive: links with authentication tokens, tracking parameters, internal addresses, redirect targets or query data that reveals what someone is searching for. There is no reason to send any of that to a third-party server just to swap some characters. In1 performs all encoding and decoding locally in your browser using the platform's own built-in functions, so your URLs never leave your device. Nothing is uploaded, nothing is stored and there is no account to create. The conversion happens the instant you type or switch modes, with no network request, which makes it both immediate and fully functional offline. You can paste a long, parameter-heavy URL and read its decoded form right away, or encode a value and copy the result with a single click. It is the convenience of an online utility with the privacy of doing the work on your own machine — which is exactly what URLs carrying tokens or personal data deserve.

Who uses a URL encoder and decoder?

It is a staple for anyone who builds or inspects links. Web and back-end developers encode query parameters when constructing URLs and decode them when debugging requests, redirects and API calls. SEO and marketing specialists decode tracking and campaign URLs to read the parameters, and encode values when assembling links by hand. QA testers and security researchers decode suspicious or complex URLs to understand exactly what they do before trusting them. Data analysts clean up exported URLs that arrive percent-encoded. Support staff make sense of links shared by users that have been mangled by encoding. Even casual users occasionally need to decode a URL to see where it really leads. Because the tool covers both directions and both the full-URL and single-component cases, and does it instantly and privately, it serves the quick 'what does this link actually say' lookup and the careful construction of a correct, safe URL equally well, without anyone reaching for code.

Get more from In1

Higher limits, batch processing and an API are on the way. Want early access?

Frequently asked questions