HTTP Multipart Body Inspector

Inspect multipart headers and byte counts, coordinate boundaries and download bounded part copies.

On-device No sign-up Free to use

Inspect multipart body controls

Drop your text file here

or choose one from your device

One file up to 2 MiB. Read locally; the bytes are never uploaded.

    ?

    Used when the source is "Paste a sample body". Up to 2 MiB of UTF-8 text and 64 parts. The value is encoded exactly as supplied, but a browser textarea normally submits LF line endings, so choose a file when exact CRLF or binary bytes matter.

    ?

    A pasted sample is encoded as UTF-8 text. A chosen file supplies the real bytes, including binary content.

    ?

    A multipart media type with a boundary parameter of 1 to 70 characters. The boundary cannot contain a line break.

    ?

    How much of each text part to show in the report. Extracted test parts are written up to the extraction limit.

    Result

    Showing an example.

    Inspect three sample parts: pasted text gives 61 B after textarea newline normalization; a file preserving CRLF gives 62 B. The .bin-named part contains sample text.

    Pasted sample: Parsed 3 parts totalling 61 B.
    File preserving the sample’s CRLF: Parsed 3 parts totalling 62 B.
    The .bin-named part contains sample text, not a real binary payload.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/http-multipart-body-inspector · 20 November 2026

    Was this helpful?

    How to use HTTP Multipart Body Inspector

    1. Enter the multipart Content-Type with its boundary, then choose pasted UTF-8 sample text or one file containing the actual body bytes.
    2. For exact CRLF or binary input, use file mode. Textareas can normalize newlines, which the report identifies separately.
    3. If changing the helper’s boundary token, select Apply boundary. It updates header and delimiter lines for pasted text, but only the header in file mode; the file itself must already match.
    4. Select Inspect multipart body, then review part headers, sizes and previews. Download the report or bounded copies if needed: only the first 12 parts, with at most 32 KiB copied from each.

    Example: HTTP Multipart Body Inspector

    Inspect three sample parts: pasted text gives 61 B after textarea newline normalization; a file preserving CRLF gives 62 B. The .bin-named part contains sample text.

    You add
    Body source: text; Content-Type header: multipart/form-data; boundary=LocalBodyBoundary; Sample body: --LocalBodyBoundary Content-Disposition: form-data; name="title" Quarterly report --LocalBodyBoundary Content-Disposition: form-data; name="notes"; filename="notes.txt" Content-Type: text/plain; charset=utf-8 Line one Line two --LocalBodyBoundary Content-Disposition: form-data; name="payload"; filename="blob.bin" Content-Type: application/octet-stream synthetic binary placeholder --LocalBodyBoundary--; Preview characters per part: 120
    You get
    Pasted sample: Parsed 3 parts totalling 61 B. File preserving the sample’s CRLF: Parsed 3 parts totalling 62 B. The .bin-named part contains sample text, not a real binary payload.

    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.
    Body source
    A pasted sample is encoded as UTF-8 text. A chosen file supplies the real bytes, including binary content.
    Content-Type header
    A multipart media type with a boundary parameter of 1 to 70 characters. The boundary cannot contain a line break.
    Sample body
    Used when the source is "Paste a sample body". Up to 2 MiB of UTF-8 text and 64 parts. The value is encoded exactly as supplied, but a browser textarea normally submits LF line endings, so choose a file when exact CRLF or binary bytes matter.
    Body file
    One file up to 2 MiB. Read locally; the bytes are never uploaded.
    Preview characters per part
    How much of each text part to show in the report. Extracted test parts are written up to the extraction limit.

    Supported inputs and limits

    • One body up to 2 MiB, 64 parts, 32 header lines per part and a 1–70-character boundary.
    • Downloaded part copies include only the first 12 parts and at most the first 32 KiB of each; larger parts are incomplete copies even though the report gives their full sizes.
    • Preview input allows 0–2,000 characters, while the table additionally caps each preview at 120.
    • Nested/encoded multipart extensions are not fully interpreted.
    • No request, execution or path following; file content is not certified safe.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved 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.

    Page updated · Project managed by Tony Hines · Report a problem with HTTP Multipart Body Inspector