Encoding tools
Percent-encode or decode UTF-8 text for query strings, redirects, and APIs. Unicode stays safe, output is easy to copy, and nothing leaves your device.
Modern apps juggle Unicode in query parameters, OIDC redirects, and deep links. A focused URL encoder helps you convert arbitrary text into percent-encoding that survives HTTP transit, while the URL decoder unwinds escaped sequences when you are debugging a broken redirect.
Practitioners reach for encoder/decoder pairs when marketing copies a storefront link from Slack and breaks UTF-8 characters, or when a gateway strips reserved characters out of OAuth state payloads. Handling those cases manually is error-prone: you guess which layer applied encoding, sprinkle decodeURIComponent calls until something renders, then discover a double-encoded slash. Running the offending substring through ToolMorph keeps the trial-and-loop inside a sandbox tab with reversible steps.
Structured logs routinely embed escaped URLs inside JSON blobs. Paste the wrapper into our JSON formatter, copy the offending string, flip to decode mode here, then return to Grafana with a readable query value. Need to regression-test router rules? Paste sample paths into the regex tester after decoding so captures line up with what your edge workers expect.
Teams standardizing redirects also benefit: encode user-supplied captions before attaching them as UTM parameters, decode historic links before comparing against blocklists, and cross-check final strings with QA spreadsheets. Explore more topical links from the Encoding tools hub when you want a focused crawl path without losing the umbrella tools directory.
For component encoding, ToolMorph uses the same percent-encoding rules browsers apply to individual URL parts. Full URLs should still be composed carefully so delimiter characters remain correct.
Run Decode once per encoding layer. If text was encoded twice, decode twice and inspect intermediate output.
Yes—encoding, decoding, and copy are free and run locally without creating an account.
No. Percent-encoding only makes strings safe for transport. Never treat encoded query values as encryption—pair TLS and server-side protections for sensitive data.
Save the page in your browser for instant access anytime, or share the free online tool with teammates—no signup required.
Paste text, then encode or decode UTF-8 safely.