Remove Underscores

Programmers use underscores to separate words in variable names, file names, and database fields. While this makes sense in code (where spaces aren't allowed), it looks awkward when you need to display that text to actual humans.

Example: The database field user_profile_picture should display as "user profile picture" on your website. This tool makes that conversion instant.

Common Use Cases

• Converting file names to readable titles
• Cleaning up exported data from databases
• Making error messages user-friendly
• Formatting API response fields for display

Knowing which convention you're looking at

Underscores carry different meanings depending on where the text came from, and the naming style is usually a reliable clue about its origin. Lowercase words joined by underscores, as in order_total, is snake_case, the standard for variables and functions in Python under PEP 8 and the common choice for SQL column names. The same pattern in capitals, as in MAX_RETRY_COUNT, signals a constant in most languages and is the near-universal convention for environment variables. If you're seeing hyphens instead, that's kebab-case, which is what CSS properties and URL slugs use.

Leading and trailing underscores mean something

Not every underscore is a word separator, and stripping them blindly can change the meaning of an identifier. In Python a single leading underscore, as in _cache, marks a name as internal by convention. Two leading underscores trigger actual name mangling inside a class, so __balance becomes something closer to _Account__balance at runtime. A trailing underscore is the usual escape hatch when a sensible name collides with a reserved word. That explains why you see class_ and type_ in library code. Names wrapped in double underscores on both sides, like __init__, are reserved for the language itself.

Where automatic conversion needs a human pass

Replacing underscores with spaces is mechanically simple, but two cases still need checking afterwards. Acronyms lose their capitalization, so api_url becomes "api url" when the label you actually want is "API URL". Identifier suffixes have the same problem, with customer_id reading better as "Customer ID" than "customer id". If you're generating column headings or form labels in bulk, convert first and then fix acronyms in a second pass rather than trying to catch both at once.

Need to clean up other formatting? Use our Remove Text Formatting tool to strip all special Unicode and styling.