About Us

Why we built it

Every codebase has a naming convention, and every one of them is different. Python wants snake_case. CSS and URLs want kebab-case. JavaScript wants camelCase and React components want PascalCase. Environment variables want CONSTANT_CASE. The simple act of moving a name from one world to another used to mean a slow, error-prone round of manual editing — and a single missed capital letter can break a build, a route, or a database column.

There are plenty of online case converters, but most of them do one of two things: they upload your text to a server, or they are buried in a page thick with ads and pop-ups. We wanted neither. So we built a text case converter that does the whole job in the browser, loads instantly, and stays out of your way.

How it works

The conversion itself is deliberately boring. You paste or type text into the input panel, and you click one of the twelve format buttons. The output updates on the spot — no submit button, no spinner, no page reload. Under the hood it is plain JavaScript running a small set of regular-expression transforms against the string in front of you.

Because the work happens in your browser, the same tool behaves identically whether you are on a fast laptop or a five-year-old phone, and it behaves the same whether you are online or not once the page has loaded. The input panel also tracks word count, character count, sentence count, line count, estimated reading time, and estimated speaking time as you type, which is handy when you are working to a length limit.

The twelve formats

• Upper case — for acronyms, headings, and short labels.
• Lower case — for normalising input and softening copy.
• Capital case and Title case — for display copy, headlines, and titles.
• Sentence case — for paragraphs and captions, where only the first letter of each sentence is capitalised.
• camelCase — for JavaScript variables and class names.
• snake_case — for Python, database columns, and environment variables in many codebases.
• kebab-case — for CSS classes, HTML attributes, and URL slugs.
• dot.case — for configuration keys and i18n translation files.
• CONSTANT_CASE — for environment variables and constants.
• Inverse case and alternating case — for when you want to have fun.

The format guide explains what each one is for, and the frequently asked questions cover the shortcuts and edge cases people ask about most.

Privacy first, not privacy later

The decision to do the conversion locally was made before the design was, and it has never been worth reversing. Your text is not sent anywhere. It is not written to a log, stored on a server, or queued for analysis. The only trace left behind is the conversion history in your own browser, which you can clear with a single click.

That principle is also why the privacy policy is short and specific rather than a generic template: there is very little to disclose, because very little is collected.

How it is built

The site is a static Astro project with Tailwind CSS for styling and a small amount of vanilla JavaScript for the conversion logic. There is no backend to scale, no database to maintain, and no framework runtime shipped to your browser. That keeps the page fast, keeps the attack surface small, and means the tool keeps working even if parts of the wider web are unreachable.

What we care about

• Speed. The tool should feel instant. If it is not instant, it is broken.
• Predictability. The same input always produces the same output. No clever guesses.
• Restraint. No pop-ups, no interstitials, no dark patterns, and no feature that exists only to send you somewhere else.
• Accessibility. Keyboard navigation, visible focus states, and a layout that works on any screen from a small phone to a wide desktop.

Get in touch

Found a bug, spotted a format that is missing, or just want to say hello? We read everything that comes in, and feature requests genuinely shape what gets built next. Use the contact page or email hello@casetoconvert.com.