ToolsArena24

URL Decoder

Maintained by the ToolsArena24 team. Methodology and test scope

Quick answer: Convert URL encoded input to readable text locally, with Unicode support and clear validation errors.

About this url decoder

Decode percent-encoded URL components into readable Unicode text. Each percent triplet represents a byte, and groups of UTF-8 bytes reconstruct accented letters and other characters. For example, a%20b%26%C3%A9 becomes a b&é. The decoder performs one decoding pass, so a double-encoded percent sequence stays encoded after its first layer is removed. Run a second pass only when you know the source was encoded twice.

Choose component mode when plus signs should remain literal plus signs. Choose form mode when the input came from an application/x-www-form-urlencoded query or form field; in that convention a plus means a space. A malformed triplet or invalid UTF-8 byte sequence raises a clear error instead of silently replacing damaged characters. Unescaped text can be mixed with properly encoded sequences.

Decoding makes a value readable but does not fetch the URL or validate its destination. It can expose separator characters such as ampersands and slashes, so decode a parameter after parsing the surrounding query rather than decoding an entire URL before splitting it into fields.

Which controls should I check first?

The URL Decoder form labels its controls as Input; Decoding convention; Result. Its selectable values include URL component (preserve +); Form field (+ means space). Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.

How should I interpret this specific operation?

The plus convention is selectable. In component mode, a plus remains a plus; in form mode it becomes a space. Percent triplets are decoded in either case. Choose the convention used by the source before comparing the worked example with another library, since two apparently reasonable decoders can disagree on a+b without either having misread the percent escapes.

Worked helper values

These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.

Supplied valuesCalculated return value
a%20b%26%C3%A9; falsea b&é
a+b; truea b

Is this a representation change or a content change?

An encoding expresses bytes or characters using a different alphabet or escape notation. It should not be confused with encryption, compression or permission to execute the result. Work out which layer the receiving field expects before converting. A URL component, a complete URL, an HTML text node and a JSON string need different escaping rules. Encoding for one context does not automatically make a value safe in another. Keep the unencoded source while editing and convert at the boundary where the destination requires it. Otherwise repeated conversions can encode existing escape markers rather than the original content.

How do I diagnose a malformed input?

Check the alphabet, prefix, separators and final padding against this tool's documented input format. A pasted quotation mark or trailing label can turn a valid payload into invalid text. For UTF-8 decoding, a byte sequence can be syntactically valid in its outer representation yet still fail to represent text. Binary images and compressed data are examples of payloads that should not be forced through a text decoder. Use the appropriate file or image workflow for them. Do not remove padding or percent signs at random to make an error disappear; first identify what those characters mean in the expected representation.

Why does decoding once matter?

A value can have more than one encoding layer. Decoding the outer layer yields another encoded string rather than necessarily reaching the final readable content. Repeating the operation is appropriate only when the source format specifies those layers. With URL components, decoding separator characters too early can change the structure of a query. With HTML entities, a decoded angle bracket is ordinary text until another application interprets it as markup. Inspect the result as text before placing it into an active context. Keep a record of which layer you decoded so that a later step does not accidentally repeat it.

How do non-ASCII characters affect the result?

A character such as é occupies more than one UTF-8 byte. An emoji can require several bytes even when it occupies one visible position. Encoders process those bytes according to their representation rules, so output length cannot be predicted from visible character count alone. A percent-encoded character can consist of several percent triplets, and Base64 groups bytes rather than visible letters. Compare the worked Unicode example with the result instead of assuming one output group per character. A strict text decoder helps expose damaged bytes that would otherwise be replaced by an ambiguous replacement character.

Does + mean a space?

Only in the selectable form mode. Component mode preserves it.

How many decoding passes occur?

One pass per run.

Why does decoding report an error?

A percent sequence is malformed or its bytes do not form valid UTF-8.