Decode error
find incomplete or non-hex percent sequences and avoid silently replacing them.
URL Encoder, Decoder & Parser
Encode a URL component, decode percent escapes or inspect a full URL structure—with explicit warnings for malformed and untrusted input.
Developer & Text ToolsDirect answer
A URL encoder converts characters into percent-encoded form, while a decoder reverses valid percent sequences. AppKiro also parses a full URL into protocol, host, path, query and fragment and may flag text that resembles readable Base64; that hint is heuristic unless strict validation is implemented.
Decoded text
URL details
Paste a URL to inspect its fields.
How to use it
Enter the source data: Choose encode, decode or parse. Paste a synthetic URL/component and preserve the original for comparison.
Choose the relevant settings: For encoding, identify whether the value is a component or a complete URL. For decoding, reject malformed percent escapes with a clear error instead of partial silent output.
Review and verify the result: Inspect parsed protocol, host, path, query and fragment. Review any Base64 hint as a clue only, then copy the result without automatically opening it.
Key capabilities
- Percent-encodes URL text/components.
- Decodes valid percent sequences.
- Parses protocol, hostname, path, query and fragment.
- Shows query components for inspection.
- Surfaces readable Base64/Base64URL hints with non-authoritative labeling.
Best use cases
- Encode a query-parameter value for testing.
- Decode a copied redirect URL for manual inspection.
- Break a URL into components during debugging or support.
Limits and safety notes
- Percent encoding is context-specific. Encoding a whole URL can also encode reserved delimiters that must remain structural. Decoded text is still untrusted and may contain scripts, redirect targets, credentials or malformed Unicode.
- The core transformation runs in the current browser component. Browser extensions, clipboard history, downloaded files and site-wide diagnostics remain separate exposure points, so never enter production secrets unless you have reviewed the complete environment.
- The Base64/Base64URL indicator is heuristic. It checks a compatible alphabet, minimum length, padding shape, valid UTF-8 and mostly printable output; it is not a strict canonical Base64 validator.
Troubleshooting
Parsed host is empty
add an explicit scheme when the URL parser requires an absolute URL.
Base64 hint is wrong
treat it as heuristic and require strict alphabet/padding/UTF-8 validation before presenting decoded content.
Frequently asked questions
Should I encode the entire URL?
Usually no. Encode individual query values or path segments with the correct component function while preserving structural delimiters such as :, /, ? and &.
Does decoding a URL make it safe?
No. It only reveals a representation. Validate the scheme/domain and handle the result as untrusted input in the destination context.
Why does URL decoding fail?
Malformed percent sequences, incomplete escapes or byte sequences that are not valid UTF-8 can cause an error. The page should report the exact failure.
Is it safe and private?
The calculation runs in this browser component, but that alone is not a complete privacy guarantee. Use non-production data unless you have also reviewed extensions, clipboard history, downloads and site diagnostics.
Does it work on mobile?
The layout adapts to narrow screens. File selection, camera access, clipboard actions and downloads still depend on the permissions and capabilities of the mobile browser.
Related tools
Use the tool
Select the correct context, inspect every component and never auto-navigate to decoded output.