URL decode path
Read encoded path segments locally.
Client/docs/my file/page.html
Nearby workflows on Toolcore
- Encoding tools — Hub index: Base64 & URL, Base64url, Base32, Crockford, LEB128, ASCII85, Z85, Base58, base-36, bencode, Morse, quoted-printable, URI, Puny… when the payload needs a different encoding or escape format.
- URL encode path — Encode URI path segments (encodeURI). when the payload needs a different encoding or escape format.
- URL decode — decodeURIComponent for percent-encoded text. when the payload needs a different encoding or escape format.
- Base64 & URL encoder — UTF-8 Base64 encode/decode and URL component encode/decode in one workspace—paste, transform, copy. when the payload needs a different encoding or escape format.
Common use cases
- URL decode path for quick local checks without uploading data.
- Copy results into tickets, docs, or classroom notes.
Common mistakes to avoid
Unexpected input shape
See the intro and how-to notes for accepted formats.
FAQ
Is processing local?
Yes—this runs entirely in your browser.
Agent prefill?
Use q or qb for the main text field when supported.
More tools
Related utilities you can open in another tab—mostly client-side.
Encoding tools
ClientHub index: Base64 & URL, Base64url, Base32, Crockford, LEB128, ASCII85, Z85, Base58, base-36, bencode, Morse, quoted-printable, URI, Punycode/IDN, Unicode escapes, data URLs, MIME, hex, HTML entities, JWT, JSON helpers, crypto.
URL encode path
ClientEncode URI path segments (encodeURI).
URL decode
ClientdecodeURIComponent for percent-encoded text.
Base64 & URL encoder
ClientUTF-8 Base64 encode/decode and URL component encode/decode in one workspace—paste, transform, copy.