JSON URL Encoder and Decoder

Percent encode a JSON document so it survives a query string, or decode one back into the document it came from.

Direcao Space is a plus sign

JSON

Encoded

O resultado aparece aqui.

Funciona inteiramente no seu navegador.

Sobre esta ferramenta

A URL cannot carry a JSON document as it stands. Braces, quotes, spaces and everything above ASCII have to be percent encoded first. This encodes the way encodeURIComponent does, one UTF-8 byte at a time, leaving alone only the characters that are safe anywhere in a URL. Decoding gathers the bytes and reads them as UTF-8 once at the end, which is what stops one accent arriving as two replacement characters. The single option is the difference between a query string and a form submission: in a form a space is written as a plus sign, and everywhere else a plus sign means a literal plus. Assuming the wrong one is the most common way an encoded document arrives corrupted, so it is a toggle rather than a guess. Failures are kept apart too: a percent sign without two hexadecimal digits after it is reported at the character it sits on, and bytes that do not decode to text are reported as their own problem.

Como usar

Choose Encode or Decode, then paste your document into the left pane.
Turn the plus sign option on if the text came from, or is going into, a form submission.
Press Convert, then copy the result or download it as a file.

Perguntas frequentes

Which characters get encoded?

Everything except letters, digits and the punctuation that is safe anywhere in a URL: hyphen, underscore, full stop, exclamation mark, tilde, asterisk, apostrophe and round brackets. That is the same set encodeURIComponent leaves alone, so the output matches what a browser or a JavaScript library produces for the same document. Everything else becomes a percent sign and two hexadecimal digits for each UTF-8 byte, which is why one accented letter becomes two escapes and a musical symbol becomes four.

Why is a space sometimes a plus sign?

Because a form submission uses a different encoding from the rest of a URL. In the form encoding, which is what a submitted form and many API clients produce, a space is a plus sign. In a path or an ordinary query string a space is written as an escape and a plus sign is a literal plus. Decoding with the wrong assumption turns every plus in your data into a space, or leaves every space as a plus, so this tool asks rather than guesses.

Is percent encoding the same as escaping?

No. They solve different problems and are often needed together. Escaping puts a document inside a JSON string using backslashes. Percent encoding puts a document inside a URL using percent signs and hexadecimal digits. A document travelling as a query parameter inside a JSON body needs both, applied in the right order. Both tools are on this site, and neither changes your data.

Does percent encoding protect or hide my data?

No. Percent encoding is not encryption, and it is not even obfuscation in any real sense: anyone who sees the encoded text can decode it back with a tool exactly like this one, no key or password involved. It exists to make a document safe to place inside a URL, not to make it private. If a document needs to stay confidential, encrypt it before it travels, and treat the encoded form on this page as exactly as visible as the original.

Ferramentas relacionadas

JSON Escape and Unescape

JSON URL Encoder and Decoder

Atalhos de teclado

Dados locais

Arquivos abertos recentemente

Compartilhar via link

Abrir o link compartilhado em

JSON

Carregar de uma URL

Encoded

Sobre esta ferramenta

Como usar