How to Pick a Side Project Domain Name in an Evening
Published 2026-10-03 · Updated 2026-11-05 · By Aaron Kempf
Side projects die in the naming stage more often than anyone admits. You open a registrar "just to grab a name," and three hours later you have a spreadsheet and no code. A side project domain name only has to be good enough to ship. Give yourself one evening, follow a routine, and get back to building.
Set the rules before you start
Decide three things up front, and don't revisit them tonight:
- A budget. Ordinary registration price only. No premium names, no buying from investors.
- Extensions you'll accept. For most hobby projects, .com plus one or two of .dev, .app, .io or .xyz is plenty.
- A deadline. Ninety minutes. When the timer goes, you register the best open name on your list.
These rules matter more than any tool. Without them, the search expands to fill the weekend.
The 90-minute routine
Minutes 0–15: words. Write 20 words connected to what the project does or who it's for. Don't judge them yet. If you're building a tool that tracks houseplant watering, write water, leaf, sprout, pot, fern, drip, and so on.
Minutes 15–35: generate. Paste the strongest five into Word Combinations or Subset Combine to get pairs. Then run the Pronounceable generator at 5 to 7 letters for a few invented options.
Minutes 35–60: check. Filter everything to open names on the extensions you chose. Sort by length.
Minutes 60–80: shortlist. Pick five. Say each aloud. Drop any you'd have to spell for a friend.
Minutes 80–90: register. Pick one. Done.
What makes a good side project domain name
The bar is lower than for a company, but a few things still matter:
- Short enough to type in a README or a tweet. Ten characters or fewer is comfortable.
- Not tied to a single feature, in case the project grows.
- Not close to an existing product, especially one in the same space. A quick search avoids an awkward email later.
- Yours, not your employer's. Register it with a personal account and a personal email address, especially if your contract mentions side work.
A worked example
A developer (invented for this example) is building a small web app that reminds people to water their houseplants. Their word list includes leaf, drip, fern, sprout, thirst and pot. Word Combinations gives pairs like dripfern and leafdrip; the Pronounceable generator offers a handful of short invented words. Twenty minutes of checking leaves six open names. "Dripfern" is open on .app and easy to say, so it's registered before the timer runs out. The developer spends the rest of the evening on the reminder logic instead.
You can rename later
Side projects that take off can be renamed. Plenty have been. A clean redirect from the old domain keeps early links working. That's the main reason not to agonise: the cost of a "wrong" name on a hobby project is small.
For a fuller process when a project turns into a business, see finding an available startup domain.
Common mistakes
Searching without a deadline. Naming has no natural end. Set one.
Buying a premium name for a weekend project. Spend the money on hosting instead.
Registering ten names "just in case." Each one renews every year.
Related reading
- Open Source Project Name: Pick One and Check the Domain
- How to Find an Available .ai Domain for an AI Product
Frequently asked questions
Which extension is best for a hobby project?
Whichever is open and affordable. .com is the most familiar, but .dev, .app and .xyz are common for personal projects.
Should I register the name before I build anything?
Only if you're sure you'll build it. An unused name still renews every year.