AaCaseConvertly

dot.case Converter

Convert text to dot.case — lowercase words joined by dots, for keys, namespaces and events.

0 characters0 words0 lines0 sentences
dot.case
Your dot.case result will appear here…

All cases — live preview (click any result to copy it)

UPPERCASE
Start typing to see UPPERCASE…
lowercase
Start typing to see lowercase…
Title Case
Start typing to see Title Case…
Sentence case
Start typing to see Sentence case…
Capitalized Case
Start typing to see Capitalized Case…
aLtErNaTiNg CaSe
Start typing to see aLtErNaTiNg CaSe…
RaNdOm CaSe
Start typing to see RaNdOm CaSe…
iNVERSE cASE
Start typing to see iNVERSE cASE…
snake_case
Start typing to see snake_case…
camelCase
Start typing to see camelCase…
PascalCase
Start typing to see PascalCase…
kebab-case
Start typing to see kebab-case…
CONSTANT_CASE
Start typing to see CONSTANT_CASE…
Train-Case
Start typing to see Train-Case…
dot.case
Start typing to see dot.case…
slugify
Start typing to see slugify…

Private by design — every conversion runs locally in your browser. Your text is never uploaded, stored or tracked.

dot.case writes words in lowercase joined by dots: app.server.port, user.profile.updated, logging.level.default. The dots are not decoration — in most systems that use dot.case, each dot marks a level of hierarchy, so a dot.case name reads like a path from the general to the specific, left to right.

You will meet dot.case in configuration files and environment hierarchies, in Java-style package and property names, in translation keys in language files, in analytics and event names, and in message-queue topics. This converter splits your text into real words first — handling camelCase, snake_case, hyphens, acronyms and numbers — then joins them with dots, so identifiers from any convention convert cleanly.

When to use it

  • Configuration keys and property names (server.host, server.port style hierarchies)
  • Translation and localization keys in language files
  • Analytics, logging and event names that group by prefix
  • Message topic and routing-key names in queues and event systems
  • Converting identifiers from camelCase or snake_case into a namespaced form

How it works

  1. The input is split into words with the same identifier-aware splitter used across this site — separators, camel humps, acronym boundaries and numbers all mark word edges.
  2. Every word is lowercased.
  3. The words are joined with single dots — no leading, trailing or doubled dots.
  4. Existing dots in the input act as word separators, so app.ServerPort becomes app.server.port.

Examples

Input
user profile updated
Output
user.profile.updated
Input
serverPort
Output
server.port

camelCase input splits at the hump.

Input
app.server.HostName
Output
app.server.host.name

Existing hierarchy is preserved and normalized to lowercase.

Good to know

dot.case is the quietest of the developer cases because it rarely appears in source code as an identifier — dots mean member access in most languages — but it dominates the layers around code. Spring and similar frameworks read configuration as dot-separated property paths; language files nest translations under dotted keys; analytics platforms encourage dotted event names so reports can group everything under a prefix; and logging systems from log4j onward have used dotted logger names that inherit settings from their parents. In all of these, the dot is structural: user.profile.updated belongs to the user.profile family, and tools can filter, inherit or aggregate by prefix.

When converting, one decision matters: how many levels to create. A flat phrase like “user profile updated” becomes three levels here because each word becomes a segment. If your system expects two levels (an area and an action), convert the phrase and then merge segments to taste — the word boundaries this tool finds are the reliable part, and adjusting the grouping afterwards is trivial.

Frequently asked questions

Where is dot.case actually used?

Configuration and property keys, translation files, analytics event names, logging hierarchies, message topics and package-style namespaces. Anywhere a name should also be a path from general to specific.

What is the difference between dot.case and snake_case?

The separator carries different meaning. In snake_case the underscore is just a word joiner inside one flat name. In dot.case each dot usually marks a hierarchy level, so systems can group, filter or inherit by the prefix before a dot.

Can dot.case be used as a variable name in code?

In most languages, no — a dot means property access, so user.profile reads as “the profile property of user”. dot.case is for keys, names and configuration strings, not for identifiers inside code.

How are acronyms and numbers handled?

As whole words: userID becomes user.id, and version2Update becomes version.2.update — the same identifier-aware splitting used by the camelCase and snake_case converters on this site.

Is my text uploaded or stored?

No. The conversion runs entirely in your browser. Nothing you type is sent to a server, stored or logged — safe for configuration keys and schemas.

Related tools