Dot Case Converter — Text to dot.case Online
Convert text to dot.case — words joined with periods, as used for config keys and object paths. Free, instant, client-side dot case converter.
🔒 100% Client-Side Processing
Your data is processed entirely in your browser and never transmitted to any server.
Input
Spring Datasource URL Output
spring.datasource.url Acronyms are lowercased as ordinary words and accents fold to ASCII, so "Café Menu" becomes cafe.menu.
Common Use Cases
Writing config keys
Convert a setting name into the dotted form used by Spring properties, log4j levels and i18n translation files, where the periods carry the grouping rather than decoration.
Building object paths
Turn a field description into the dot-notation path that lodash get(), JSONPath and most query languages expect when reaching down into a deeply nested structure.
Naming packages and namespaces
Compose the reverse-domain package names that Java, Kotlin and Scala use, where each period maps to a real directory level rather than a cosmetic word separator.
Composing metric and event names
Build the dotted metric namespaces that StatsD, Graphite and many event pipelines expect, so a dashboard can group and roll measurements up by prefix automatically.
Frequently Asked Questions
- Where is dot.case used?
- Configuration keys such as log.level and spring.datasource.url, package and namespace paths in Java and Kotlin, object property chains, metric names in StatsD and Graphite, and i18n translation keys. The common thread is hierarchy: anywhere a name needs to express nesting, the period is the separator that does it.
- How is the text converted?
- Non-alphanumeric characters are collapsed into word boundaries, existing camelCase boundaries are split, every word is lowercased, and periods join the result — so "User Profile Data" and getUserProfile become user.profile.data and get.user.profile. Accented characters fold to ASCII first, so "Café Menu" comes back as cafe.menu.
- Why does dot.case mean something the other conventions do not?
- In camelCase and snake_case the separator is purely cosmetic — it marks where words break and nothing more. The period is a real operator in most languages, so a dotted name is also a path. Tools split on it to build a tree, which is why config systems and metric backends can group by prefix for free.
- Can I use dot.case for a variable name?
- No. The period is property access, so user.profile is read as a lookup of profile on user rather than as one identifier, and it will not compile as a variable name. Use dot.case for keys, paths and namespaces — strings that something else parses — and a valid identifier convention for names that live in code.
- How is dot.case different from path-case?
- Only in the separator: dot.case joins with periods and path-case joins with forward slashes. They split the input identically. Periods are the convention for namespaces, properties and config keys; slashes are the convention for file paths, URL segments and anything a filesystem or router will read.
- Is my data private when I use this tool?
- Yes. This tool runs entirely in your browser using client-side JavaScript — nothing you type is transmitted to, logged by, or stored on any server. You can safely process confidential text, tokens, or code.