ToolForge

JSON

JSON has the odd distinction of being simple enough to learn in ten minutes and strict enough to reject your file for a reason you cannot see. Most of the time it just works; the rest of the time you are staring at "Unexpected token } in JSON at position 412" wondering which of four hundred lines is at fault.

This cluster covers both halves. The format itself — its six value types, the handful of grammar rules, and the parts of the specification that surprise people who have used it for years. And the failure modes: what each parser error actually means, why a payload that works in JavaScript is rejected as JSON, and what happens to a sixteen-digit number on its way through.

ToolForge has a dozen tools in this area, and the guides here sit alongside them rather than duplicating them. Where a tool page explains how to operate the widget, these explain the format underneath it — with the specification cited, because JSON is one of the few subjects where the primary sources are short, free and worth reading.

Start with the guide

Guide

What Is JSON?

JSON is a text format for structured data, with six value types and a grammar you can read in an afternoon. What it is, where it came from, and where it bites.

Tools for this

The tools these guides refer to, most relevant first.

Guides & tutorials

Comparisons

Troubleshooting

Reference

Frequently asked questions

Is JSON a programming language?

No. It is a data format — a set of rules for writing structured values as text. The name comes from JavaScript, whose object syntax it borrowed, but it defines no behaviour, no variables and no logic. ECMA-404 is explicit that it specifies syntax only and deliberately says nothing about what the data means.

Why does JSON not allow comments?

Because the grammar has no production for them, and a conforming parser must reject anything the grammar does not permit — ECMA-404 defines the syntax exhaustively and comments are simply not in it. The omission is deliberate rather than an oversight. Formats that do allow comments, such as JSON5, JSONC and YAML, are separate formats even where they look similar.

Do JSON keys have to be in a particular order?

No, and you cannot rely on order being preserved either. RFC 8259 notes that parsing libraries differ over whether they expose the ordering of object members at all. Treat an object as an unordered bag of named values; if sequence matters, use an array.

Is JSON secure to paste into an online tool?

It depends entirely on the tool. Every JSON tool on ToolForge runs in your browser and sends nothing anywhere, which matters because real payloads carry tokens, customer records and internal identifiers. Before pasting a production response into any other site, check where it is processed.

Keep looking

Buy Me a Coffee