Header-Case Converter — Free Online Tool
What is Header-Case Converter?
Header-Case is identical to Train-Case — it capitalises the first letter of each word and joins them with hyphens, producing output like Content-Type or Accept-Encoding. It is named specifically for its primary use case: formatting HTTP request and response header names.
While HTTP/2 normalises headers to lowercase during transmission, Header-Case remains the standard display format in documentation, API tools, and developer interfaces.
When to use Header-Case Converter?
Use Header-Case for HTTP header names like Content-Type, Authorization, X-API-Key, and Cache-Control. API documentation, Postman collections, and REST client interfaces conventionally display headers in this format.
If you are working with Kebab Case identifiers but need title capitalisation, this tool adds it. For all-uppercase hyphenated output like COBOL naming, use the COBOL-CASE Converter.
How to use this tool
- 1Paste your text
- 2Click 'Convert' for Header-Case output
- 3Copy for HTTP header names
The tool detects word boundaries and capitalises the first letter of each word. HTTP headers are technically case-insensitive, but Header-Case is the conventional display format for readability.
Examples
| Input | Output |
|---|---|
| content type | Content-Type |
| x api key | X-Api-Key |
| cache control | Cache-Control |
| accept encoding | Accept-Encoding |
| authorization bearer | Authorization-Bearer |
Rules & Behavior
- The first letter of each word is capitalised, with the remaining letters in lowercase. This produces the standard Title-Cased-Hyphenated pattern used for HTTP headers.
- Words are separated by hyphens (-). Spaces, underscores, dots, and other separators are replaced with hyphens.
- This is the standard formatting for HTTP header names. While HTTP/2 normalises headers to lowercase during transmission, Header-Case remains the conventional human-readable display format.
Related Tools
Frequently Asked Questions
What is Header-Case?
Header-Case capitalises each word and separates them with hyphens, like Content-Type, Cache-Control, and X-Forwarded-For. It is the conventional display format for HTTP request and response header names. Also known as Train-Case, it makes headers readable and consistent.
Is Header-Case the same as Train-Case?
Yes. Header-Case and Train-Case describe the exact same convention — capitalised words separated by hyphens. The term 'Header-Case' emphasises the HTTP header context, while 'Train-Case' describes the visual pattern of connected capitalised words.
Why is it called Header-Case?
Because its primary use is formatting HTTP request and response header names. Standard HTTP headers like Content-Type, Authorization, Accept-Language, and X-API-Key all follow this convention. The name directly reflects its most common application.
Are HTTP headers case-insensitive?
Yes, HTTP/1.1 headers are case-insensitive by specification, and HTTP/2 normalises all headers to lowercase. However, Header-Case (Title-Cased-With-Hyphens) remains the standard display format in documentation, Postman, cURL output, and browser developer tools for readability.
What's the difference from Title Case?
Title Case is for human-readable titles with spaces between words (The Quick Brown Fox). Header-Case uses hyphens instead of spaces and follows the same first-letter capitalisation but is designed for code identifiers, not prose.