Local Processing

URL Encode / Decode Tool

Use URL encode, URL decode and HTTP encode workflows for query parameters, API testing, redirects and copied links.

Runs locallyNo uploadYour input is processed in your browser.

URL Encode / Decode

Encode, decode, parse, and build URL query parameters in batches.

What is this tool?

A URL encode/decode tool converts reserved characters into percent-encoded text and decodes percent-encoded values back to readable strings. It is especially useful for query parameters, redirect URLs, API calls and HTTP debugging.

Best practices

Use component encoding for query parameter values rather than a whole URL.
Check for double encoding such as %2520 when a value was encoded twice.
Keep reserved characters unencoded only when they are meant to structure the URL.
Prefer %20 for spaces in URL components unless your target expects plus signs.
Test the final link in the destination browser or API client.

Common errors

Using encodeURI when encodeURIComponent is required.
Double-encoding a value that was already percent encoded.
Forgetting to encode & inside a parameter value.
Decoding an entire URL when only one parameter value should be decoded.
Mixing form encoding plus signs with ordinary URL percent encoding.

Examples

Search query encoding

Input example

luma ai video generator

Output example

luma%20ai%20video%20generator

Use this encoded value inside a query parameter such as q=.

Nested redirect value

Input example

https://example.com/?next=https://lumatool.com/tools/base64

Output example

https%3A%2F%2Fexample.com%2F%3Fnext%3Dhttps%3A%2F%2Flumatool.com%2Ftools%2Fbase64

Encoding the nested URL prevents its ? and & characters from breaking the outer query string.

Privacy note

This tool runs in your browser. Text values are processed locally and are not uploaded to LumaTool servers.

How to use

Step 1. Paste a URL, query value or component into the input field.
Step 2. Choose the mode that matches your workflow: whole URI or component.
Step 3. Encode or decode and check whether reserved characters such as &, ?, = and / are handled correctly.
Step 4. Copy the result into your API client, browser, redirect rule or documentation.

Real-world examples

Encode search terms or campaign parameters before adding them to a URL

Encode search terms or campaign parameters before adding them to a URL.

Decode copied redirect links to understand the target and query par...

Decode copied redirect links to understand the target and query parameters.

Prepare HTTP encode examples for API tests and support notes

Prepare HTTP encode examples for API tests and support notes.

FAQ

What is HTTP encode?

People often use HTTP encode to mean percent-encoding URL components so they can travel safely inside HTTP query strings.

Should I encode the whole URL or only a parameter value?

Encode only the component or parameter value unless the entire URL is being nested as another parameter.

Why do I see %2520?

%2520 usually means %20 was encoded again. Decode once and check where the duplicate encoding happened.

What is URL Encode / Decode best used for?

URL Encode / Decode is useful for focused developer tools tasks where you need a quick browser-based result without switching tools.

How is my input handled?

This tool runs in your browser. Text values are processed locally and are not uploaded to LumaTool servers.

Can I use the output in production work?

Yes, but review the result before applying it to production systems. LumaTool helps with utility work, validation, and formatting, but final decisions stay with you.

Which related tools pair well with this page?

The related tools section links to nearby workflows in the same locale so you can continue formatting, validating, converting, or checking related data.

Does this page work on mobile browsers?

Yes. The tool layout, examples, FAQ, and result areas are designed to work on both desktop and mobile browsers.