Nearby tools from the catalog that fit the same job or workflow.
Encode URL-safe text
Encode plain text for safe use inside full URLs, query strings, query values, and path segments.
Inspect query params
Parse one URL into origin, path, fragment, ordered query params, duplicates, and empty values.
Remove URL parameters
Remove selected query params from one URL while keeping the destination path and fragment intact.
Compare two URLs
Compare two URLs side by side and highlight path, fragment, and query parameter differences locally.
Extract campaign tags
Extract UTM tags and extra query params from one campaign URL in the browser.
Build anchor links
Build one anchored URL from a base URL and slugified fragment text in the browser.
Everyone can see the current score. Signed-in users can leave a 1 to 5 star rating, and any written review goes only to review@cleanor.app.
No ratings yet. Be the first to leave one.
Sign in to leave a public score from 1 to 5 stars. Optional written feedback is private and emailed only to review@cleanor.app.
This block mirrors the system review flow: score first, then an optional private note.
A quick way to understand who this helps, what it solves, and where it connects next.
Marketers, frontend engineers, QA teams, and founders debugging links and copied query strings.
Decoding URL-safe text without guessing whether the input is a full URL, a query string, or a single value.
Capture URL decoder intent with a practical multi-mode browser utility.
Cleanor Labs
These sections explain the job in plain language and set expectations for what the tool should do well.
To decode encoded text, paste it into URL Decoder and pick the mode that matches where the text came from: a full URL, a query string, a single query value, or a path segment. The tool then percent-decodes the input — turning sequences like %20 back into spaces and %3D back into equals signs — and shows the readable result, ready to copy.
Mode matters because encoded text looks similar across these contexts but the safest decoding behavior is not identical. In query-oriented modes, a plus sign is treated as a space, which is the expected behavior for form data, while other modes leave it alone. Keeping the cases separate keeps the output trustworthy.
All decoding happens locally in your browser. The link or value you paste never leaves your device, which is useful for URLs that contain tokens, internal paths, or other sensitive parameters.
When URL Decoder encounters invalid or incomplete percent-encoding, it does not silently corrupt the output. Instead it keeps the broken segment visible and warns you, so you can see exactly where the problem is rather than getting a misleading result.
This is the reverse of the URL Encoder tool and shares the same mode structure, so you can move between encoding and decoding work safely. Picking the matching mode on each side keeps round-trips predictable.
Short answers for the questions people usually have before trying a utility like this.
Yes, in the query-oriented modes where that behavior is usually expected. Other modes leave plus signs as-is so the output stays accurate for that context.
URL Decoder keeps the invalid segment visible and warns you instead of silently corrupting the output, so you can see exactly where the encoding is broken.
Encoded text behaves differently in full URLs, query strings, query values, and path segments. Separate modes keep the decoded output safe and accurate for each context.
No. URL Decoder runs entirely in your browser. The text you paste is decoded locally on your device and never uploaded.
Yes. URL Decoder is free to use with no account and no upload required.
Every tool on Cleanor is free with no sign-up, no credits, and no limits. Files are processed privately in your browser. Looking for on-device phone cleanup and Premium features? That lives in the Cleanor app.
Paste encoded text, choose the decoding mode, and turn the URL, query string, query value, or path segment back into readable text.