COBOL-CASE Converter
Convert text to COBOL-CASE online - uppercase words joined by hyphens. Free COBOL case converter, no signup required.
Three steps to get started
Paste your text
Enter any text, phrase, camelCase, snake_case, or other format into the input.
Converts to COBOL-CASE
All letters uppercased, words joined with hyphens - like THIS-IS-COBOL-CASE.
Copy the result
Click Copy and paste into your COBOL program, legacy system, or EDI format.
COBOL-CASE: uppercase with hyphens
COBOL-CASE is a naming convention in which every letter of an identifier is uppercase and words are joined by hyphens, producing names likeCUSTOMER-ACCOUNT-BALANCE. It takes its name from COBOL (Common Business-Oriented Language), designed by a committee including Grace Hopper and standardized in 1959, which required this shape for every data name and paragraph label in a program.
Two historical constraints produced the convention. Early punched-card equipment and the EBCDIC character sets used on IBM mainframes made uppercase the practical default, and the COBOL grammar reserved the underscore for other purposes while explicitly permitting the hyphen inside user-defined words. The result is a format that reads unusually in most modern languages - a hyphen normally parses as subtraction - but is completely unambiguous inside COBOL's fixed-format source.
Where you will encounter it:
- COBOL
WORKING-STORAGEdata items:WS-CUSTOMER-NAME,WS-TOTAL-AMOUNT - Paragraph and section names in the PROCEDURE DIVISION:
READ-INPUT-FILE,CALCULATE-INTEREST - ANSI X12 and EDIFACT EDI element labels such as
SENDER-IDandRECEIVER-ID - JCL job and step naming conventions on z/OS:
PAYROLL-JOB,STEP-EXTRACT - HTTP header names, which follow the closely related
Content-Typehyphenated pattern
Why does anyone still write COBOL-CASE?
Because COBOL never left. Reuters and IBM figures repeatedly cited across the industry put roughly 220 billion lines of COBOL in active production, concentrated in core banking ledgers, insurance policy administration, airline reservation systems, and government benefits platforms. Developers modernizing those systems constantly translate between modern identifiers and the mainframe copybook names they map to - turning customerAccountBalance from a Java DTO intoCUSTOMER-ACCOUNT-BALANCE for the COBOL side of the interface.
The converter is deliberately format-agnostic on input. It splits on spaces, underscores, dots, existing hyphens, and camelCase or PascalCase boundaries, then uppercases each token and rejoins with hyphens - so orderLineItem,order_line_item, and Order Line Item all yieldORDER-LINE-ITEM. Watch one gotcha: COBOL identifiers may not begin or end with a hyphen and are limited to 30 characters in most compilers, so trim long phrases before pasting them into a copybook.
Nothing you paste is uploaded. The transformation is a few lines of JavaScript running inside your own tab, which matters when the identifier names come from a proprietary internal schema.