Choose the exact component
Encode a parameter value or path segment rather than blindly transforming an entire URL. Separators such as colon, slash, question mark, ampersand, and equals have structural meaning.
Percent-encode a URL component or decode an encoded value without uploading it. Use this tool for query values, paths, callback parameters, and sanitized HTTP examples.
Transform one query value or path segment without uploading it.
This url tool keeps input local, but its result still needs the human review described in the steps below before it is shared or used.
Encode a parameter value or path segment rather than blindly transforming an entire URL. Separators such as colon, slash, question mark, ampersand, and equals have structural meaning.
Encoding replaces characters that are unsafe in a component with percent escapes. Decoding reverses one layer and reports malformed escape sequences instead of guessing.
Decoded URLs can expose signed parameters, tokens, email addresses, internal hosts, redirect targets, or personal data. Redact those values before sharing a transcript.
Percent-encoding is a transport representation, not encryption, validation, authentication, or protection against open redirects and injection. A receiving application must still parse and validate each value in context.
Before sharing the url result, read HTTP transcript sharing guide for the matching context and privacy checks.
Privacy, limits, and correct interpretation.
No. Encoding and decoding use built-in browser functions on this device.
Usually not. Encode the individual query value or path segment so structural separators keep their meaning.
No. Anyone can decode it, and servers, proxies, analytics, and browser history may record the URL.
A percent sign may be incomplete, contain non-hexadecimal characters, or represent malformed UTF-8 bytes.
Choose another browser tool only when the next task changes from free online url encoder and decoder to formatting, comparison, encoding, or measurement.
Pretty-print compact JSON, minify a valid document, or locate a syntax error without uploading the input. The formatter runs entirely in this browser.
Open tool →Compare an original and changed block line by line without sending either version to the server. Use the result for a quick inspection, not as a replacement for version-control history.
Open tool →Convert UTF-8 text to Base64 or decode a Base64 value locally. Base64 is a transport representation, not a confidentiality or access-control mechanism.
Open tool →Check code, logs, configuration, and HTTP transcripts for common credential shapes before sharing. Detection and redaction run in this browser, and no input is uploaded.
Open tool →Measure visible writing and actual UTF-8 storage size as you type. Counts update locally and help you check a text block before creating a paste.
Open tool →Inspect the Base64URL-encoded header and payload of a three-part JSON Web Token in this browser. The decoder never verifies the signature and never proves that a token is authentic or safe to trust.
Open tool →Convert Unix seconds, Unix milliseconds, or an ISO 8601 date into UTC, local time, seconds, and milliseconds. Processing stays in the browser for safer log analysis.
Open tool →Create a lowercase SHA-256 digest from the exact UTF-8 bytes of a text block. Hashing runs through the browser Web Crypto API and does not upload the input.
Open tool →Prepare a text list or copied diagnostic block locally by trimming trailing spaces, compacting blank lines, removing duplicate lines, or sorting lines. Every action changes text, so review the result before replacing a source artifact.
Open tool →