Pro
securityIn-Browser

URL Encoder / Decoder

Encode, decode, and visually highlight malformed percent-encoding mistakes (like broken % signs and double-encoding).

Quick Fix:

Diagnostic Results (3 issues flagged)

❌ Broken Percent-Encoding (% Spellmistake)Snippet: st%2

Found solitary or incomplete percent symbol '%' at index 75. Every '%' must be followed by two hexadecimal characters.

💡 Recommendation: Replace with '%25' or provide two valid hex characters.

⚠️ Double-Encoded Sequence DetectedSnippet: %2520

Found '%2520' at index 58. The character was percent-encoded twice (%25 = %), which often triggers HTTP 400 Bad Request on web servers.

💡 Recommendation: Decode once to restore the standard single percent sequence.

❌ Unencoded Space Character

Raw spaces are strictly forbidden in URIs per RFC 3986.

💡 Recommendation: Replace raw spaces with "%20" or "+" in query strings.

Encoded Safe URL Output
https://api.example.com/search?query=hello%20world&token=abc%252520def&tag=test%252

Parsed Query String Parameters (3)

Key ParameterDecoded Value
queryhello world
tokenabc%20def
tagtest%2

Are you a happy user?

Forge DevTools is free, private, and runs 100% in your browser.

Want more features?Upgrade to Pro
Buy us Coffee
Sharing is caring
Come back!
Link to this tool
Send Feedback

Key Capabilities & Features

Pinpoints malformed percent sequences before they break server APIs.
Flags double-encoding mistakes like %2520 that produce HTTP 400 Bad Request errors.
Visual interactive query string parameter table for quick parameter editing.
Handles full URLs, path segments, and isolated query parameters with equal precision.

How to Use This Tool in 3 Steps

1

Provide Input

Paste your raw code or data, choose options, or load a pre-configured sample.

2

Instant Client-Side Processing

The parser compiles your data instantly inside your browser without any network round-trip.

3

Copy or Export

Copy the result directly with one click or export to a local downloadable file.

Frequently Asked Questions

This error occurs when decodeURIComponent() encounters an invalid percent-encoded sequence, such as a "%" character that is not followed by two valid hexadecimal characters.