No. Encoding and decoding run locally in your browser. Your data stays in your browser.

What does “Preserve URL structure” do?

When enabled, the tool keeps the scheme and host intact (for example https://example.com) and encodes path, query, and fragment parts separately. When disabled, the whole input is treated as a single component (encodeURIComponent semantics).

Why %20 instead of +?

RFC 3986 encodes spaces as %20. The “Encode spaces as %20” option follows that. Turning it off uses + in the form-urlencoded style after encoding.

What happens with invalid percent-encoding?

Decode validates sequences like %ZZ before converting and shows a clear error with a character position when possible. Malformed input is not silently altered.

TEXT TOOLS

URL Encoder / Decoder

Encode and decode URL strings safely

Encode & DecodeURL, text and parameters
Fast & AccurateInstant conversion
Supports Special CharactersSpaces, symbols, Unicode, etc.
Copy & DownloadOne click actions

Your data stays in your browser.

1. Select Operation

2. Enter Text or URL

Characters: 0 | Lines: 0

3. Options

Encode spaces as %20 (RFC 3986)Encode all special charactersUse upper case hex (e.g. %2F)Preserve URL structure (scheme & host)Preview changes in real time

Result

Characters: 0 | Lines: 0

About URL Encoding

URL encoding converts special characters into a format that can be safely transmitted in URLs. For example, a space is encoded as %20 instead of a space character.

Common Characters

Space%20
!%21
#%23
$%24
%%25
&%26
+%2B
/%2F
?%3F
@%40

Quick Examples

How to encode or decode a URL

Step 1
Choose Encode or Decode
Select whether to convert text into URL-safe form or back.
Step 2
Enter text or a URL
Paste a full URL, query value, path, or plain text — including Unicode.
Step 3
Tune options
Control %20 spaces, special-character encoding, uppercase hex, and URL-structure preservation.
Step 4
Copy or download
Use the result instantly, or download it as a text file.

Real URL encoding — standards-based and client-side

OneFileKit uses JavaScript’s encodeURIComponent / decodeURIComponent semantics for component encoding, with an optional mode that preserves scheme and host while encoding path, query, and fragment parts.

Malformed percent-encoded sequences are validated before decode so you get a clear error instead of a crash. Analytics only track aggregate events — never your URLs or text.

Related Tools

Frequently asked questions

Is my URL uploaded?: No. Encoding and decoding run locally in your browser. Your data stays in your browser.
What does “Preserve URL structure” do?: When enabled, the tool keeps the scheme and host intact (for example https://example.com) and encodes path, query, and fragment parts separately. When disabled, the whole input is treated as a single component (encodeURIComponent semantics).
Why %20 instead of +?: RFC 3986 encodes spaces as %20. The “Encode spaces as %20” option follows that. Turning it off uses + in the form-urlencoded style after encoding.
What happens with invalid percent-encoding?: Decode validates sequences like %ZZ before converting and shows a clear error with a character position when possible. Malformed input is not silently altered.