How to use HTTP Multipart Body Inspector
- Enter the Content-Type with its declared boundary.
- Choose pasted UTF-8 sample text or one file containing actual body bytes.
- Review part sizes, headers and previews before downloading test copies.
Example: HTTP Multipart Body Inspector
Inspect supplied multipart body bytes as bounded parts, with boundary findings and local extracted test copies.
You add
Body source: "text"
Content-Type header: "multipart/form-data; boundary=----Wave52BoundaryExample"
Sample body: "------Wave52BoundaryExample\r\nContent-Disposition: form-data; name=\"title\"\r\n\r\nQuarterly report\r\n------Wave52BoundaryExample\r\nContent-Disposition: form-data; name=\"notes\"; filename=\"notes.txt\"\r\nContent-Type: text/plain; charset=utf-8\r\n\r\nLine one\r\nLine two\r\n------Wave52BoundaryExample\r\nContent-Disposition: form-data; name=\"payload\"; filename=\"blob.bin\"\r\nContent-Type: application/octet-stream\r\n\r\nsynthetic binary placeholder\r\n------Wave52BoundaryExample--"
Body file: []
Preview characters per part: "120"
You get
Parsed 3 parts totalling 62 B.
Options
- Text versus file
- Pasted text is a UTF-8 test sample and browser textareas can normalize newlines. File mode preserves the supplied body bytes for binary inspection.
- Preview length
- The selected character allowance bounds text shown in the report. Extracted parts remain separate local files under the tool’s extraction limits.
Supported inputs and limits
One body up to 2 MiB, 64 parts and a 1–70-character boundary. Bounded supported multipart parsing; nested/encoded-body interpretations follow the reported subset. No submission or execution; extracted copies are not trusted files.
Where your input is processed
This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.
Extracted parts can contain private content
A multipart body can include form values, file content and identifying filenames. Nothing is submitted or executed, but reports and extracted copies still need inspection before sharing. A tolerated bare-line-feed body is identified separately from strict CRLF multipart syntax.
Questions about HTTP Multipart Body Inspector
Does it contact the form destination?
No. It reads only supplied text or file bytes.
Is a text sample byte-identical to an upload?
Not necessarily; use file mode for exact binary bytes and newline preservation.
Are extracted files safe to open?
The parser does not establish that their content is harmless.