snake_case is a naming convention where words are separated by underscores (_) and all letters are lowercase. There are no spaces, no capital letters, and no other separators. Each word is clearly delimited by an underscore, making multiword identifiers easy to read at a glance.

The name 'snake_case' is a visual metaphor: the underscores between words create a flat, connected line — like a snake lying across the ground. This is in contrast to camelCase, where the capital letters create 'humps.'

• ▸user_name
• ▸first_name
• ▸get_user_by_id
• ▸database_connection_string
• ▸is_authenticated
• ▸max_retry_count

snake_case has a closely related variant called CONSTANT_CASE (also called UPPER_SNAKE_CASE or SCREAMING_SNAKE_CASE). In CONSTANT_CASE, the same underscore separator is used — but all letters are uppercase instead of lowercase.

CONSTANT_CASE is the near-universal convention for named constants: MAX_RETRIES, DATABASE_URL, NODE_ENV, API_KEY. This visual distinction — all caps for constants, all lowercase for variables — helps developers immediately recognize whether a given identifier is a fixed value or a dynamic variable.

Python: PEP 8, the official Python style guide, mandates snake_case for variable names, function names, module names, method names, and file names. Python code that uses camelCase for variables or function names is considered non-idiomatic and will fail most linters and code review standards.

SQL databases: Column names and table names in relational databases conventionally use snake_case, especially in PostgreSQL. Fields like first_name, created_at, order_total, and is_active are standard. Many ORMs automatically translate between snake_case database columns and camelCase application objects.

Ruby: The Ruby programming language and Ruby on Rails both follow snake_case for variable names, method names, symbol names, and file names.

Rust: Rust adopts snake_case for variable names, function names, module names, and file names — and the Rust compiler emits warnings if you use camelCase where snake_case is expected.

Environment variables: The convention for environment variable names — DATABASE_URL, SECRET_KEY, NODE_ENV, DEBUG — is CONSTANT_CASE, which is the uppercase variant of snake_case.

All three formats represent the same information with different delimiters. Choosing the right one is entirely context-dependent:

• ▸user_profile_picture — snake_case: Python variable, SQL column, Ruby method
• ▸userProfilePicture — camelCase: JavaScript variable, Java method, JSON key
• ▸user-profile-picture — kebab-case: URL slug, CSS class name, npm package name

The critical technical reason these formats are not interchangeable: hyphens (-) are subtraction operators in most programming languages, so kebab-case variable names cause syntax errors. Underscores are valid identifier characters everywhere, which is why snake_case works safely as a variable name format. Neither can be used in standard CSS property names, which require kebab-case.

The most common real-world use cases for a snake_case converter are database migration, cross-language data translation, and manual text formatting.

When pulling data from a JavaScript API (which returns camelCase keys) and storing it in a Python or PostgreSQL backend (which expects snake_case columns), you need to translate field names: firstName becomes first_name, isActive becomes is_active, createdAt becomes created_at. A case converter handles this instantly for many field names at once.

Similarly, when converting prose descriptions into variable or function names, it's faster to type the description naturally and then convert — 'number of retries allowed' becomes number_of_retries_allowed in one click.