All Tools
Categories
XML Tools 64 Email Marketing Tools 55 Import-Export Tools 50 JSON Tools 36 Text Tools 12 Shipping Freight Tools 5 Calculator 4 Marketing Tools 3
About Contact Privacy

JSON to CSON

Convert a JSON document to CSON in one click: CoffeeScript-style keys, single-quoted strings, block arrays and clean indentation. Download ready. All client-side.

JSON Input
Waiting for input
CSON Output
CSON uses key: value lines, indentation instead of braces, and block arrays. Simple keys stay bare; complex strings fall back to double-quoted JSON-style escapes.

About JSON to CSON

CSON trades JSON punctuation for readability: colons instead of colons-and-quotes, indentation instead of braces, arrays as blocks. Config files in that style are genuinely easier to scan — but most data starts life as JSON, and writing CSON by hand means re-indenting everything and remembering the quoting rules.

Convert JSON to CSON produces idiomatic CSON from any JSON document in one click: bare keys, single-quoted strings, block arrays with objects wrapped in braces, and clean two-space indentation. Paste, copy, done.

Features

  • Idiomatic output: Bare keys, single-quoted strings, block arrays and indented nesting.
  • Block arrays: key: [ lines with indented elements and a matching closing bracket.
  • Objects in arrays: Multi-object arrays use braces so elements stay unambiguous.
  • Smart quoting: Simple names stay bare; unusual keys and complex strings are quoted automatically.
  • Full type support: Numbers, booleans, nulls and nested structures all survive.
  • Live preview: The CSON output updates as you type.
  • Copy and download: Export the result as a .cson file instantly.
  • Private: All processing happens in your browser; nothing is uploaded.

How to Use

  1. Paste your JSON into the input pane.
  2. Review the live CSON — quoting and indentation are applied automatically.
  3. Copy or download the .cson file.

Examples

Example 1 — Tooling migration. A team moves a config from JSON to CSON for a legacy CoffeeScript tool, converting the payload and verifying the structure reads cleanly before deployment.

Example 2 — Legacy package config. A developer converts a modern JSON config into the CSON shape expected by older Atom-style packages and editor tooling.

Example 3 — Readable defaults. An architect publishes a CSON sample config in documentation because the block style is easier to review in diffs than nested JSON.

Example 4 — Round-trip editing. A developer converts JSON to CSON, hand-edits the friendly format, and converts back with the companion tool.

Benefits

  • Friendly format: CSON output is readable and diff-friendly.
  • Correct by construction: Quoting and indentation follow the format rules automatically.
  • Lossless types: Numbers, booleans and nesting survive conversion.
  • Zero data movement: The document is converted locally and never uploaded.
  • Instant results: Live output updates with every keystroke.

Frequently Asked Questions

What is CSON?
CSON (CoffeeScript Object Notation) is the data format used by CoffeeScript tooling, older Atom packages and the CSON npm ecosystem. It looks like JSON without the noise: keys with colons, single-quoted strings, block arrays and indentation instead of braces.
How are objects written?
Objects become indented blocks: key: value lines where nested objects follow on their own indented lines and arrays open with key: [ and close with a matching ]. No commas anywhere.
How are strings quoted?
Strings use single quotes by default, with internal quotes and backslashes escaped. Strings containing newlines or non-ASCII characters fall back to double-quoted JSON-style escapes for safety.
Do key names need quotes?
Only when they contain characters outside the bare-key alphabet. Simple names like company or max_items stay unquoted; unusual keys are emitted as quoted strings automatically.
Can the output be converted back?
Yes. The companion CSON to JSON tool parses this output back into the identical JSON structure, including numbers, booleans, nulls, arrays and nesting.
Is my JSON uploaded anywhere?
No. Conversion happens entirely in your browser. Nothing is uploaded, stored or logged.