Text Case Converter
Convert text between camelCase, snake_case, kebab-case and more.
parseHttpResponseHandler
JavaScript variables
ParseHttpResponseHandler
Class and component names
parse_http_response_handler
Python, SQL columns
PARSE_HTTP_RESPONSE_HANDLER
Environment variables
parse-http-response-handler
URLs, CSS classes
Parse-Http-Response-Handler
HTTP headers
parse.http.response.handler
Config keys
parse/http/response/handler
File paths
Parse Http Response Handler
Headings
Parse http response handler
Body copy
parsehttpresponse handler
PARSEHTTPRESPONSE HANDLER
pArSeHtTpReSpOnSe hAnDlEr
PARSEhttprESPONSE HANDLER
About this tool
Paste any identifier or sentence and see it in every common casing convention at once, so you can grab the one you need without hand-editing. Handles multi-word input, existing delimiters and acronyms sensibly.
How to use it
- Paste your text or identifier.
- Read every conversion at once.
- Copy the one you need.
Which convention goes where
Casing conventions are arbitrary but strongly held, and using the wrong one marks code as foreign immediately.
| Case | Used for |
|---|---|
camelCase |
JavaScript and Java variables, JSON keys |
PascalCase |
Classes, React components, TypeScript types |
snake_case |
Python, Ruby, SQL columns and tables |
CONSTANT_CASE |
Environment variables, constants |
kebab-case |
URLs, CSS classes, HTML attributes, npm packages |
Train-Case |
HTTP headers — Content-Type |
The one that actually matters technically is kebab-case for URLs. Google treats a hyphen as a word separator and an underscore as a word joiner, so my_blog_post is read as one token while my-blog-post is read as three words.
Everything else is convention — but conventions are what make a codebase readable, and mixing them within one file is worse than picking the "wrong" one consistently.
How acronyms are handled
Acronyms are where naive case converters produce nonsense, because the boundary rules that work for normal words break on a run of capitals.
Splitting parseHTTPResponse naively on every capital gives parse H T T P Response, and the snake_case output becomes parse_h_t_t_p_response.
This converter treats a run of capitals followed by a capital-plus-lowercase as one unit, so:
parseHTTPResponse -> parse_http_response
XMLHttpRequest -> xml_http_request
getUserID -> get_user_id
The style question underneath is whether acronyms should be capitalised in camelCase at all. Google's style guides say no — parseHttpResponse, XmlHttpRequest — precisely because it makes boundaries unambiguous both for humans and for tools like this one. Microsoft's convention capitalises two-letter acronyms only.
Either is fine. Consistency is what matters, and the PascalCase output here follows the unambiguous form.
Frequently asked questions
- How are acronyms handled?
- Runs of capitals are treated as a single word, so "parseHTTPResponse" becomes "parse_http_response" rather than splitting on every letter.
- Does it work on whole sentences?
- Yes. Title case and sentence case are designed for prose, while the programming cases will collapse a sentence into a single identifier.
- Is my text transmitted?
- No. Every conversion is a string operation performed in the page, which is why all the variants update the instant you type.