URL Encode JSON

Report an Issue

Help us improve by telling us what went wrong.

Embed this Tool

Customize and copy the embed code for your website.

URL Encode Your JSON Data Safely

When you need to pass JSON data through a URL - as a query parameter, in a redirect URL, inside a webhook callback, or as part of an OAuth state parameter - you cannot just paste raw JSON into the URL string. Characters like curly braces, double quotes, colons, and spaces are not valid in URLs without encoding. They will break the URL parser, corrupt the data, or cause security vulnerabilities. Our URL Encode JSON tool takes your JSON data and converts it into a URL-safe string using percent-encoding, ensuring it can travel through any URL without issues.

Why Raw JSON Breaks URLs

URLs have strict rules about which characters are allowed. The RFC 3986 standard defines a limited set of unreserved characters (letters, digits, hyphens, periods, underscores, tildes) that can appear in URLs as-is. Everything else - including the curly braces, square brackets, double quotes, colons, and commas that make up JSON syntax - must be percent-encoded. A double quote becomes %22, a curly brace becomes %7B, a colon becomes %3A. Without this encoding, a URL containing JSON will be misinterpreted by browsers, servers, and proxies, potentially losing data or causing errors.

How URL Encoding Works for JSON

Our tool applies percent-encoding (also called URL encoding) to your entire JSON string. Each character that is not URL-safe gets replaced with a percent sign followed by its two-digit hexadecimal ASCII code. So {"name":"Alice"} becomes %7B%22name%22%3A%22Alice%22%7D. Spaces can be encoded as either %20 or + depending on the context (query string versus path component). Our tool uses the standard encodeURIComponent approach, which is correct for query parameter values and the most widely compatible encoding method.

Common Use Cases for URL-Encoded JSON

The need to URL encode JSON comes up in several common development scenarios. OAuth state parameters often carry JSON payloads that encode the return URL and session context. Webhook URLs sometimes include JSON configuration in query parameters. Deep links in mobile apps pass structured data as URL parameters. Analytics tracking URLs embed JSON metadata for attribution. API gateway configurations pass JSON through URL-based routing rules. Redirect URLs carry state information as encoded JSON in query strings. In all of these cases, failing to properly URL-encode the JSON will cause data loss or errors downstream.

The Difference Between URL Encoding Methods

JavaScript provides two built-in encoding functions: encodeURI and encodeURIComponent. They encode different character sets. encodeURI leaves characters like &, =, and / unencoded because they have meaning within a full URL. encodeURIComponent encodes everything except letters, digits, and a handful of symbols, making it safe for use as a query parameter value. For JSON data, you almost always want encodeURIComponent, because JSON contains characters like & and = that would be misinterpreted as query string delimiters. Our tool uses the correct encoding method for safe JSON transmission.

Encoding and Decoding Round-Trip

A properly URL-encoded JSON string is fully reversible. The receiving end simply applies URL decoding (decodeURIComponent in JavaScript, urldecode in PHP, urllib.parse.unquote in Python) and gets back the exact original JSON. No data is lost, no characters are changed, and the JSON structure is preserved perfectly. Our tool shows you both the encoded output and confirms that decoding it produces the original input, so you can verify the round-trip integrity before using the encoded string in production.

Handling Special Characters and Unicode

JSON strings can contain Unicode characters, emoji, accented letters, and other non-ASCII content. Our URL encode JSON tool handles all of these correctly. Unicode characters are first encoded to UTF-8 bytes, and then each byte is percent-encoded. So a Japanese character might become six percent-encoded bytes. The encoding is fully standards-compliant and will be correctly decoded by any server or client that follows the URL encoding specification. You do not need to worry about character set issues - the tool handles everything automatically.

Fast, Private, No Server Needed

The URL encoding runs entirely in your browser using native JavaScript encoding functions. Your JSON data is not sent to any server, which is critical when you are encoding API keys, authentication tokens, user data, or other sensitive information that might appear in your JSON payloads. The encoding is instantaneous for any practical input size. Paste your JSON, copy the encoded result, and use it with confidence that the encoding is correct and your data remains private.