JSON to Erlang record
ClientDocument Erlang records from JSON.
Learn more: JSON to Erlang record
Document Erlang records from JSON.
Local processing
Document Erlang records from JSON. Parsing and output formatting run entirely in your browser—nothing is uploaded for this transform.
Nearby workflows on Toolcore
- JSON formatter — JSON format online: pretty-print, minify, validate, escape, download . once JSON text parses on this page.
- JSON type inference — Infer a readable type tree from sample JSON—objects, arrays, and primitives before codegen. once JSON text parses on this page.
- Compare JSON shapes — Compare inferred shapes of two JSON samples—added paths, missing fields, type changes—local. once JSON text parses on this page.
- JSON byte size — Measure JSON UTF-8 bytes—minified vs pretty length, characters, and lines in your browser. once JSON text parses on this page.
Common use cases
- Document Erlang records from JSON.
- Paste valid JSON, then read the transformed output below.
Common mistakes to avoid
Invalid JSON
Fix parse errors before expecting output.
FAQ
Is data uploaded?
No—all parsing and transforms run locally.
How is this different from jq?
This page focuses on one deterministic task without a filter language.
More tools
Related utilities you can open in another tab—mostly client-side.
JSON formatter
ClientJSON format online: pretty-print, minify, validate, escape, download .json.
JSON type inference
ClientInfer a readable type tree from sample JSON—objects, arrays, and primitives before codegen.
Compare JSON shapes
ClientCompare inferred shapes of two JSON samples—added paths, missing fields, type changes—local.
JSON byte size
ClientMeasure JSON UTF-8 bytes—minified vs pretty length, characters, and lines in your browser.