Equals Sign Inside Query Value – Decode %3D Correctly

Local only

Keep equals signs inside query values with %3D and inspect the decoded result.

16 chars · 1 line

22 chars · 3 lines

1 parameter1 unique keys

Query string percent encoding

How do I put = inside a query parameter value?

The first equals sign separates a query key from its value. Percent-encoded %3D is decoded as a literal equals sign inside that value. This tool is free to use. No account or payment is required.

Last updated

What you can do here

  • Browser-native URLSearchParams behavior
  • Full URL and raw query parsing
  • Repeated parameter preservation
  • JSON object to query construction
  • Browser-local processing

Steps

  1. Paste the query into Parse to JSON.
  2. Identify equals signs that are data rather than the key/value separator.
  3. Encode those inner equals signs as %3D.

Only query structure should stay literal

The outer key/value separator remains an equals sign, while equals signs belonging to the value can be percent-encoded.

After parsing, URLSearchParams decodes %3D back to = in the exposed value.

Token containing multiple equals signs

Encoded equals signs remain part of one value.

Query string

?token=a%3Db%3Dc

Parsed JSON

{
  "token": "a=b=c"
}

Common questions

Frequently asked questions

Does every equals sign need encoding?

No. Keep the structural key=value separator; encode equals signs that belong inside the key or value.

Is %3D case-sensitive?

Percent-escape hex digits are commonly accepted in either case.

Can parameter names contain equals signs too?

They can when percent-encoded before parsing.

Debugging a specific Query String issue? Browse Query String troubleshooting.