All tools

Multipart/form-data Body Parser

Code

Paste a raw multipart/form-data request body plus its boundary (or a full Content-Type header to extract the boundary from) and get back each part's field name, filename, headers, and decoded value

Paste a captured multipart/form-data request body, the format a browser sends for a file-upload form, and see it broken down into its individual parts: each field's name, filename if it's a file field, headers, and decoded value. Give the boundary directly, or paste a full Content-Type header value and it pulls the boundary parameter out automatically, quoted or not. This is exactly what's needed when debugging a captured file-upload request from a proxy log or browser DevTools export, since nothing else on the site decodes an existing multipart body: the cURL Builder only generates simple multipart fields going the other direction.

multiparthttpform-datarfc7578parserweb-dev

How to use Multipart/form-data Body Parser

  • 1.Paste the raw multipart/form-data body, including its boundary lines, into the body field.
  • 2.Enter the boundary directly, or paste the request's full Content-Type header value and let it extract the boundary automatically.
  • 3.Review each parsed part: its field name, filename for file fields, headers, and decoded value.

Frequently asked questions

Can this decode a real binary file that was uploaded?
No, it parses the body as text. A binary file part (an image or PDF, for example) will show up with its part detected and flagged as binary, but its raw bytes won't render as anything meaningful since the tool never receives true binary data through a text field.
What if I don't know the exact boundary string?
Paste the request's Content-Type header value instead of the bare boundary, for example "multipart/form-data; boundary=----WebKitFormBoundaryABC123", and the tool extracts the boundary parameter for you, whether or not it's quoted.
Why did it say no parts were found?
The boundary you entered doesn't match the one actually used in the body's --boundary delimiter lines. Double-check you copied the exact boundary string, including any leading dashes some browsers include as part of the value itself.
Is my data sent anywhere?
No, the parsing runs entirely in your browser. Nothing is transmitted to a server or stored.

Use via API, SDK, or MCP

cURL# Free: 1,000 req/day · Pro: 10,000 req/day
curl -X POST https://api.utilix.tech/v1/tools/multipart-form-parser \
  -H "Authorization: Bearer utx_live_..." \
  -H "Content-Type: application/json" \
  -d '{"body":"------WebKitFormBoundaryABC123\r\nContent-Disposition: form-data; name=\"username\"\r\n\r\nalice\r\n------WebKitFormBoundaryABC123--\r\n","boundary":"----WebKitFormBoundaryABC123","contentType":"multipart/form-data; boundary=----WebKitFormBoundaryABC123"}'

Get an API key from your dashboard · Full API docs →

Related tools

User-Agent ParserParse a browser User-Agent string into browser, engine, OS, and device typeNetworkAccept-Language Header Parser / BuilderBuild an Accept-Language request-header value from locale/quality pairs, sorted by preference, or parse an existing header into its ranked locale/quality entriesNetworkCache-Control Header BuilderBuild and explain an HTTP Cache-Control response header from directives like max-age, s-maxage, no-store, and immutableNetwork