Guide

THE TOOLBOX / TEXT & IDENTIFIER UTILITIES

Convert case &
inspect UTF-8 bytes.

Transform identifiers across 11 naming conventions in bulk, while measuring exact UTF-8 byte length, UTF-16 code units, and Unicode graphemes.

Showing 11 naming conventions (79 UTF-8 bytes · 79 graphemes).

Samples

79 / 100,000 UTF-16 code units · 79 UTF-8 bytes

UTF-8 Bytes
79
Graphemes
79
UTF-16 (.length)
79
Words
7
Lines
4
11 Converted Naming Conventions
camelCase
parseXmlHttpRequest
userProfileAvatarUrl
maxRetryTimeoutMs
apiV2AuthToken
PascalCase
ParseXmlHttpRequest
UserProfileAvatarUrl
MaxRetryTimeoutMs
ApiV2AuthToken
snake_case
parse_xml_http_request
user_profile_avatar_url
max_retry_timeout_ms
api_v2_auth_token
CONSTANT_CASE
PARSE_XML_HTTP_REQUEST
USER_PROFILE_AVATAR_URL
MAX_RETRY_TIMEOUT_MS
API_V2_AUTH_TOKEN
kebab-case
parse-xml-http-request
user-profile-avatar-url
max-retry-timeout-ms
api-v2-auth-token
Train-Case
Parse-Xml-Http-Request
User-Profile-Avatar-Url
Max-Retry-Timeout-Ms
Api-V2-Auth-Token
dot.case
parse.xml.http.request
user.profile.avatar.url
max.retry.timeout.ms
api.v2.auth.token
path/case
parse/xml/http/request
user/profile/avatar/url
max/retry/timeout/ms
api/v2/auth/token
Title Case
Parse Xml Http Request
User Profile Avatar Url
Max Retry Timeout Ms
Api V2 Auth Token
lowercase
parsexmlhttprequest
userprofileavatarurl
max_retry_timeout_ms
api-v2/auth-token
UPPERCASE
PARSEXMLHTTPREQUEST
USERPROFILEAVATARURL
MAX_RETRY_TIMEOUT_MS
API-V2/AUTH-TOKEN

THE DETAILS

RFC 3629 UTF-8 byte length, UAX #29 graphemes, and identifier refactoring.

1. Step-by-Step Workflow

Paste variable names, SQL columns, or text into the left editor—or click TS Identifiers, SQL Columns, or UTF-8 Emoji. Copy any of the 11 converted naming convention cards on the right, or click Inspect UTF-8 Codepoints to view the hex byte breakdown of the first 50 graphemes.

2. RFC 3629 UTF-8 vs. UTF-16 vs. UAX #29 Graphemes

Using new TextEncoder().encode(text).length (IETF RFC 3629) and new Intl.Segmenter('en', { granularity: 'grapheme' }) (Unicode Standard Annex #29), the telemetry grid separates storage bytes from UTF-16 code units (string.length) and visible characters.

3. Acronym-Aware Identifier Tokenizer

Moving identifiers between TypeScript (camelCase), Rust/Python/SQL (snake_case), CSS/URLs (kebab-case), and environment variables (CONSTANT_CASE) preserves acronym boundaries such as XML, URL, ID, and API.

Naming Convention & Unicode Encoding Matrix

Convention / CharacterExample OutputEcosystem / Byte Size
camelCase / PascalCaseuserProfileId / UserProfileIdTypeScript, JavaScript, React, Go, Java
snake_case / CONSTANT_CASEuser_profile_id / USER_PROFILE_IDPostgreSQL, Python, Rust, .env vars
kebab-case / path/caseuser-profile-id / user/profile/idCSS classes, URL slugs, file routes
Rocket Emoji (🚀 U+1F680)Hex: F0 9F 9A 801 grapheme · 2 UTF-16 units · 4 UTF-8 bytes

Common String & Encoding Pitfalls

Truncating Strings with .slice(0, N)

Calling str.slice(0, N) cuts by UTF-16 code units and can slice a 2-unit surrogate pair in half, producing an invalid lone surrogate (U+D800–U+DFFF) that breaks JSON serializers.

Zero-Width Joiner (ZWJ) Emoji Sequences

Compound emojis joined by U+200D (Zero-Width Joiner) consist of multiple Unicode code points that Array.from(str) splits apart, whereas Intl.Segmenter keeps them together as a single grapheme.

ASCII vs. Multi-Byte UTF-8 Ranges

ASCII characters (U+0000–U+007F) take 1 byte in UTF-8; Latin/Greek/Cyrillic/Arabic take 2 bytes; CJK and basic symbols take 3 bytes; and astral plane emojis take 4 bytes.

Case-Insensitive Database Collations

Standardizing database column names to lowercase snake_case avoids quoting issues in PostgreSQL (which folds unquoted identifiers to lowercase) and cross-OS filesystem conflicts.

Frequently Asked Questions

Why does JavaScript string.length differ from UTF-8 byte size and grapheme count?

JavaScript strings use UTF-16 code units, so characters outside the Basic Multilingual Plane (such as 🚀) report .length === 2 while occupying 4 UTF-8 bytes and 1 user-perceived grapheme cluster. Multi-codepoint sequences like family or flag emojis can occupy 12–28 UTF-8 bytes while still rendering as 1 grapheme.

How does the tokenizer split acronyms like parseXMLHttpRequest?

Instead of splitting every uppercase letter into single characters (p_a_r_s_e_x_m_l...), the boundary detector recognizes transitions between uppercase acronyms and TitleCase words, splitting parseXMLHttpRequest cleanly into parse, xml, http, and request.

Can I convert a list of database columns or variables line by line?

Yes. Keep Convert line-by-line (preserve line breaks) checked and paste as many lines of identifiers as you need. Every naming convention card converts all lines in parallel while keeping line breaks intact.

Why do UTF-8 byte counts matter for SQL databases and APIs?

Database columns (such as MySQL VARCHAR(255) or PostgreSQL index keys), HTTP headers, Kafka messages, and S3 object keys enforce limits in UTF-8 bytes rather than visible characters. The live UTF-8 byte counter and codepoint inspector let you spot multi-byte characters immediately.

Is my text processed 100% locally in the browser?

Yes. All case conversions, TextEncoder byte measurements, and Intl.Segmenter grapheme analyses run natively in your browser with zero network calls.