Free Online URL Encoder & Decoder

Complete Guide to URL Encoding, URL Decoding, and Percent Encoding

URLs are essential to how websites, browsers, and web applications communicate. They identify web resources, carry query parameters, and connect users to specific pages.

However, URLs can contain characters that have special meanings. Spaces, ampersands, question marks, Unicode characters, and other symbols may need to be encoded to work correctly in a particular part of a URL.

A URL encoder converts characters into an appropriate encoded representation. A URL decoder reverses valid encoded sequences into readable text.

Nimzoa's free URL Encoder & Decoder makes these conversions easier. You can encode or decode text directly in your browser, choose between URL Component and Full URL modes, and copy the result without installing software.

This guide explains how URL encoding works, how to decode a URL online, the differences between JavaScript encoding functions, and how to avoid common mistakes.

What Is URL Encoding?

URL encoding is a method of representing characters within URLs so they can be interpreted correctly.

It is commonly called percent encoding because encoded bytes are written using a percent sign followed by two hexadecimal digits.

For example:

Whether a character needs encoding depends on where it appears in the URL.

A slash, for example, is meaningful as a path separator. An ampersand commonly separates query parameters. If these characters are intended to be part of an individual parameter value rather than separators, encoding them can prevent incorrect interpretation.

URL encoding example

Suppose you want to pass this search phrase as a query-parameter value:

red shoes & bags

When encoded as a URL component, it becomes:

red%20shoes%20%26%20bags

This representation allows the ampersand to be treated as part of the search phrase instead of as a separator between query parameters.

The resulting URL could look like:

https://example.com/search?q=red%20shoes%20%26%20bags

The q parameter contains the intended search phrase.

What Is URL Decoding?

URL decoding reverses valid percent-encoded representations into readable characters.

For example:

hello%20world

decodes to:

hello world

Similarly:

red%20shoes%20%26%20bags

decodes to:

red shoes & bags

URL decoding is useful when reading encoded links, examining API requests, debugging query parameters, or interpreting data copied from browser address bars.

Common URL decoding examples

These examples assume component-style decoding, where encoded reserved characters are converted to their literal characters.

Full URL decoding can behave differently because some reserved characters must retain their structural meaning.

How to Decode a URL Online

Nimzoa provides a browser-based way to convert encoded text into readable characters.

Step 1: Select Decode

Choose the Decode option in the converter.

Step 2: Choose the conversion scope

Select URL Component for an individual encoded value or Full URL for a complete URL whose structure should be preserved.

Step 3: Enter encoded text

Type or paste the text containing percent-encoded sequences.

For example:

https%3A%2F%2Fexample.com%2Fproducts%3Fid%3D25

Step 4: Review the result

In URL Component mode, this example decodes to:

https://example.com/products?id=25

Step 5: Copy the output

Use Copy Output to save the converted result to your clipboard.

The conversion is performed locally in your browser.

How to Encode a URL Online

Encoding is useful when text contains characters that may be interpreted as URL syntax.

Step 1: Select Encode

Choose the Encode option.

Step 2: Choose URL Component or Full URL

Use URL Component when encoding an individual value, such as a search phrase.

Use Full URL when encoding a complete URL while preserving many of its structural separators.

Step 3: Enter the original text

For example:

summer sale & offers

Step 4: Review the encoded output

In URL Component mode, the result is:

summer%20sale%20%26%20offers

Step 5: Copy and use the result

Copy the encoded value and place it in the appropriate URL component.

Remember that encoding a complete URL and encoding a query-parameter value are different operations.

URL Encoder vs. URL Decoder: What's the Difference?

An encoder and decoder perform opposite transformations.

Both operations are useful when building or troubleshooting websites, APIs, and links.

Nimzoa combines them in one tool so you do not need separate websites for everyday conversions.

URL Component vs. Full URL Encoding

This is one of the most important distinctions in URL encoding.

A complete URL contains structural characters with special purposes.

Consider:

https://example.com/search?q=red shoes&sort=popular

The colon, slashes, question mark, equals signs, and ampersand are meaningful parts of the URL.

Encoding the entire string as one component would encode many of those structural characters.

That may be appropriate when embedding the whole URL as a value inside another URL, but it is usually not what you want when preserving the structure of the original URL.

URL Component encoding

JavaScript's encodeURIComponent() is designed to encode a URI component.

For example:

Result:

The ampersand is encoded because it belongs to the value, not to the query string's structure.

Full URL encoding

JavaScript's encodeURI() preserves many reserved characters that can be meaningful in a complete URI.

For example:

Result:

The URL's structural separators remain present.

Comparison

Important: Full URL mode does not understand whether every separator is correctly placed. It applies encoding rules; it is not a complete URL validation or repair tool.

decodeURI() vs. decodeURIComponent()

JavaScript also provides two commonly used decoding functions.

decodeURIComponent() decodes percent-encoded sequences in an individual component, including encoded reserved characters.

decodeURI() is designed for complete URIs and preserves certain percent-encoded reserved characters.

For example:

Result:

But:

Result:

The second function preserves %26 because it represents an ampersand, a character with a reserved meaning in URI syntax.

This distinction matters when debugging encoded links.

If you expect %26 to become &, choose component decoding rather than full URI decoding.

What Is Percent Encoding?

Percent encoding is the underlying representation used for many characters in URLs.

An encoded byte is written as a percent sign followed by two hexadecimal digits.

For example, %20 represents the byte value hexadecimal 20, which corresponds to a space in UTF-8 and ASCII.

For non-ASCII characters, UTF-8 commonly represents a character using multiple bytes, and each byte may be percent-encoded.

For example, the check mark ✓ is represented in UTF-8 by three bytes.

Its percent-encoded form is:

%E2%9C%93

When decoded correctly as UTF-8, those bytes become the original check mark.

Percent encoding is not limited to English-language characters.

How URL Encoding Handles Unicode and Emoji

Modern web applications often process text containing accents, non-Latin scripts, and emoji.

For example:

Result:

The accented character is represented using UTF-8 bytes.

An emoji example:

Result:

These encoded values can be decoded back into their original characters when the encoded sequence is valid.

Unicode handling is especially important for international websites, multilingual search forms, and API integrations.

Why Does a Space Become %20 or +?

Spaces are one of the most confusing aspects of URL encoding.

With JavaScript's encodeURIComponent() function:

The result is:

However, HTML form-style query serialization commonly uses + for spaces.

For example, JavaScript's URLSearchParams can produce:

Result:

Both conventions appear in real web applications, but they are not interchangeable in every context.

In particular, decodeURIComponent() does not automatically convert a literal plus sign into a space.

Result:

If you are decoding form-encoded query data, use an appropriate form-data or URL query parser.

Do not assume every + character in a URL should become a space.

How to Encode URL Query Parameters Correctly

Query parameters allow websites to pass information through a URL.

For example:

https://example.com/search?q=shoes

The parameter name is q, and its value is shoes.

Now suppose the value is:

shoes & accessories

If you insert that value directly into the URL, the ampersand could be interpreted as a new query-parameter separator.

Using component encoding:

Result:

You can then construct:

https://example.com/search?q=shoes%20%26%20accessories

For application code, using the browser's URL and URLSearchParams APIs is often safer than manually concatenating complex query strings.

Example:

Result:

Notice that URLSearchParams uses form-style serialization, so spaces become plus signs.

Both examples can represent the intended query value when interpreted using the appropriate conventions.

URL Encoding for APIs

APIs frequently use URLs to identify resources and pass request parameters.

For example, an API request might contain a search value, category name, identifier, or filter.

If a parameter contains characters such as & or =, component encoding can prevent those characters from being mistaken for query syntax.

Consider this value:

status=active&sort=latest

As a single component, it becomes:

status%3Dactive%26sort%3Dlatest

This preserves the value as data rather than allowing it to be interpreted as two separate parameters.

When writing application code, prefer established URL construction APIs and follow the API provider's documentation.

URL Encoding for SEO and Marketing Links

Marketing URLs frequently contain campaign-tracking parameters.

For example, a campaign link might include:

utm_source=newsletter

utm_medium=email

utm_campaign=summer sale

The campaign name contains a space and should be serialized appropriately.

An encoded representation might be:

utm_campaign=summer%20sale

Proper encoding helps preserve parameter values when links are copied, shared, or processed.

However, URL encoding does not guarantee accurate analytics attribution.

Tracking also depends on correct parameter names, consistent campaign conventions, analytics configuration, and functioning destination pages.

For campaign link creation, a dedicated UTM Builder can help organize tracking parameters before the URL is shared.

Is URL Encoding the Same as Encryption?

No. URL encoding and encryption solve different problems.

URL encoding represents characters in a form suitable for a particular URL context.

Encryption protects information using cryptographic methods and keys.

For example:

secret message

can be encoded as:

secret%20message

Anyone can reverse this transformation.

The encoded text is not secret or protected.

Do not place passwords, access tokens, personal data, or other sensitive information in URLs merely because they are percent encoded.

URLs may appear in browser history, application logs, analytics systems, referrer information, or shared messages.

Use appropriate security practices and data-handling methods instead.

Why Does URL Decoding Sometimes Fail?

URL decoding may fail when the input contains malformed percent-encoded sequences or invalid UTF-8 data.

1. Incomplete percent encoding

For example:

hello%2

This contains an incomplete percent sequence.

A valid percent-encoded byte requires two hexadecimal digits after the percent sign.

2. Invalid hexadecimal characters

For example:

hello%ZZ

The characters ZZ are not hexadecimal digits.

3. Invalid UTF-8 sequences

Even if percent sequences are structurally correct, the decoded bytes may not form valid UTF-8 text.

For example, a lone %E9 byte is not a complete UTF-8 encoding of é.

4. Double encoding

Double encoding occurs when text that is already encoded is encoded again.

For example:

Original text:

hello world

Encoded once:

hello%20world

Encoded twice:

hello%2520world

The percent sign itself becomes %25.

Decoding the double-encoded value once produces:

hello%20world

Decoding it again produces:

hello world

Repeated decoding should not be performed automatically on untrusted input, especially when different application layers interpret encoded characters differently.

5. Choosing the wrong decoding scope

Full URL decoding preserves certain encoded reserved characters.

Component decoding converts them.

If %26 remains encoded when you expected an ampersand, check whether you selected Full URL instead of URL Component.

Common URL Encoding Mistakes

Encoding the entire URL as one component

Encoding a complete URL with component rules converts structural separators such as : and /.

This may be correct when embedding the URL as data, but not when preserving the original URL's structure.

Encoding query parameters incorrectly

Characters such as &, =, and ? may be part of a value or part of URL syntax.

Choose the appropriate encoding method based on their role.

Assuming URL encoding validates a URL

Encoding converts characters; it does not confirm that the destination exists, the URL is safe, or the syntax is appropriate for every use case.

Treating encoded text as secure

Percent encoding is reversible and provides no confidentiality.

Confusing plus signs with spaces

Form-style query serialization may use + for spaces, but ordinary component decoding does not automatically interpret every plus sign that way.

Encoding text repeatedly

Double encoding can produce unexpected values such as %2520.

Check whether the input has already been encoded before applying another transformation.

Decoding untrusted data without validation

Applications should handle malformed input safely and avoid treating decoded text as trusted instructions, HTML, file paths, or executable content.

URL Encoding Examples for Developers

Here are several practical examples using JavaScript.

Encode a search phrase

Output:

Decode a search phrase

Output:

Encode an email address as a component

Output:

Decode an encoded ampersand

Output:

Encode a complete URL

Output:

These examples demonstrate standard JavaScript encoding behavior.

They are not a substitute for validating application input or constructing URLs safely in production code.

Who Uses a URL Encoder and Decoder?

URL encoding and decoding are useful in many everyday workflows.

Web developers use them when preparing query parameters, debugging requests, and integrating APIs.

SEO professionals use them to inspect encoded links, troubleshoot URL parameters, and understand how search engines and browsers handle different characters.

Digital marketers use encoded URLs in campaign tracking, email links, and advertising destinations.

Website administrators may need to inspect redirect destinations, query strings, and content management system URLs.

Students and beginners can use a URL encoder to learn how percent encoding works.

Everyday internet users may need to decode a link to understand what its encoded text represents.

Why Use Nimzoa's Free URL Encoder & Decoder?

Nimzoa offers a practical browser-based workspace for common URL encoding tasks.

The tool supports both encoding and decoding, with separate options for URL Component and Full URL processing.

You can type or paste text, inspect the converted result immediately, swap input and output, and copy the output when ready.

Its built-in query-parameter example demonstrates how encoded values are used in real URLs.

The conversion happens in your browser, without requiring an account or an external processing API.

The tool is designed for quick conversions rather than bulk processing, encryption, shortened-link expansion, or automatic URL validation.

Frequently Asked Questions About URL Encoding

What does %20 mean in a URL?

%20 Represents a space character using percent encoding.

What does %26 mean?

%26 Represents an ampersand (&) when decoded as a URL component.

Is a URL decoder free to use?

Nimzoa's URL Encoder & Decoder is free to use, with no account required.

Can URL encoding handle emoji?

Yes. Unicode characters, including emoji, can be represented using percent-encoded UTF-8 bytes.

Does URL decoding remove encryption?

No. URL decoding reverses percent encoding. It does not decrypt protected information.

Why does a URL contain %25?

%25 represents a literal percent sign. It may also appear when already encoded text is encoded again.

Should I use encodeURI or encodeURIComponent?

Use encodeURIComponent() for an individual URL component or parameter value. Use encodeURI() when applying URI encoding rules while preserving many structural characters in a complete URI.

Why doesn't a plus sign become a space?

A literal + is not automatically converted to a space by decodeURIComponent(). The plus-as-space convention belongs to form-style query encoding.

Decode or Encode Your URL with Nimzoa

Whether you're preparing a query parameter, inspecting a percent-encoded link, or troubleshooting special characters, choosing the correct encoding scope is essential.

Use Nimzoa's free URL Encoder & Decoder above to convert text instantly, review the result, and copy the output for your next task.

Remember: URL encoding is a character-representation method, not encryption or URL validation.