Mycelgrid Guide
camelCase vs snake_case vs kebab-case: What’s the Difference?
Compare three common naming conventions and understand the lossy normalization that can happen when text is rebuilt as an identifier.
Direct answer
camelCase uses capitals to show later word boundaries, snake_case uses underscores, and kebab-case uses hyphens. Choose the convention required by the destination.
The three formats
| Format | Example | Boundary marker |
|---|---|---|
| camelCase | projectStatusReport | Later initial capitals |
| snake_case | project_status_report | Underscores |
| kebab-case | project-status-report | Hyphens |
What conversion changes
Mycelgrid tokenizes the source into Unicode letter/number words, lowercases those tokens, and rebuilds them. Original punctuation, separators, spacing, separator counts, and special casing can be discarded.
Why it is not reversible
Different sources such as project-status, project_status, and project status can normalize to the same token sequence. The exact source cannot generally be recovered from the result.
How to choose
Follow the destination’s specification or established project convention. Review acronyms, product names, filenames, configuration keys, and case-sensitive identifiers before replacement.
Next step
Once you know the format you need, use the Mycelgrid Text Case Converter to make the mechanical change, then review the result before replacing important text or identifiers.