Why it matters
A JSON Schema already says what a form should collect: which fields, of what type, which are required, and the limits on each. Writing the form by hand repeats all of that and drifts out of step with the schema the API actually checks.
This builder reads the schema and draws the form, choosing a sensible input for each field, then validates the data against the same schema as you type. Errors appear beside the field and in a summary at the top that links to each one. The markup uses real labels, fieldsets, hints and aria-describedby, so it's a good starting point for an accessible form.
How to use it
- Paste your JSON Schema.
- Fill in the form to try it.
- Read the errors and the JSON the form produces.
- Copy the HTML if you want to build on it.
FAQ
Which JSON Schema versions does it support?
Draft 2020-12, 2019-09 and draft 7 keywords for drawing the form, and the full validator from the JSON Schema Validator for checking it.
How does it choose the inputs?
From the type, format and enum of each property: a date format becomes a date picker, an enum becomes a select, a boolean a checkbox and so on.
Is the form accessible?
Every field has a label, hints and errors are linked with aria-describedby, groups use fieldset and legend, and errors are listed in a summary linking to each field.
Is anything sent anywhere?
No. The form is built and checked in your browser.