Text formatter

Three one-click formats: pretty-print JSON with two-space indents, convert to lowercase, or convert to uppercase by your page language's rules.

Output
—

What to know

The formatter offers three operations in the Operation menu: JSON formatter (the default), Lowercase and Uppercase. Each runs on the whole input and shows its result in the Output panel at once, ready to copy or save as chatcument-text-output.txt.

The JSON option parses your text and prints it back with an indent of two spaces, one key or array element per line. It is a strict parser, so single quotes, comments, trailing commas and unquoted keys are rejected with the message Invalid input for this operation. There is no minify or sort-keys choice.

The two case options follow the language rules of the page, not a byte-by-byte table. Lowercasing a Greek word ends it with the final-form sigma, and uppercasing the German sharp s gives SS, so the text can grow in length. Hangul, kana, Chinese characters, digits and emoji pass through untouched.

Pick JSON for API responses, config snippets and log lines that arrive as a single unreadable row. Pick a case option for tags, codes and headings. Each pass applies one operation, so to format and then change case, copy the output back into the input between the two steps.

Choose a specific task 3
Related tools 4
How to use Text formatter
  1. Open the Operation menu and choose JSON formatter, Lowercase or Uppercase for the job in front of you.
  2. Paste a one-line payload such as {"id":7,"tags":["a","b"]} to test JSON formatting before using a large response.
  3. Check the Output panel: a clean error message means the input is not strict JSON, and a pretty-printed block means it parsed.
  4. Copy the formatted text, or download it with the icon beside the copy button.

Quick answers

How many formatting operations are there?

Three: JSON formatter, Lowercase and Uppercase. Title case, sentence case and minified JSON are not offered.

Why does my JSON show an error?

The parser is strict. Single quotes, comments, trailing commas, unquoted keys and values such as NaN are not valid JSON and are rejected.

Does changing case touch Korean or Japanese text?

No. Scripts without letter case, along with digits, punctuation and emoji, pass through unchanged, so only Latin, Greek, Cyrillic and similar letters change.

Can I format JSON and lowercase it together?

Not in one pass. Format first, copy the output into the input box, then switch to Lowercase and apply the second step.