All tools

Content-Disposition Header Builder

Network

Build or parse a Content-Disposition header for a file download or inline display, with RFC 5987 support for non-ASCII filenames.

Build a Content-Disposition response header from a disposition type and filename, or paste in an existing header to see how it decodes. A filename with non-ASCII characters like accents or CJK text automatically gets an RFC 5987 filename* parameter alongside an ASCII-sanitized fallback, matching what browsers actually expect for correct download naming.

content-dispositionhttpheadersdownloadfilenamemime

How to use Content-Disposition Header Builder

  • 1.Choose inline or attachment and enter a filename to build a header.
  • 2.Copy the generated Content-Disposition header for use in your server response.
  • 3.Paste an existing header into the parse box to see its decoded type, filename, and raw parameters.

Frequently asked questions

Why does a non-ASCII filename produce two filename parameters?
Older clients only understand the plain filename parameter, which can't safely carry non-ASCII bytes, so an ASCII-sanitized fallback is included alongside the RFC 5987 filename* parameter that carries the exact UTF-8 name for clients that support it.
Does this tool upload my file?
No. It only builds or parses the header text you provide; no file is ever read or transmitted.
What disposition types are supported?
inline and attachment, the two values actually registered for the Content-Disposition response header. Arbitrary extension tokens are not generated, though the parser will still show you whatever type string a pasted header contains.

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/content-disposition-builder \
  -H "Authorization: Bearer utx_live_..." \
  -H "Content-Type: application/json" \
  -d '{"type":"attachment","filename":"report.pdf"}'

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