About this tool

Snake Case Converter

Convert any phrase into snake_case.

The Snake Case Converter rewrites a phrase as snake_case by splitting the text at every run of non-alphanumeric characters, lowercasing each piece and joining them with single underscores. It is for developers and data people who need identifiers that match a Python, Ruby, SQL or JSON naming convention — "My Variable Name Here" comes back as my_variable_name_here. Spaces, hyphens, dots, slashes and punctuation are all treated as the same separator, so messy input collapses to one clean identifier.

How to use Snake Case Converter

1. 1

   Open Snake Case Converter on AltFTool — it loads instantly in your browser.

2. 2

   Type or paste your phrase into the Input box, or click Load sample to try "My Variable Name Here".

3. 3

   The converter splits the text at every run of spaces, hyphens or punctuation, lowercases each piece and joins them with single underscores as you type — no convert button.

4. 4

   Read the snake_case identifier in the Result panel and click Copy to put it on your clipboard.

Why use Snake Case Converter

• One rule for every separator

  Hyphens, dots, slashes, punctuation and any run of spaces all collapse to a single underscore, so double separators never produce a double underscore.

• No leading or trailing underscores

  Empty pieces are dropped before joining, so input that starts or ends with punctuation still returns a valid identifier.

• Predictable digit handling

  Numbers already set off by a space or punctuation become their own segment, so "HTTP Response Code 404" becomes http_response_code_404 rather than losing the number. Digits already touching a letter stay fused instead of being split out — "item2Value" becomes item2value, not item_2_value.

Common use cases

• You are renaming spreadsheet headers such as "Order Date" and "Total (USD)" before loading them into a Postgres table that expects lowercase underscore column names.
• You are following PEP 8 in a Python module and want function and variable names generated from the plain-English description you already wrote in the ticket.
• You are normalising a list of event names for analytics so that "Sign-Up Completed" and "Sign up completed" both end up as the same key.

Frequently asked questions