Local references. Tool-specific titles, descriptions and edge cases replace generic translated copy. Visible questions and structured data stay aligned.
Workflows. Reviewed schemas and downloadable examples support QA fixtures, SQL seeds and spreadsheet demos; a task directory links the tools together.
Privacy and measurement. Optional analytics records coarse successful actions after consent; schemas, values, filenames and share payloads are excluded. Product documentation explains optional cloud sync and the conditions for repeatable output.
93 field types and five regional customer templates. Native names, postcode/PIN references, fictional addresses, invalid phone prefixes and TEST-marked negative identity fixtures cover Türkiye, China, India, Russia and Germany.
Data integrity. Converters reject duplicate or flattened column collisions, handle reserved object keys, keep empty text distinct from null and inspect late format conflicts. CLI and MCP reject invalid schemas and failed constraints.
Local workspace. Reversible backup restore, field search, bulk blank settings, conflict choices and related users/orders/order_items fixtures. Large text exports stream in a cancellable worker; embedded previews use the full logical row count.
Cloud and releases. Concurrent edits are merged through transactions. Share creation and revocation enforce an atomic 50-link quota with expiry. Failed cleanup keeps account deletion retryable. CI tooling is pinned and cached; previews are requested with a label and rules deploy alongside Hosting.
A JSON formatter and validator that does not rewrite your data. It reads JSON with its own parser rather than JSON.parse, so 12345678901234567890 keeps its digits, 19.90 keeps its zero, keys keep their order and a duplicate key is reported instead of silently dropped. Errors name the line and column and say which of the usual mistakes it is.
JSON to YAML and YAML to JSON. The writer quotes every string a YAML 1.1 or 1.2 reader would retype — NO, yes, 007, 12:30, dates. The reader follows YAML 1.2 and handles anchors, merge keys, block scalars and multiple documents.
JSON to XML, the mirror image of the XML to JSON converter: @ keys become attributes, arrays repeat their element, and keys that are not legal XML names are repaired.
CSV to Excel, Excel to CSV and Excel to JSON. CSV goes into a real .xlsx without Excel turning 02134 into 2134 or a 16-digit ID into 4.24E+15; workbooks come out with their dates as ISO 8601 rather than serial numbers like 45292. Nothing is uploaded.
Four more generators:random numbers (uniform or bell curve), lorem ipsum, IP addresses from the documentation-only ranges, and random strings from a pattern or a regex. The number and lorem ipsum widgets can output plain text.
Embed a sample in your docs.Copy embed code, under “More schema actions” in the builder, copies an iframe showing up to 25 rows of your schema — fixed by its seed, if it has one — and a link back to it. The generator pages also open faster: they now show a sample at once and load the generator engine after the page is up.
Phone numbers in CSV. The guard that stops Excel from running a cell as a formula prefixed every value starting with + or - with an apostrophe — so every +1 (415) … arrived as '+1 (415) …. Values made only of digits and phone punctuation are now left alone, and the guard itself is a checkbox next to Header row.
Phone fields default to fictional numbers. New Phone Number fields use +1 (###) 555-01##, the North American block reserved for fiction, instead of a pattern that could produce a real subscriber’s number. Saved schemas keep the format they were saved with. More on safe phone ranges.
Avatar URLs without a third party. The Avatar URL field has a host option: pravatar (real placeholder images, as before) or example, which stays on the reserved example.com domain and never reaches anyone.
Share links from the builder. Opening a /#s= or /#g= link while the builder was already open changed only the address bar. It now loads the shared schema.
Behind the scenes. Large downloads are written in slices instead of one frozen-tab string, the offline cache no longer pins unversioned files, deleting an account asks you to confirm it is you before anything is removed, and the Content-Security-Policy no longer allows arbitrary inline scripts.
Every field type has its own anchor./api/types.json publishes a documentation link per type, and 67 of the 68 pointed at a fragment that did not exist — they all landed at the top of the reference. They resolve now, and each type carries a real definition in the page's structured data instead of just a name.
Section anchors and a contents list. 337 headings had no id, so a page could only be linked as a whole. Every content section is addressable now, and the longer pages open with an "On this page" list.
The standards are linked. Pages that mention RFC 4180, RFC 2606 and 6761, RFC 4122, ISO 8601, E.164 or JSON Schema draft 2020-12 now link the document that defines them, rather than asking you to take the claim on trust.
Two counts were wrong. The site advertised a vague “60+” in 24 places and the exact number in a handful of others; there are 93 field types. It also claimed nine name locales where there are eleven locales — the ninth entry in the dropdown is “any”, which is not one. Both counts are asserted by the test suite now, against the generator itself.
Five format converters.CSV to JSON, JSON to CSV, CSV to SQL, JSON to SQL and XML to JSON. They run in your browser like everything else here, so nothing is uploaded. Each page documents the decisions the conversion forces — what happens to a leading zero, to a nested object, to a repeated XML element.
Static sample files. The sample pages now offer real files under /samples/: users, employees, orders and sensor readings, as CSV, JSON and SQL, at 100 and 1,000 rows. They are generated from a fixed seed and committed, so a link to one keeps returning the same bytes. Public domain, no attribution needed.
A generator on every generator page.UUIDs, names, emails and the rest now generate a live example on the page instead of describing one. The button beside it opens the full builder on that page's schema — it used to open the default Users template, which was unhelpful on a page about IBANs.
A machine-readable field catalogue at /api/types.json, generated from the generator itself.