ToolsHub
Name Generators

Project Name Generator

Need a name for a new project, repository or release? Choose a theme for neutral code names such as “Project Kestrel”, or enter keywords for descriptive names such as “Invoice Bridge”. Every idea is shown in the format you choose together with its repository-style slug.

  • Private by default
  • No sign-up
  • Free to use

Needed for descriptive names.

The second line shows the name as a repository or package slug. Whether it is free on GitHub, npm or PyPI is not checked.

Project name ideas

    How to use Project Name Generator

    1. Choose code names, descriptive names or both.
    2. Pick a theme for code names, and enter keywords for descriptive ones.
    3. Choose the format: title, plain, kebab-case, snake_case or upper case.
    4. Shortlist names and check the one you choose where it will be published.

    Project Name Generator features

    Eight themes

    Birds, mountains, stars, rivers, minerals, trees, weather and colours: 24 names each, enough for a series.

    Descriptive names

    Built from your keywords with words such as Kit, Core, Engine and Bridge.

    Five formats

    Title case, the bare word, kebab-case, snake_case or upper case.

    Repository slug

    Each idea shows a lower-case, hyphenated slug.

    Consistent series

    Staying with one theme gives related names for successive projects or releases.

    Optional AI writer

    More suggestions when the site has AI enabled.

    When to use Project Name Generator

    • Naming an internal project before it has a public name.
    • Naming a repository, package or service.
    • Choosing release or sprint names in a series.
    • Giving a confidential initiative a neutral label.

    Project Name Generator FAQ

    What is a code name for?

    It lets a team talk about a project before a final name exists, and without revealing what it is. A neutral word gives nothing away if it appears in a calendar invite or is overheard.

    Why use a theme?

    A theme produces names that clearly belong together, which helps when there are several projects or a sequence of releases. It also avoids arguments: the next name comes from the list.

    Should a code name describe the project?

    No. A descriptive code name leaks the purpose and becomes misleading when the scope changes. Use descriptive names for repositories and packages, where clarity helps.

    What format should a repository name have?

    Lower-case words joined by hyphens are the convention on GitHub and npm. Python packages commonly use underscores for the import name. The slug shown with each idea follows the hyphenated form.

    Does the tool check whether a package name is free?

    No. Search the registry you will publish to, such as npm, PyPI or crates.io, and GitHub. Popular single words are usually taken; a prefix or a second word solves that.

    Can a code name become the product name?

    It happens, but a public name needs trademark and domain checks that a code name never had. Treat it as a new naming decision.

    Startup Name Generator Startups need names that are short, easy to type and free as a domain. Enter a few… App Name Generator An app name has to work in a store listing and under a tiny icon. Enter what your… Team Name Generator Give the generator a few words about your team, such as your department, your town… Username Generator Get username ideas built from your own name and interests, or from random word… Case Converter Fix text typed with Caps Lock on, capitalise a headline properly, or turn a phrase… GitHub README Generator Fill in a few fields about your project and get a well-structured README.md, ready…

    Two kinds of project name

    Projects need names at two moments, and the requirements are opposite. At the start, a team needs a label to use in meetings, tickets and channels, often before anyone outside should know what is being built. Later, the code needs a name that tells other developers what it does.

    Code names serve the first need. The best are deliberately meaningless: a bird, a river, a mineral. Because they say nothing about the content, they stay valid when the scope changes and reveal nothing if they leak. Choosing them from a theme has practical advantages: the names are easy to tell apart, clearly belong to one series, and the supply does not run out. Many organisations name successive releases alphabetically within a theme for that reason.

    A few cautions apply. Avoid words with unfortunate meanings in the languages your colleagues speak, names of real companies or products, and anything that could be read as a comment on the project. Short, easily pronounced words work best, since the name will be said many times a day.

    Repository and package names serve the second need and should be plain. Lower-case, hyphenated, and descriptive of what the code does is the convention, because people find packages by searching for what they need. Check the registry before you publish: single common words are almost always taken, and a scope, prefix or second word usually resolves the clash.

    Other useful tools