Why is a space sometimes encoded as '+' instead of '%20'?

In standard RFC 3986 URL percent-encoding, a space is always '%20'. However, in HTML web form submissions (application/x-www-form-urlencoded), spaces were traditionally encoded as '+'. Both are valid depending on the context.

How do I fix a double-encoded URL (with '%2520')?

Paste the string into FileZenith's URL Decoder. Decoding it once will resolve '%2520' back to '%20', and decoding it a second time will restore the original clean space.

Can I decode complex URLs that have non-English characters or emojis?

Yes! FileZenith utilizes standard UTF-8 byte serialization, allowing it to flawlessly encode and decode international characters, accented letters, and modern emojis.

Can FileZenith parse and split query parameters into a table?

Yes! FileZenith includes an interactive Query Parameter Inspector that automatically splits complex URLs into clean, readable Key-Value pairs for easy editing and debugging.

Can I encode and decode URLs on an iPhone, iPad, or Android phone?

Yes. You can paste query strings, tracking parameters, and REST API endpoints on your phone to encode or decode RFC 3986 percent-encoded entities with zero network latency.

URL Encoder & Decoder Online

Encode or decode URLs, URI parameters, and percent-encoded query strings instantly. Features RFC 3986 support, query parameter inspector, and 100% private browser processing.

Mode:

Quick Samples:

Input Text / Plain URL to Encode

Encoded Output (Percent-Encoded)

https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Dhello%20world%20%26%20science%3D100%25%26redirect%3Dhttps%3A%2F%2Fapp.io%2Foauth%3Ftoken%3Dabc%2B123

Parsed URL Query Parameters (3)

Key (Parameter)	Value
q	hello world
science	100%
redirect	https://app.io/oauth?token=abc 123

Explore Related FileZenith Tools

View All

Zero Sign-Up

Free Invoice & HRA Rent Receipt Maker

Generate professional invoices and Section 10(13A) HRA rent receipts with instant PDF download.

Launch Tool

Keynote .key

Apple Keynote to PDF & Slides (.key)

Open and convert Apple Keynote (.key) presentations on Windows, Android & Linux.

Launch Tool

Privacy Scrub

PDF & EXIF Metadata Remover

Scrub hidden camera EXIF, GPS location, author name & software tags from PDFs and images.

Launch Tool

About Free URL Encoder & Decoder Online

Encode or decode URLs, URI parameters, and percent-encoded query strings online free. Features RFC 3986 compliance, query parameter inspector table, and 100% browser privacy.

Comprehensive web standards manual detailing IETF RFC 3986 URI generic syntax specifications, percent-encoding (%XX), reserved vs unreserved characters, UTF-8 byte serialization, and query parameter escaping.

How to Use Free URL Encoder & Decoder Online

Follow these simple steps to use Free URL Encoder & Decoder Online directly in your browser.

Step 1

Choose Mode

Select URL Encoder or URL Decoder from the top tab.

Step 2

Enter Text or URL

Paste your URL, query string, or plain text into the input field.

Step 3

Copy Result or Inspect Params

Instantly copy the converted string or inspect broken-down query parameters in the table below.

IETF RFC 3986 Percent-Encoding Engine

In-Depth Developer Guide: URL Encoder & Decoder Online (Percent-Encoding)

1Mathematical Architecture: IETF RFC 3986 Percent-Encoding (%XX) Mechanics

Uniform Resource Identifiers (URIs and URLs)—standardized under IETF RFC 3986—are restricted to a limited subset of US-ASCII characters to guarantee safe transmission across internet routing protocols, proxy caches, and web servers. When a web application needs to pass arbitrary data (such as non-English Unicode characters, spaces, or reserved punctuation) inside a URL query string or path segment, the data must be transformed via Percent-Encoding (also termed URL Encoding).

Under RFC 3986, any character not permitted in a specific URL component is converted into its underlying UTF-8 byte sequence; each byte is then represented by a triplet consisting of a percent character '%' followed by two hexadecimal digits representing the byte value (0–9, A–F). For example, an ASCII space (byte value 32, hex 20) becomes '%20'. Multi-byte UTF-8 characters (like the euro symbol '€' or accented letters 'é') expand into multiple percent-encoded hex triplets (e.g., '€' becomes '%E2%82%AC'). FileZenith executes this encoding directly in browser memory.

RFC 3986 Standard: Universal URI percent-encoding mapping non-ASCII and reserved bytes into %XX hexadecimal triplets.
UTF-8 Octet Serialization: Converts complex multilingual Unicode characters and emojis into standard valid URL byte triplets.
Sub-Millisecond Execution: Instantly decodes and encodes long URLs and API query strings in local browser RAM.

2Reserved vs Unreserved Characters: encodeURI vs encodeURIComponent

A foundational concept in web engineering is the distinction between Reserved and Unreserved characters. Unreserved characters are always safe in URIs and never require encoding: uppercase letters (A–Z), lowercase letters (a–z), decimal digits (0–9), hyphen (-), underscore (_), period (.), and tilde (~). Reserved characters possess structural syntactic meaning within URLs: delimiters such as ':', '/', '?', '#', '[', ']', '@', '!', '$', '&', ''', '(', ')', '*', '+', ',', ';', and '='.

JavaScript provides two native functions that developers frequently confuse: encodeURI() and encodeURIComponent(). The encodeURI() function assumes you are passing a complete URL (e.g., 'https://site.com/search?q=hello world') and preserves structural delimiters like 'https://' and '?', encoding only spaces and unsafe characters. In contrast, encodeURIComponent() encodes every reserved delimiter, ensuring a query parameter value can be safely passed inside a larger URL without breaking the query string. FileZenith supports both encoding modes.

Unreserved Characters: A–Z, a–z, 0–9, -, _, ., and ~ are universally safe and never altered.
Reserved Delimiters: Characters like '?', '&', '=', '/', and '#' define URL routing structure and require context-aware encoding.
encodeURI vs encodeURIComponent: Toggle between full-URL preservation mode and strict query parameter component encoding.

3Step-by-Step Practical Developer Workflow

To encode tracking parameters, format REST API endpoints, or decode garbled web links, follow this streamlined operational workflow. First, choose your operation: select 'Encode' (to convert plain text or URLs into percent-encoded format) or 'Decode' (to restore %XX strings back into readable human text).

Second, paste or type your URL or query string into the input editor. Third, select your encoding mode: choose 'Component Mode' (encodeURIComponent, recommended for query parameter values) or 'Full URL Mode' (encodeURI, which preserves http:// and ?). Fourth, view the real-time encoded or decoded output with instant character highlights. Finally, click 'Copy to Clipboard' for immediate integration into your web code or API client.

Step 1: Operation Selection - Choose between Encoding (text to %XX) and Decoding (%XX to readable text).
Step 2: String Ingestion - Paste raw web URLs, API endpoints, tracking UTM parameters, or JSON strings.
Step 3: Modality Calibration - Toggle between component-level parameter escaping and full-URL routing preservation.
Step 4: Query String Parser - Automatically splits complex URLs into an interactive key-value query parameter table.
Step 5: One-Click Export - Copy encoded strings or decoded parameters to clipboard ready for API testing.

4Enterprise & API Use Cases: OAuth Redirects, UTM Tracking & Webhooks

URL encoding and decoding is a daily necessity across full-stack web development, digital marketing, and cybersecurity. In OAuth 2.0 and OpenID Connect authentication flows, the redirect_uri parameter must be strictly percent-encoded when sent to authorization servers to prevent URL injection vulnerabilities.

In digital marketing, tracking parameters (such as Google Analytics UTM tags: utm_source, utm_campaign) containing spaces or ampersands must be encoded to prevent tracking links from breaking when shared across email and social media. In API testing, inspecting webhook payloads formatted as application/x-www-form-urlencoded requires rapid decoding to inspect submitted form parameters.

OAuth 2.0 Authentication: Guarantees redirect_uri parameters are properly escaped to prevent open-redirect vulnerabilities.
Google Analytics UTM Tags: Ensures marketing campaign tracking links survive email client parsing without breaking.
Form-Urlencoded Webhook Inspection: Decodes complex application/x-www-form-urlencoded payloads in seconds.

5Common Encoding Pitfalls & Client-Side Privacy Guarantees

A pervasive bug in web development is Double Encoding: encoding an already percent-encoded string. If 'hello%20world' is accidentally encoded a second time, the '%' character is itself encoded into '%25', resulting in 'hello%2520world', which causes backend 400 Bad Request errors. FileZenith includes intelligent heuristics that warn developers when an input appears already encoded.

Crucially, developers frequently encode URLs containing sensitive API tokens, bearer authorization headers, customer email addresses, and secret webhook endpoints. Pasting these URLs into third-party cloud web tools exposes private authentication tokens to external servers. FileZenith executes 100% locally in your web browser via client-side JavaScript. Zero bytes of your URLs or tokens are ever uploaded over the internet, guaranteeing total security.

Double Encoding Warning: Automatically detects and alerts developers to accidental %25 double-encoding bugs.
Plus (+) vs %20 Clarification: Clarifies how application/x-www-form-urlencoded uses '+' for spaces while RFC 3986 uses '%20'.
Absolute Security Sovereignty: Client-side mathematical execution ensures sensitive API tokens and URLs remain 100% private.

Frequently Asked Questions

Everything you need to know about Free URL Encoder & Decoder Online privacy, speed, and limits.

URL encoding converts characters that are not allowed in URLs (like spaces, quotes, emojis, and symbols) into a safe '%' followed by two hexadecimal digits (e.g., a space becomes '%20'). This ensures URLs transmit safely across web browsers and servers without breaking.

encodeURI is meant for full URLs; it leaves structural characters like 'http://', '?', and '/' intact. encodeURIComponent is meant for individual query parameter values; it encodes all reserved characters (including '?' and '/') so they can be safely passed inside another URL.