dot.case Converter
dot.case joins lowercase words with periods: app.config.path, user.profile.email, analytics.event.signup.completed. It fits translation keys, nested configuration, analytics event names, and feature-flag namespaces where hierarchy matters as much as spelling.
Enjoying this tool?
Part of Case converters
dot.case converter: namespaced keys and config paths
dot.case joins lowercase words with periods: app.config.path, user.profile.email, analytics.event.signup.completed. It fits translation keys, nested configuration, analytics event names, and feature-flag namespaces where hierarchy matters as much as spelling.
Paste a phrase, camelCase property, or snake_case column and copy the dotted token into your i18n files, YAML config, or event catalog.
How to use this converter
- Enter a label with spaces, underscores, hyphens, or camelCase boundaries.
- Confirm segment order matches your namespace design (broad → specific).
- Copy into JSON config, i18n JSON, or analytics dictionaries.
Before and after examples
Order segments from general to specific when designing namespaces.
| Original | Converted | Notes |
|---|---|---|
| app config path | app.config.path | Plain phrase |
| userProfileEmail | user.profile.email | From camelCase |
| analytics_event_signup | analytics.event.signup | From snake_case |
| Feature Flag Dark Mode | feature.flag.dark.mode | From Title Case |
When should you use dot.case?
Use dot.case when tools expect dotted keys: many i18n libraries, nested settings objects, and analytics taxonomies. URLs use kebab-case; Python uses snake_case; JavaScript properties often use camelCase—dot.case is for hierarchical labels, not public paths.
Translation and locale files
Namespaced keys like `errors.form.email.invalid` keep collisions out of flat dictionaries. When product copy arrives as Title Case labels, convert to dot.case before merging into `en.json` or `fr.json`.
Configuration and feature flags
Remote config services sometimes expose dotted paths that mirror object shape. Document whether `app.theme.dark` is a single key string or a nested JSON path in your SDK—dot.case here produces the key, not the nesting itself.
Common mistakes
Using dot.case in URL slugs—browsers and SEO expect hyphens, not periods.
Creating keys so deep that no one remembers the hierarchy—prefer shallow, meaningful segments.
Mixing `user.profileId` camelCase inside a dot.case file without a documented mapping.
Frequently asked questions
Is dot.case the same as a JSON path?
Similar visually, but JSON paths often imply nested objects. dot.case here produces a single key string—check how your config loader resolves it.
Can dots appear in the middle of a word?
The converter splits on word boundaries, not arbitrary dots in acronyms. Review `api.v2` style segments manually.
dot.case vs kebab-case for events?
Analytics vendors differ—some want `signup.completed`, others `signup-completed`. Follow your warehouse schema.
Are uppercase letters allowed?
Output is lowercase with dots. Normalize shouting input first if needed.