How does the tool split compound words like 'innerHTML' or 'XMLParser'?

camelCase splitting uses two regex passes: first it inserts a space before any lowercase-to-uppercase transition (innerHTML → inner Html), then before any sequence of uppercase letters followed by an uppercase-then-lowercase transition (XMLParser → XML Parser). Both passes together correctly split 'XMLParser' into ['xml', 'parser'] and 'innerHTML' into ['inner', 'html'].

Does the tool preserve acronyms like 'URL' or 'HTTP'?

Acronyms are lowercased as part of tokenisation and then recased according to the target convention. In camelCase, 'parseURL' becomes 'parseUrl'; in PascalCase it becomes 'ParseUrl'. If your codebase uses a style guide that keeps acronyms uppercase (e.g. 'parseURL'), apply the conversion and then manually restore the acronym casing.

What is the difference between encodeURI and encodeURIComponent?

encodeURI is designed for complete URLs — it leaves the structural characters (: / ? # & = + @) untouched so the URL remains valid. encodeURIComponent is designed for individual values within a URL — it encodes those structural characters too, preventing them from being misinterpreted as URL delimiters. Use encodeURIComponent for query parameter values; use encodeURI only if you have a full URL that you want to sanitise without breaking its structure.

Why does a space sometimes appear as + instead of %20?

HTML forms using application/x-www-form-urlencoded encoding replace spaces with + rather than %20. Both are valid in query strings, but they are different encodings. Modern APIs and URLs use %20 (RFC 3986). If you are constructing a query string for a form submission, check whether the receiving server expects + or %20.

Tool comparison

Text Case Converter vs URL Encoder / Decoder

Text Case Converter (text) and URL Encoder / Decoder (encoding) come from different categories but appear together in developer workflows. This guide explains what each does and when to reach for one over the other.

Bottom line

Text Case Converter can produce clean kebab-case slugs (e.g. `my-page-title`); URL Encoder then makes that slug safe for query strings containing special characters. The tools often chain: case-convert first, then URL-encode if the result contains non-ASCII characters.

What each tool does

Text Case Converter

Naming conventions define how words are combined into identifiers in code, configuration files, APIs, and databases. camelCase (myVariable) is the standard in JavaScript and Java. snake_case (my_variable) is the norm in Python, Ruby, and SQL. kebab-case (my-variable) is used in CSS, HTML attributes, and URL slugs. PascalCase (MyVariable) is used for class names and React components across most languages. SCREAMING_SNAKE_CASE (MY_VARIABLE) marks constants. Different tools, frameworks, and languages enforce different conventions, so converting between them is a constant need when writing glue code, generating API clients, or adapting data from one system to another. This tool splits any identifier or phrase into its component words — intelligently handling camelCase boundaries, underscores, hyphens, and dots — then reassembles them in the target convention.

Open Text Case Converter →

URL Encoder / Decoder

Percent-encoding (also called URL encoding) is a mechanism defined in RFC 3986 for representing characters that are not allowed or have special meaning in a URL. Every character that needs encoding is replaced by a percent sign followed by two hex digits representing the character's UTF-8 byte value — for example, a space becomes %20 and an ampersand becomes %26. There are two encoding variants: component encoding (encodeURIComponent) converts every character except the unreserved set A–Z a–z 0–9 and - _ . ! ~ * ' ( ); full URL encoding (encodeURI) additionally preserves the structural characters : / ? # [ ] @ ! $ & ' ( ) * + , ; = so that a complete URL remains navigable. Decoding reverses the process, converting all %XX sequences back to the original characters. URL encoding is required whenever you embed user-supplied text in a query string, form a redirect URL, construct a OAuth callback, or pass data through a system that only allows safe ASCII characters.

Open URL Encoder / Decoder →

Side-by-side comparison

Feature	Text Case Converter	URL Encoder / Decoder
Category	text	encoding
Primary purpose	Convert text between camelCase, snake_case, kebab-case, PascalCase, and 7 other naming conventions.	Encode or decode URLs and query string components using percent-encoding (RFC 3986).
Inputs	input, to	input, mode
Outputs	output, tokens, from_detected	output, mode, changed, encoding_table

When to use each

Use Text Case Converter when…

How to convert camelCase to snake_case

Convert JavaScript variable names to Python or SQL naming conventions.

How to convert snake_case to camelCase

Convert Python or database identifiers to JavaScript naming conventions.

Use URL Encoder / Decoder when…

How to encode a URL query parameter value

Safely embed user input or special characters in a URL query string.

How to decode a percent-encoded URL

Convert %XX sequences back to human-readable text for debugging or display.

Frequently asked questions

How does the tool split compound words like 'innerHTML' or 'XMLParser'?: camelCase splitting uses two regex passes: first it inserts a space before any lowercase-to-uppercase transition (innerHTML → inner Html), then before any sequence of uppercase letters followed by an uppercase-then-lowercase transition (XMLParser → XML Parser). Both passes together correctly split 'XMLParser' into ['xml', 'parser'] and 'innerHTML' into ['inner', 'html'].
Does the tool preserve acronyms like 'URL' or 'HTTP'?: Acronyms are lowercased as part of tokenisation and then recased according to the target convention. In camelCase, 'parseURL' becomes 'parseUrl'; in PascalCase it becomes 'ParseUrl'. If your codebase uses a style guide that keeps acronyms uppercase (e.g. 'parseURL'), apply the conversion and then manually restore the acronym casing.
What is the difference between encodeURI and encodeURIComponent?: encodeURI is designed for complete URLs — it leaves the structural characters (: / ? # & = + @) untouched so the URL remains valid. encodeURIComponent is designed for individual values within a URL — it encodes those structural characters too, preventing them from being misinterpreted as URL delimiters. Use encodeURIComponent for query parameter values; use encodeURI only if you have a full URL that you want to sanitise without breaking its structure.
Why does a space sometimes appear as + instead of %20?: HTML forms using application/x-www-form-urlencoded encoding replace spaces with + rather than %20. Both are valid in query strings, but they are different encodings. Modern APIs and URLs use %20 (RFC 3986). If you are constructing a query string for a form submission, check whether the receiving server expects + or %20.