Which field types are supported?

text, email, number, tel, url, password, date, textarea, and select with comma-separated options. An unrecognized type falls back to a plain text input.

Does it generate a validation schema?

Yes. Alongside the HTML it emits a JSON Schema with a type for each field, enums for select options, and a required list built from your required flags.

Is my form design uploaded anywhere?

No. The form is generated entirely in your browser and nothing is uploaded. Drafts are saved only in this browser.

Does the exported form submit data anywhere?

No. The exported HTML has no action wired up. Point the form at your own endpoint or handler, and validate submissions on the server with the generated JSON Schema.

JSON form builder

A JSON form builder turns a field list into a working HTML form and a JSON Schema that describes the data the form collects.

Define form fields in simple lines, preview the form live, and export the HTML with a matching JSON Schema for validation. Free and made in your browser.

Browser-sideNo accountCopy, download, or print

Last reviewed 30 Oct 2026

Your inputs are saved as a draft in this browser only. Nothing is uploaded.

Jump to result

Result

Form titlePartner onboarding request

Fields5

Required fields4

Thememodern

Field configuration

Name	Type	Required	Label
fullName	text	required	Full name
workEmail	email	required	Work email
company	text	required	Company
integrationNeed	select	required	Integration need
notes	textarea	optional	Context

HTML form:

<form class="apyrn-form apyrn-form--modern">
  <h2>Partner onboarding request</h2>
  <p>Capture the minimum information needed to qualify a partner API onboarding conversation.</p>
  <label for="fullName">Full name *</label>
  <input type="text" id="fullName" name="fullName" placeholder="Enter full name" required />
  <label for="workEmail">Work email *</label>
  <input type="email" id="workEmail" name="workEmail" placeholder="name@company.com" required />
  <label for="company">Company *</label>
  <input type="text" id="company" name="company" placeholder="Company name" required />
  <label for="integrationNeed">Integration need *</label>
  <select id="integrationNeed" name="integrationNeed" required>
    <option value="Unified API">Unified API</option>
    <option value="Workflow API">Workflow API</option>
    <option value="Partner API">Partner API</option>
  </select>
  <label for="notes">Context</label>
  <textarea id="notes" name="notes" placeholder="Systems, constraints, timeline"></textarea>
  <button type="submit">Submit request</button>
</form>

Validation schema (JSON Schema):

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Partner onboarding request",
  "type": "object",
  "properties": {
    "fullName": {
      "type": "string",
      "title": "Full name"
    },
    "workEmail": {
      "type": "string",
      "title": "Work email"
    },
    "company": {
      "type": "string",
      "title": "Company"
    },
    "integrationNeed": {
      "type": "string",
      "title": "Integration need",
      "enum": [
        "Unified API",
        "Workflow API",
        "Partner API"
      ]
    },
    "notes": {
      "type": "string",
      "title": "Context"
    }
  },
  "required": [
    "fullName",
    "workEmail",
    "company",
    "integrationNeed"
  ]
}

HTML form:

<form class="apyrn-form apyrn-form--modern">
  <h2>Partner onboarding request</h2>
  <p>Capture the minimum information needed to qualify a partner API onboarding conversation.</p>
  <label for="fullName">Full name *</label>
  <input type="text" id="fullName" name="fullName" placeholder="Enter full name" required />
  <label for="workEmail">Work email *</label>
  <input type="email" id="workEmail" name="workEmail" placeholder="name@company.com" required />
  <label for="company">Company *</label>
  <input type="text" id="company" name="company" placeholder="Company name" required />
  <label for="integrationNeed">Integration need *</label>
  <select id="integrationNeed" name="integrationNeed" required>
    <option value="Unified API">Unified API</option>
    <option value="Workflow API">Workflow API</option>
    <option value="Partner API">Partner API</option>
  </select>
  <label for="notes">Context</label>
  <textarea id="notes" name="notes" placeholder="Systems, constraints, timeline"></textarea>
  <button type="submit">Submit request</button>
</form>

Validation schema (JSON Schema):

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Partner onboarding request",
  "type": "object",
  "properties": {
    "fullName": {
      "type": "string",
      "title": "Full name"
    },
    "workEmail": {
      "type": "string",
      "title": "Work email"
    },
    "company": {
      "type": "string",
      "title": "Company"
    },
    "integrationNeed": {
      "type": "string",
      "title": "Integration need",
      "enum": [
        "Unified API",
        "Workflow API",
        "Partner API"
      ]
    },
    "notes": {
      "type": "string",
      "title": "Context"
    }
  },
  "required": [
    "fullName",
    "workEmail",
    "company",
    "integrationNeed"
  ]
}

How to use it

Enter the form title, description, and submit button text.
Define fields one per line as name|type|required|Label|Placeholder|Option A,Option B.
Pick a theme — modern, minimal, or corporate — and check the live preview.
Copy the generated markup and validation schema, or use Download HTML.

Questions

Which field types are supported?: text, email, number, tel, url, password, date, textarea, and select with comma-separated options. An unrecognized type falls back to a plain text input.
Does it generate a validation schema?: Yes. Alongside the HTML it emits a JSON Schema with a type for each field, enums for select options, and a required list built from your required flags.
Is my form design uploaded anywhere?: No. The form is generated entirely in your browser and nothing is uploaded. Drafts are saved only in this browser.
Does the exported form submit data anywhere?: No. The exported HTML has no action wired up. Point the form at your own endpoint or handler, and validate submissions on the server with the generated JSON Schema.