Sycago
All toolsReport an issue ↗

Developer tools / FREE ONLINE TOOL

URL Encoder & Decoder

Encode or decode URL components and full URLs as text without visiting the address.

No signupNo API keysLocal processing

YOUR WORKSPACE

URL Encoder & Decoder

How to use ↓

Ready. Your inputs stay in this tool's browser session.

Encode URL text without visiting an address

''

URL encoding represents certain characters with percent escapes so text can be used in a URL context. This tool encodes or decodes a URL component or a full URI as text. It does not visit an address, fetch a page, check a link or establish that a destination is trustworthy. Paste the text, choose the correct mode and direction, and inspect the result before using it in another system.

The distinction between a component and a full URI is essential. A component can be one query value, such as a search phrase. A full URI includes structural punctuation such as a scheme separator, slashes, a question mark and ampersands. Encoding an entire address as if it were one query value can escape its structure. Encoding a query value as if it were a complete URI can leave structural characters unprotected.

Use up to 100,000 text characters and keep an unchanged copy during review. Processing takes place locally in the browser. Encoding changes representation; it is not encryption, anonymization or link shortening. Anyone who obtains an encoded value can often decode it easily, so do not use percent escapes as a way to conceal a password or other secret.

Choose component or full URI mode

''

Encode one component

Choose component encoding for one value that will be inserted into a URL structure by another process. A search phrase such as “red & blue” needs its ampersand protected so it does not become the separator between two query parameters. A literal plus sign in a value also needs a deliberate representation. Let a URL-building API assemble the final address where possible instead of manually joining unescaped fragments.

Encode a full URI

Choose full URI encoding when you need to preserve the structural punctuation of an already assembled URI while encoding characters that cannot appear directly in that representation. It is not a substitute for encoding individual values before assembly. If a full URI contains an unescaped ampersand that was intended to be part of a value, this mode cannot infer that intention and repair the parameter boundaries.

Decode in the matching context

Decoding turns valid percent-encoded sequences back into text according to the selected mode. Component and full URI decoding differ in how reserved punctuation is handled. Use the mode that matches the representation you have. If a result still contains escapes for structural characters, check whether full URI behavior is preserving them rather than assuming decoding failed.

Optional plus-to-space handling

Some form-style query encodings represent spaces with a plus sign. General percent decoding does not automatically mean every plus is a space. Enable plus-to-space handling only when the source uses that convention. A literal plus in a mathematical expression, an identifier or a value such as C++ should not be erased by an assumption about form encoding.

Worked examples of representation

Think about the text's role before choosing a mode
TextRoleImportant distinction
red & blueOne query valueThe ampersand belongs inside the value
https://example.com/search?q=redA complete addressScheme and query separators are structure
a+bA literal expressionThe plus may be data rather than a space
hello%20worldPercent-encoded textOne decode gives a space

Suppose you want a search URL with the phrase “tea & cake”. Encode that phrase as a component before inserting it as a query value. The encoded ampersand then stays within the value instead of creating another parameter. After constructing the full URL, inspect its parsed query values or test the destination deliberately. This encoder does not open it for you.

Suppose a copied value is “summer+sale”. If it came from a form-style query, the plus may stand for a space. If it is an actual product code, the plus may be literal. The text alone may not tell you which interpretation is correct. Consult the source format and use the optional plus setting accordingly. A readable result is not necessarily the intended result.

Suppose a value contains %2520. Decoding once produces %20, while decoding again produces a space. That is a sign of multiple encoding layers, but it does not mean you should always decode twice. Each layer may correspond to a real surrounding format. Remove only the layer your task calls for, and keep the original for comparison.

Suppose an address has a fragment beginning with a hash mark. The fragment is structurally different from a query value and may be interpreted by client-side code. Encoding or decoding the whole address without considering that structure can change how it is parsed. Use a URL builder for assembling addresses and use this tool to inspect or transform the specific text representation you intend.

A workflow that avoids double encoding

''

Identify the source first. Is it raw text, an encoded query value, a complete URL or a string embedded inside another format such as JSON? The same visible percent sign can belong to different layers. Do not combine JSON unescaping, HTML entity decoding and URL decoding as if they were the same operation. Each has different rules and should be handled in its own context.

Keep the raw value and label the intended output. “Encoded search term” is clearer than “fixed URL” because it states what the result is meant to be. Select component mode for a value and full URI mode for a complete URI representation. If you are unsure, test a small value containing a space, an ampersand and a plus before processing the actual text.

Encode once at the boundary where raw text enters URL structure. If an API or a link builder already encodes parameter values, provide raw values to that builder unless its documentation says otherwise. Pre-encoding can turn a percent sign into %25 and create a second encoding layer. The destination may then receive literal escape text instead of the intended value.

After encoding, decode a copy once in the matching context and compare it with the original raw text. This round-trip check is useful for detecting accidental double encoding and plus-to-space mistakes. It does not validate whether the assembled URL is safe or whether the destination interprets the parameter as you expect. That requires a separate destination test.

When decoding, treat the result as untrusted text if the source is untrusted. A hidden-looking link can become readable after decoding, but readability is not proof of safety. Do not open a decoded destination automatically. Review the scheme, host and intended use before choosing to navigate in a separate step.

Errors, Unicode and other edge cases

''

A percent escape needs a valid hexadecimal byte representation, and encoded text must form a valid sequence for the relevant decoder. A stray percent sign, an incomplete escape or malformed UTF-8 can produce an error. Do not delete percent signs at random to force a result. Return to the source and determine whether the value was truncated, copied incorrectly or never meant to be encoded text.

Unicode text is represented through encoded bytes, so a single visible character may become several percent escapes. This is normal and does not imply several letters were added. Conversely, invalid Unicode sequences or malformed surrogate input can fail to encode. Preserve exact source text when you need to investigate a character issue, and avoid replacing unfamiliar letters merely to make a string shorter.

Decoding a full address can change how it looks without making it a suitable address to visit. Reserved characters have structural roles, and different modes intentionally handle some of them differently. If your goal is to read a query value, isolate that component rather than decoding the entire address indiscriminately. The receiving URL parser is the final authority on how structure is interpreted.

Plus-to-space behavior is a frequent source of silent errors. Run one test with the option off and one with it on when the source convention is uncertain. Compare the results with a known example from the same source. A literal plus sign can be part of a legitimate value, so the more human-looking output is not always correct.

The tool does not validate domain ownership, follow redirects, remove tracking parameters or inspect a downloaded file. It transforms text representation within the 100,000-character limit. For a campaign address, a UTM builder can handle structured parameters more directly. For JSON strings containing URLs, validate the JSON separately and avoid mixing the two escape systems.

Practice: trace one value through several layers

Suppose a JSON object contains a URL whose query includes a human search phrase. There are at least two representation layers: JSON string escaping and URL component encoding. Start by identifying which layer you are currently looking at. A backslash in JSON notation is not the same as a percent escape in a query value. Use the correct parser or decoder for each layer and preserve the raw source while investigating.

Extract the intended query component rather than decoding the entire surrounding structure by habit. A slash can be ordinary data inside a nested value but a path separator in a complete URL. Likewise, an ampersand can belong to the search phrase or divide two parameters. The correct representation depends on the role it should have after parsing, not on whether the character is visible in the source text.

Use a small test phrase containing a space, a plus, an ampersand and a non-ASCII letter. Encode it as a component, decode a copy once and compare with the original. Then test any form-style plus handling separately. This controlled round trip makes the convention explicit. It is much easier to reason about than a long production URL containing several nested addresses and already escaped tokens.

Watch for encoded separators in security-sensitive paths or routing values. Decoding can expose a separator that another component interprets structurally. This tool does not decide how a server, proxy or application will normalize a path, and it does not test access control. Use the destination's documented parsing rules and relevant application checks. A string that round-trips here is not automatically safe to use in every routing context.

Do not confuse a fragment with a query value. The hash portion can be handled by the browser or client-side application in a different way from a server query. Encoding a literal hash as data and leaving a structural hash unescaped have different effects. When assembling a complete address, use a structured URL builder so each part is assigned its proper role rather than concatenating unlabelled fragments.

After the representation is correct, review the actual destination and any sensitive values before sharing. A token remains a token when percent-encoded, and a malicious address remains untrusted when decoded into readable text. The tool does not navigate or inspect the server. Keep the text transformation, URL construction, destination test and permission to share as separate decisions with clear inputs and outputs.

Percent-escape hexadecimal digits can be written in different letter cases, but that does not mean the entire URL is case-insensitive. A path, query value or embedded token can depend on exact case. Do not lowercase a whole result merely to make escapes look consistent. If a comparison requires normalization, define the rule for each URL part separately. This encoder transforms representation; it does not establish a universal equivalence rule for every address or a canonical spelling accepted by all servers.

Local processing and a reliable review

This tool carries out its operation in your browser. It does not send the values you enter to a remote processing service, and it does not need an account to produce a result. The page still runs within your device and browser environment: anyone with access to your screen, an exported file, or a copied clipboard value may be able to read that material. Choose input that you are allowed to handle on the device you are using.

The practical input limit for this tool is 100,000 text characters. A limit is a boundary, not a promise that every device will handle the largest possible entry at the same speed. Other tabs, low available memory, browser extensions and an old browser can affect responsiveness. If the page appears busy, allow the operation to finish before repeating it. When a large text task can be divided safely, try a small representative sample first and then process clearly labelled parts.

Keep your source separately until you have checked the output. A browser result can be useful and still be unsuitable for the final place where you intend to use it. The receiving form may have different limits, a house style may need a manual edit, or a document may require facts that no mechanical conversion can infer. Compare one simple case by hand, then inspect a case near the boundary that matters to your work.

Keep URL structure separate from the data placed inside it. Choose the correct layer, encode once at the right boundary, and verify the result without treating a readable address as a safety judgment.

Frequently asked questions

What is the difference between a component and a full URI?

A component is one piece, such as a query value. A full URI includes separators that define its structure. Component encoding protects more punctuation so the value can be inserted safely as data. Full URI encoding preserves structural characters. Choose based on the role of the text, not simply whether it looks like a web address.

Does the tool open or fetch a URL?

No. It transforms the supplied text locally and does not visit the destination. It cannot confirm that a page exists, check a redirect or judge a site's trustworthiness. If you later choose to open a result, that is a separate action. Review the destination and purpose before navigating.

Is URL encoding encryption?

No. Percent encoding is a reversible representation used for URL contexts. It does not keep a value secret or provide access control. A password or token remains sensitive when encoded. Avoid placing secrets in URLs unless the system design explicitly requires and protects that usage, and handle the copied result appropriately.

Why does a space become %20?

A space is represented as the byte escape %20 in ordinary percent encoding. Some form-style encodings use a plus sign for spaces instead. Those are related but distinct conventions. Use the optional plus-to-space handling only when the source uses the form convention, and preserve a literal plus when it is actual data.

Should I turn every plus sign into a space?

No. A plus can be a literal character in a value, an expression or a code. It represents a space only under particular form-style conventions. Check the source format before enabling plus-to-space decoding. A value such as C++ would be damaged if literal plus signs were changed to blanks without that context.

Why did % become %25?

The percent sign itself needs encoding when it is raw data in a component. If you encode text that is already percent-encoded, its percent signs can become %25, creating another layer. This is often called double encoding. Identify whether the input is raw or already encoded before deciding whether another encoding pass is needed.

Can I decode the same value several times?

Only when the source actually contains multiple intended encoding layers. Repeated decoding until the text looks readable can change literal data and produce the wrong value. Keep the original, decode one layer at a time, and match each layer to the surrounding format. A round-trip test can help confirm the intended operation.

Why does decoding report malformed input?

The input may contain an incomplete percent escape, invalid hexadecimal digits or invalid encoded byte sequences. It may also have been truncated during copying. Check the source rather than removing characters randomly. If the percent sign was literal text rather than an escape, you may have selected the wrong operation for that value.

Can I encode a whole query string as one component?

You can transform it as text, but that treats all of its separators as data. That is appropriate only if the entire query string is itself one nested value. For a normal URL with several parameters, encode each raw value and assemble the structure with a URL builder. Do not confuse nested data with top-level separators.

Does decoding also fix HTML entities?

No. URL percent escapes and HTML entities are different representation systems. An ampersand written as an HTML entity in source markup needs HTML handling, not an arbitrary URL decode. Determine the source layer first. Applying several unrelated decoders blindly can alter valid text or create confusing results.

Can it handle non-English text?

It can encode valid Unicode text through the browser's encoding functions. A visible letter or emoji may expand to several percent escapes because its encoded representation uses multiple bytes. Malformed Unicode input can still cause an error. Check exact names and symbols after a round trip rather than assuming visual similarity proves equality.

Will full URI decoding remove every escape?

Not necessarily. Full URI decoding preserves certain reserved representations because those characters have structural meaning. Component decoding follows a different rule. If you need the value of one parameter, isolate and decode that component rather than forcing the entire URI through a mode that changes its structure.

Can it remove campaign tracking parameters?

No. Encoding and decoding change representation, not the set of parameters in an address. To edit a URL, use a structured URL editing process and decide which parameters are safe to remove. Some query values affect content rather than tracking. This tool does not fetch the page to determine their purpose.

How much text can I process?

The input limit is 100,000 characters, with practical responsiveness also depending on browser memory. Encoded output can be longer than the original because characters may expand into several escapes. For a large structured value, work at a meaningful component boundary and preserve the original instead of cutting arbitrarily through an escape sequence.

Is an encoded link safe to share?

Encoding alone says nothing about safety, permissions or privacy. A link can contain a secret token, personal data or an untrusted destination whether it is encoded or readable. Review the actual content and intended recipient. The tool does not check reputation, ownership or what a destination will do when opened.

What is a good final check?

Confirm the mode, the source convention for plus signs and whether the value was already encoded. Decode a copy once in the matching context and compare it with the intended raw text. Then validate the assembled URL separately. A correct representation is useful, but it does not prove the destination behavior is correct.

Choose a related tool when its operation matches the next part of your task. Check the result at each stage so a small source mistake does not carry into the final output.