Text Case, Sort & Slug Converter

Yes. The converter intelligently detects word boundaries from spaces, hyphens, underscores, and camelCase transitions. So input like "my-variable_name" is correctly split into words before converting to your target case format.

camelCase starts with a lowercase letter (e.g., myVariableName), while PascalCase starts with an uppercase letter (e.g., MyVariableName). camelCase is commonly used for variables and functions, while PascalCase is used for class names in most programming languages.

The tool works best with single identifiers, variable names, or short phrases. While you can input longer text, case conversions like snake_case and camelCase are designed for programming identifiers, not prose.

Yes. Numbers within your input are preserved during conversion. For example, "myVar2Name" converts to "my-var-2-name" in kebab-case, keeping the numeric characters in place.

Alphabetical sort treats all characters as text and sorts strictly by character code: "item1", "item10", "item2", "item20", "item3". Natural sort recognizes embedded numbers and sorts them numerically: "item1", "item2", "item3", "item10", "item20". Use natural sort when your lines contain version numbers, filenames with numbers, or any mixed text-and-number data.

When "Remove duplicate lines" is enabled, only the first occurrence of each line is kept and all subsequent duplicates are removed. By default, comparison is case-insensitive (so "Apple" and "apple" are considered duplicates). Enable "Case-sensitive sorting" to treat differently-cased lines as distinct.

By default, the tool splits input by newline characters (one item per line). If your data uses a different delimiter (comma, semicolon, pipe, tab), enter it in the Separator field to split and rejoin by that character instead. For example, entering "," will treat each comma-separated value as a separate item.

Prefix adds a string before each line, and suffix adds a string after each line in the output. This is useful for wrapping lines into code syntax: for example, prefix '"' and suffix '",' converts a plain list into JSON array elements. Prefix/suffix are applied after sorting and deduplication.

The original text remains in the input field, the sort only affects the output. You can always copy from the input field to get the original order. If you want to completely reverse the current line order, use the "Reverse Lines" sort method.

There is no hard line limit since all processing happens in your browser. Performance depends on your device, but modern browsers handle tens of thousands of lines without issues. For extremely large datasets (100K+ lines), processing may take a moment.

A URL slug is the human-readable part of a URL that identifies a specific page, for example, "my-blog-post" in example.com/blog/my-blog-post. Well-crafted slugs improve SEO because search engines use URL keywords as a ranking signal, and users are more likely to click on links with clear, descriptive URLs. A good slug is lowercase, uses hyphens as word separators, contains target keywords, and avoids stop words and special characters.

Yes. The tool includes a built-in Unicode transliteration engine that converts characters from 10+ languages to their closest ASCII equivalents. For example: Turkish ç→c, ğ→g, ş→s, ı→i; German ä→ae, ö→oe, ü→ue, ß→ss; French é→e, ê→e; Russian а→a, б→b, and so on. Characters without a direct mapping are processed through Unicode NFD normalization to strip diacritical marks as a fallback.

Google officially recommends hyphens (-) over underscores (_) in URLs. Google treats hyphens as word separators, meaning "my-blog-post" is read as three separate words. Underscores are treated as word joiners, so "my_blog_post" is read as one compound word. For maximum SEO benefit, always use hyphens as your URL separator.

Stop words are common, low-meaning words like "a", "an", "the", "is", "in", "on", "for", "and", "with". Removing them from slugs makes URLs shorter and more keyword-focused. For example, "The Ultimate Guide to SEO in 2024" becomes "ultimate-guide-seo-2024" instead of "the-ultimate-guide-to-seo-in-2024". Shorter URLs are easier to read, share, and remember. However, sometimes stop words add meaning, use your judgment.

Yes. Enable Bulk Mode to process multiple lines of text simultaneously, each line is converted into a separate slug. This is useful when generating slugs for a list of blog post titles, product names, or page headings. Paste your list with one title per line and get all slugs at once.

The converter splits on three signals: explicit separators (spaces, hyphens, underscores), lowercase-to-uppercase transitions (helloWorld → hello + world), and letter-to-digit boundaries. This means it can correctly re-case helloWorld2User regardless of which convention it started in.

Consecutive capitals are treated as a single word, so parseURLPath splits into parse + URL + path. When converting to camelCase or PascalCase the acronym is normalized (parseUrlPath), matching the style most linters and style guides, including Google's and Microsoft's, recommend for identifiers.

Pure character-code (ASCII/Unicode) sorting orders by the numeric value of each character, which doesn't match how a human or a dictionary expects words to sort. All uppercase letters come before all lowercase ('Z' before 'a'), and accented letters (é, ö, ñ) sit far away in the Unicode table, so they land after 'z' instead of next to their base letter. Languages also have their own rules, in Turkish, 'ı' and 'i' are distinct letters with a specific order. For human-friendly ordering, you want locale-aware (collation) sorting rather than raw code-point sorting; enabling case-insensitive comparison fixes the most jarring upper/lower issue, and for serious multilingual sorting, normalize or use a locale-aware collator.

Use the prefix, suffix, and separator options together, they're built for exactly this. To make a JSON array of strings, set the prefix to a double-quote and the suffix to a quote-plus-comma, so each line becomes "item", and wrap the result in [ ]. For a SQL IN-clause, the same pattern produces 'item', 'item', 'item' to drop inside IN (...). Combine with deduplication to remove repeats and with sorting to make the output deterministic. This turns the tool into a quick list-to-code converter, paste a column from a spreadsheet, and get a ready-to-paste array or clause in seconds.

Avoid it whenever possible, a published URL is an asset. Changing a slug breaks every existing link to that page (other sites, social shares, bookmarks, your own internal links) and discards the SEO authority the old URL accumulated, which can tank its rankings. If you absolutely must change it (a bad typo, a rebrand), set up a 301 redirect from the old slug to the new one. A 301 passes most of the link equity to the new URL and keeps existing links working. The cleanest strategy is to get the slug right before publishing and then leave it alone.

Generally no, keep slugs short, stable, and keyword-focused. Dates in URLs (/2024/03/my-post) make content look stale the moment the year turns and force a redirect if you ever update and 'refresh' the piece. Category paths (/blog/seo/my-post) break the moment you recategorize an article, again requiring redirects. Both also lengthen the URL without adding ranking value. Prefer a flat, descriptive slug (/my-post or /blog/my-post) that won't need to change when the content's date or category does. Stability is worth more than cleverness in a URL.