How to use HTML Form Serialization Tester
- Paste exactly one form. Set checked attributes and submit-button values in the HTML; file/image controls and form-associated external controls are unsupported.
- Optionally use Named control overrides or advanced JSON for existing text/select control names. Multiple-select lists use arrays; checkbox/radio state must be edited in the HTML.
- Enter the name of one enabled submit button to include, or leave it blank. Review the updated controls, decoded successful entries and encoded body previews.
- Download the UTF-8 URL-encoded/multipart bodies or report. No action URL is contacted and no submission script runs.
Example: HTML Form Serialization Tester
Override name with Sam, include the checked updates field and action submitter, and normalize the note’s line break to CRLF.
Options
- Submitter
- A named enabled submit button contributes its value. Leave the name blank when no button should be included.
- Overrides
- Text overrides change text/select values. Checkboxes and radios keep their supplied checked attributes; multiple selects accept an array.
- One form (HTML)
- Up to 200,000 characters and 500 controls. Parsed in a detached template, never submitted.
- Override named text/select controls (JSON)
- Arrays select multiple options. Checkboxes keep their supplied checked state.
Supported inputs and limits
- One inert form within 200,000 HTML characters, 500 controls and 1,000 resulting entries.
- Up to 100 override names in 20,000 JSON characters.
- File/image controls and any explicit external form ownership are refused.
- Uses this browser’s native FormData successful-control behavior, then normalizes names/values to CRLF in local UTF-8 test bodies.
- No request, destination encoding, JavaScript submit handler or uploaded-file body is reproduced.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
The report contains entered form values
Hidden successful controls can be included just like visible text fields. Inspect the report before sharing it, especially when testing copied forms. Actual browser FormData behavior is used within the supported subset, but no form is submitted and the destination’s scripts or encoding are not tested.
Questions about HTML Form Serialization Tester
Does a disabled control get submitted?
Disabled controls are omitted by native FormData rules, as are unchecked checkboxes/radios and controls without a successful name. A named enabled submitter is included only when selected here. The decoded entries show the result for this browser.
Can I test uploaded file bodies here?
File controls are excluded from this text-form model; use the multipart inspector for supplied body bytes.
Will the action URL be contacted?
No. The form stays detached and only local test bodies are created.