Private URL utility

Free URL Encoder & Decoder Online - No Signup

Convert Unicode text, URL components, complete URLs, and form values with accurate percent encoding. Everything runs locally in your browser without uploads or external libraries.

Encode or decode See how it works
Three accurate modes Unicode and UTF-8 Malformed input detection No uploads

URL Encoder & Decoder

Select a direction and scope, enter your content, and convert it locally with standards-aligned browser APIs.

Browser-only processing
Direction
Encoding scope

Encodes one query value, path segment, parameter value, or fragment value. URL structural characters are encoded.

Text to encode

0 characters · 0 B

Encoded result

0 characters · 0 B
Tip: press Ctrl/⌘ + Enter to convert

URL encoding is not encryption. Encoded text is reversible and may remain visible in browser history, analytics, logs, referrer headers, and server records. Do not place secrets in URLs.
01
Private by design Input remains in this browser tab
02
Unicode ready UTF-8 percent encoding
03
Three scopes Components, URLs, and forms
04
Strict validation Malformed input is reported
Standards-aligned URL processing

Encode and decode URL data locally

This URL Encoder & Decoder converts text into percent-encoded URL data and reconstructs Unicode text from valid encoded input. All processing happens inside your browser.

Different parts of a URL have different structural rules. Encoding a query value is not the same operation as encoding an already structured complete URL. The tool therefore provides separate modes for URI components, full URLs, and form values.

Accurate Unicode and UTF-8 handling

Valid Unicode characters are represented using their UTF-8 bytes before percent encoding. The decoder rejects malformed percent escapes and invalid encoded UTF-8 instead of silently returning corrupted text.

Focused capabilities

Everything needed for URL encoding

A clean workflow for preparing URL data, debugging encoded values, and inspecting percent-encoded content.

Component mode

Encode individual query values, path segments, fragment values, and parameters while escaping URL delimiters.

Full URL mode

Preserve structural characters such as slashes, colons, question marks, ampersands, equals signs, and fragments.

Form-value mode

Handle application/x-www-form-urlencoded values where spaces use plus signs instead of %20.

Unicode support

Encode international scripts, emoji, accented text, and symbols through their correct UTF-8 byte representation.

Strict error detection

Identify incomplete escapes, non-hexadecimal escape bytes, malformed UTF-8, and unpaired UTF-16 surrogate code units.

Flexible output

Copy converted content, swap it back into the input, or download it as a UTF-8 text file.

Three simple steps

How to encode or decode a URL

Convert URL data without installing software or sending content to a remote API.

01

Choose the direction

Select Encode to create percent-encoded data or Decode to reconstruct readable Unicode text.

02

Select the correct scope

Choose component, full URL, or form value according to where the data will be used.

03

Convert and copy

Review the result and statistics, then copy, swap, or download the converted content.

Mode comparison

Which URL encoding mode should you use?

Choose the mode based on whether your input is a value, an already structured URL, or HTML form data.

Property
URI component
Full URL
Form value
Typical input
One query value, path segment, or fragment value
An already structured complete URL
One HTML form field value
Space encoding
%20
%20
+
URL delimiters
Characters such as &, =, and ? are encoded
Structural URL delimiters are preserved
Delimiters inside the form value are encoded
Browser operation
encodeURIComponent
encodeURI
Form percent-encoding rules
Implementation guidance

URL encoding best practices

Encode data at the correct boundary and remember that transport encoding is not a security control.

1

Encode individual values

Construct URLs by encoding each dynamic component rather than encoding an entire URL after concatenation.

2

Avoid accidental double encoding

Track whether data is raw or already encoded so percent signs are not repeatedly converted to %25.

3

Do not put secrets in URLs

URLs can appear in history, logs, analytics, screenshots, caches, and referrer information.

4

Apply contextual output escaping

URL encoding does not replace HTML escaping, SQL parameters, JavaScript escaping, or authorization checks.

Common questions

URL Encoder & Decoder FAQ

What is URL encoding?

URL encoding converts characters into a representation that can be transmitted safely within a URL. UTF-8 bytes are commonly written as percent signs followed by two hexadecimal digits.

Should I encode a full URL or a URL component?

Encode a component when processing one query value, path segment, fragment value, or parameter value. Use full URL mode when the input already contains URL structure such as a scheme, slashes, question mark, ampersands, or fragment delimiter that should remain structural.

What is the difference between %20 and + for spaces?

Percent-encoded URL components normally represent a space as %20. HTML form encoding commonly represents spaces as plus signs, so the form-value mode converts spaces to + and converts + back to spaces when decoding.

Is my URL or text uploaded or stored?

No. Encoding, decoding, validation, copying, and downloading happen locally in your browser. This page does not upload or save the input or output.

Does the URL encoder support Unicode?

Yes. Valid Unicode text is converted through its UTF-8 representation before percent encoding. Decoding reconstructs Unicode text from valid UTF-8 percent-encoded bytes.

Does URL encoding make data secure?

No. URL encoding is a reversible transport format, not encryption, access control, or contextual sanitization. Sensitive information should not be exposed in URLs, and applications must still apply appropriate validation and output escaping.

What is double URL encoding?

Double encoding happens when already encoded text is encoded again. For example, %20 may become %2520 because the percent sign is encoded as %25. Encode data once at the correct component boundary unless a protocol explicitly requires another layer.

Continue working

Related developer tools

Work with Base64, JSON, and hash values using other private browser-based utilities.

Data encoding

Base64 Encoder & Decoder

Encode and decode text or binary data using standard Base64 representations.

JSON utility

JSON Formatter

Format, validate, and inspect JSON structures with readable indentation and validation feedback.

Hashing utility

Hash Generator

Generate cryptographic hashes for verification, testing, and development workflows.

Ready to encode or decode URL data?

Convert URL components, complete URLs, and form values privately with accurate Unicode handling and strict validation.

Use the URL codec now