Does it accept JSON Schema or plain JSON?

Both. If the input has a top-level \"properties\" object it is treated as JSON Schema and uses each property's type, enum, and description. Otherwise it is treated as a sample object and infers the field type from each value (string, number, boolean, or array).

How are field types chosen?

Strings become text inputs (or textareas for long values), numbers become number inputs, booleans become checkboxes, arrays become a comma-separated text field, and any property with an enum becomes a select dropdown.

Can I use the generated HTML directly?

Yes. The Copy HTML button gives you clean, framework-agnostic markup with labels, name attributes derived from the property keys, and the right input types — ready to paste into a page or adapt to your component library.

Is my schema uploaded anywhere?

No. Parsing and rendering happen entirely in your browser. Your schema or sample data never leaves the page.

Structured LLM Output → HTML Form

Structured LLM output → HTML form

When you extract structured data with an LLM — using a JSON Schema or a function / tool definition — you usually need a UI for a human to review and edit the result. Hand-building that form for every schema is repetitive. This tool reads your JSON Schema or a sample object and instantly generates a matching, interactive HTML form, then hands you the markup to drop into an admin panel.

How it works

The tool first decides what you gave it: if the JSON has a top-level properties object, it is parsed as JSON Schema and each property contributes a field driven by its type, optional enum, and description. Otherwise the input is treated as a sample object and the field type is inferred from each value — strings become text inputs (long strings become textareas), numbers become number inputs, booleans become checkboxes, and arrays render as a comma-separated text field. Any property with an enum becomes a <select>. The form is rendered live so you can interact with it, and a Copy HTML button emits clean, framework-agnostic markup with proper labels and name attributes.

Tips and notes

Schema beats sample. A JSON Schema gives you enums, descriptions, and explicit types, producing a richer form than inferring from a single sample.
Long strings get textareas. Values over ~60 characters render as a multi-line field automatically, which is right for descriptions and bodies.
Names come from keys. The generated name attributes match your property keys, so wiring the form back to your data model is direct.
Everything is local. No data leaves your browser.