Do I need to encode slashes in a query string?

Usually not. A slash after the question mark has no special meaning, so most servers accept it as-is. Encoding it anyway is safe and removes any ambiguity.

Why does my %2F turn back into a slash?

Some servers and proxies decode the path before routing the request. Apache blocks it by default via AllowEncodedSlashes. If your application never sees the %2F, the fix is in the server configuration.

Is %2F the same as %5C?

No. %2F is a forward slash and %5C is a backslash. Only the forward slash separates path segments in a URL.

%2F is a forward slash

%2F is a forward slash.

Character	"/"
Name	Forward Slash
Encoded	%2F
Reserved	Yes — it has a special meaning in a URL

Why it breaks things

The slash is what divides a URL path into segments. In /products/shirts/blue the slashes say where one part ends and the next begins. So when a slash appears inside a value rather than between segments, it has to be encoded, or the server will read it as a divider.

This matters most for values that naturally contain slashes: dates written as 2026/08/12, file paths, category names like Home/Garden, and campaign tags. Encoding the slash as %2F keeps it inside the value where it belongs.

Be warned that some web servers reject or rewrite %2F in a path before your application ever sees it, as a security measure against path traversal. If a %2F in a path is not reaching your code, check the server configuration rather than the encoding.

Real examples

Without encoding

https://example.com/tags/Home/Garden

With encoding

https://example.com/tags/Home%2FGarden

Without encoding the server sees two path segments, 'Home' and 'Garden', instead of one tag.

Without encoding

https://example.com/report?range=2026/08/01

With encoding

https://example.com/report?range=2026%2F08%2F01

Slashes in a query value are usually tolerated, but encoding them removes all doubt.

Decode something

Paste a URL or text

History

Nothing yet.

History stays in this browser. It is never sent to our server.

Common questions

Do I need to encode slashes in a query string?: Usually not. A slash after the question mark has no special meaning, so most servers accept it as-is. Encoding it anyway is safe and removes any ambiguity.
Why does my %2F turn back into a slash?: Some servers and proxies decode the path before routing the request. Apache blocks it by default via AllowEncodedSlashes. If your application never sees the %2F, the fix is in the server configuration.
Is %2F the same as %5C?: No. %2F is a forward slash and %5C is a backslash. Only the forward slash separates path segments in a URL.