Encode and decode URLs online
URL Encode / Decode helps prepare URL components, query parameter values and complete URLs for safe sharing or development work. Choose URL Component when the entire input is one value. Choose Full URL when separators such as :, /, ?, &, = and # are part of the URL structure.
How to encode a URL
Paste a component or URL, choose the matching mode and select Encode. Spaces and reserved characters are represented safely while Full URL mode keeps the URL's structure and preserves query parameter order, duplicates and empty values.
How to decode a URL
Paste percent-encoded text and select Decode. WCODX reports malformed percent sequences clearly instead of silently returning a partial result. A literal plus sign remains a plus in component mode.
URL encoding is not encryption
Percent encoding makes data safe for transport; it does not hide the data. Never use URL encoding as a substitute for authentication, encryption or secret storage.
encodeURI vs encodeURIComponent
Component mode behaves like encodeURIComponent for a complete value. Full URL mode applies component-style encoding to URL parts while retaining delimiters, so query keys and values do not lose their structure.
Encode SVG for CSS
Paste or upload an SVG and convert it into a readable, percent-encoded data URI for CSS. The generated declaration follows the practical pattern background-image: url("data:image/svg+xml,..."); and keeps SVG text as SVG text rather than automatically switching to Base64.
URL-encoded SVG vs Base64 SVG
SVG is text-based, so percent-encoded SVG can be convenient for CSS and data URIs while remaining inspectable. Base64 is another representation and may be useful in other contexts, but it is not always necessary. Neither representation encrypts the SVG.
Safe browser preview
WCODX previews processed SVG through an isolated image object URL. Scripts, event handlers and external resource references are not executed or fetched by the WCODX document.
URL encoding questions
What is URL encoding?
URL encoding represents characters that have a special meaning in a URL, or are not safe in a URL, as percent-encoded bytes.
Is URL encoding encryption?
No. URL encoding is reversible data formatting, not encryption. Do not use it to protect secrets.
What is the difference between URL Component and Full URL mode?
URL Component mode encodes the complete value. Full URL mode keeps URL structure such as the scheme, slashes, query separators and fragment marker while encoding URL parts.
Does URL Encode / Decode upload my text?
No. Processing happens in your browser. WCODX does not send the entered URL or text to a server.
Are plus signs treated as spaces?
No. Component mode preserves a literal plus sign. In query-form conventions, plus can represent a space, but this tool does not silently rewrite it.
Can I upload an SVG file?
Yes. SVG mode accepts SVG files up to 5 MB and reads them locally in your browser.
Does WCODX upload my SVG?
No. SVG source, filenames and generated data stay in your browser and are not sent to WCODX.
Can I use the generated SVG in CSS?
Yes. Copy the generated CSS declaration into a rule such as background-image: url(...).
Does SVG URL encoding change image quality?
No. URL encoding changes the text representation, not the SVG vectors or rendered image quality.
Is URL-encoded SVG the same as Base64?
No. They are different representations. Percent-encoded SVG remains readable text, while Base64 converts bytes into another alphabet; neither is encryption.
Can I decode an SVG data URI?
Yes. SVG mode accepts percent-encoded SVG and data:image/svg+xml URIs, while clearly identifying unsupported Base64 SVG data URIs.