JSON Formatter and Validator

Validate the example

Paste the compact example into JSON input, then select Validate JSON. Foxger passes the complete text to the browser’s native JSON.parse method.

That success is useful but limited. It does not prove that available has the right number, that an API allows a notes property, or that any required field is present. Those are data or schema questions, not JSON syntax questions.

Minify the same JSON

Select Minify JSON. Foxger parses the example and recreates it without optional indentation or line-break whitespace:

{"site":"Foxger","private":true,"tools":["Slug Generator","JSON Formatter","UTM Campaign URL Builder","Hreflang Generator and Validator"],"available":4,"notes":null}

Minified JSON is harder for people to scan, but it is useful when compact text is preferred. It does not remove spaces inside a quoted string. For example, the space inside"JSON Formatter" remains part of that value.

Smaller text is not automatically a meaningful performance improvement in every application. Use minification because your destination expects or benefits from compact JSON, not as a universal requirement.

JSON can begin with an array or primitive value

Foxger accepts every top-level value that the native JSON parser accepts. A complete JSON text does not have to begin with {.

Formatting a top-level primitive such as true produces truebecause there is no nested structure to indent. Whether your destination accepts a primitive is a separate application rule.

Read an error line and column

Line

The one-based line where the browser reported or reached the problem.

Column

The one-based position within that line.

Reason

The browser’s explanation, cleaned so Foxger does not repeat an excerpt of your JSON in the error.

Foxger extracts a raw parser position when the browser provides one and converts it to line and column. Some browsers already report line and column; some messages provide no usable location. In that fallback case, Foxger still says the JSON is invalid and shows the cleaned reason without inventing coordinates.

The visible error does not include a separate nearby-text snippet. Look at the input itself, start at the reported location, and inspect backward. Missing commas and quotes often make the parser complain only when it reaches the next otherwise-correct token.

Character and UTF-8 byte counts

The input and output each show a character count and byte count. Foxger counts Unicode code points as characters and measures the text after UTF-8 encoding as bytes.

ASCII characters usually use one UTF-8 byte. The accented é and fox emoji use more, which is why the totals differ. A combined visible symbol can also contain more than one code point, so this “character” total is a documented technical count rather than a promise about every symbol a person sees.

Privacy and local processing

Parsing, formatting, minifying, counting, copying, and download preparation run through JavaScript in your browser. Foxger does not intentionally upload the JSON to a formatting API or save it in server storage.

• The workspace has no form submission and does not put JSON in the page URL.
• Tool input is not written to local storage, session storage, IndexedDB, or cookies.
• The unrelated theme preference may be stored locally if you choose Light, Dark, or System.
• Copy writes only the current output to your device clipboard after you select Copy.
• Download creates a temporary local Blob URL with the MIME type application/json;charset=utf-8.
• Input and output remain textarea text; markup-like JSON is not rendered as page HTML.

Loading Foxger still makes an ordinary page request that hosting and security systems may log. The JSON itself is not added to that request by this tool. See thePrivacy page for the site-wide distinction.

Very large JSON and exact source text

Foxger does not advertise or enforce a fixed input-size limit. That is not the same as unlimited capacity. Parsing a large document and creating another full string can use substantial browser memory and make the page slow or temporarily unresponsive.

Extreme nesting has another limit: JSON can be syntactically valid but too deeply nested for the browser to serialize. Foxger keeps the input, clears unavailable output, and reportsValid JSON — output unavailable instead of pretending the syntax is invalid.

Troubleshooting the JSON Formatter

Practice: repair a smaller Foxger object

Paste this example into the tool and select Validate JSON:

{
  "site": "Foxger",
  private: true,
  "available": 4,
}

Find the unquoted key and the comma after the final property. Repair both, validate again, then format with 2 spaces. Open the solution only after you have a valid result.

{
  "site": "Foxger",
  "private": true,
  "available": 4
}

Final checklist

• My JSON validates successfully.
• I understand that formatting changes layout and may normalize source representation.
• I chose and applied the indentation I want.
• I repaired errors before copying or downloading.
• I know JSON keys and strings use double quotes.
• I know valid JSON does not guarantee correct application data.
• I reviewed the size and sensitivity of the data before pasting it into any website.