Free podcast name generator for a stronger first draft.

Corbett and Hale are a two-person accountancy practice in Leeds whose clients are mostly independent cafes and restaurants. The inputs: subject, the money side of running a small food business; format, a thirty minute interview with one owner per episode; listener, people running one or two sites who learned the finance on the job.

What came out and got used was Service Charge, with the subtitle 'the money side of running a restaurant' and a first description line reading 'Every fortnight, one independent cafe or restaurant owner on what the numbers actually looked like.' Episode titles follow the pattern 'Service Charge 14: turning a 40-seat cafe into a bakery'. The cover art carries the two words at a size still legible at the width of a thumb.

It holds up in the three places a show name gets used. Fourteen characters fits an app tile without truncating on a phone. Both words are ordinary, so a listener half remembering the show types something close enough to find it, which is the failure mode killing invented spellings and visual puns. And it is sayable: 'there's a podcast called Service Charge' is a complete recommendation with no spelling required afterwards. The name signals the industry without committing to a format, so the show can add a solo episode or a panel without the title fighting it.

The cost is honest and worth naming. Service Charge is a common phrase, so the show will not own the results for it, and the topic terms an owner would actually type, restaurant, cafe, hospitality, margins, live in the subtitle and description rather than the title. That is a deliberate trade: a name people can repeat, with the discoverable words placed in the fields built to hold them.

The first draft was The Corbett and Hale Restaurant Finance Podcast. It loses on every one of those tests. It truncates to about 'The Corbett and Hale Res' in a mobile listing, which shows a browsing listener the name of a firm they have never heard of and nothing about the show. The word Podcast is dead weight inside a podcast directory. Nobody types the practice's name, because nobody outside the client list knows it. And it is unsayable as a recommendation: by the time you have got the whole thing out, the person you are talking to has stopped listening. The second draft, Bean Counters, failed differently. It is a coffee pun in a category full of coffee shows, and it would have pulled in listeners looking for something about roasting rather than about cash flow.

Do not name the show before you have recorded three episodes. Format drifts hard in the first month: the interview show becomes a two-hander, the ten minute explainer becomes forty minutes, the guest list turns out to be a different industry from the one you planned. A name fixed to the original plan then either constrains the show or has to change, and changing it means new artwork, a new feed title propagating through the apps at their own pace, and a back catalogue where the old name is spoken in every intro.

If the name you want already belongs to an active show, choose another one. Near-duplicate podcast names are extremely common and the damage is permanent: directory search is largely literal, so two shows with similar names split every search for either of them, and the one with more episodes and older reviews usually wins by default. This is a check to run before recording rather than before launching, because the intro you record fifty times is expensive to redo.

A name is also the wrong thing to work on if the show does not have a stated listener yet. Naming is choosing what to promise, and you cannot promise anything to an audience you have not described. If the honest answer to who this is for is anyone interested in the topic, spend the time narrowing that instead. The name that follows will be obvious, and it will do the filtering work in the directory that a generic name leaves undone.

Finally, if the show exists mostly to serve an audience who already know you, a members' feed or an internal series, the naming exercise matters much less than the description. Those listeners arrive by link, not by browse. Use a plain descriptive title, put the effort into episode titles, which are what get shared, and stop there.

A podcast title is read in three contexts and each one rejects a different kind of name. In a directory tile the title sits under the artwork at a width truncating aggressively on a phone, so roughly four words or thirty characters is the practical ceiling and anything longer is being cut somewhere you cannot see. In a search box the listener is typing from memory, often days after hearing the name once in a car, which is why literal spellings beat clever ones and why a name relying on a visual joke fails at the exact moment it is needed. In speech it has to survive being said by somebody who is not you, in a sentence, without a follow-up explaining how it is spelled.

Test all three before committing. Write the title at tile width and see where it cuts. Type a plausible misremembering of it into an app and see whether your show could still surface. Say it in a recommendation to somebody who has not heard of the show and watch whether they ask you to repeat it. Names failing the third test are the ones quietly capping word-of-mouth growth.

Most naming pain comes from asking the title to carry information belonging in another field. The apps give you a title, a short subtitle or author line, and a longer description, and they are read in that order by someone deciding in a couple of seconds whether to tap.

The title's job is to be memorable and repeatable. The subtitle's job is to say what the show is about and who it is for, in a phrase, and it is also where the words a listener would search belong if the title itself is abstract. The description's job is to set the format and the promise: how long, how often, what a typical episode contains, and why this host is the one making it. Split that way, an evocative title stops being a discovery liability, because the searchable terms sit in fields the directories index. Combine them and you get the familiar overstuffed title describing the topic, the format and the audience, truncating before it finishes and impossible to say aloud. Write the subtitle before the title, since knowing exactly what you would say in that line usually makes the title obvious.

The difference is the discovery channel. A newsletter arrives in an inbox where the sender name does most of the identifying, so its name is optimised for recognition and word of mouth and barely needs to be searchable. A blog is found by people searching a topic, so the publication name is close to irrelevant to whether anyone arrives. A podcast lives in a directory with a search box, and that box does the sorting.

So a podcast name carries a discovery load the other two do not. It also carries loads they never face: it has to be spoken by guests, sit inside artwork legible at thumbnail size, and read cleanly in the episode title pattern used for the whole run, since 'Show Name 42: subject' is what appears when an episode is shared. And it is harder to change. A newsletter rename is a sentence at the top of one issue. A podcast rename means new artwork, an updated feed title moving through the apps at their own speed, listeners whose saved subscription still shows the old name, and a back catalogue announcing something no longer true.

Search the exact name in the two or three largest directories and look at near matches as well as exact ones, because a show one word away from yours is still splitting the search. Check whether the phrase has an established meaning that will drown you, particularly if it is a common expression. Check the domain and the handle you would use for clips. If the show is tied to a trading name, check for registered marks in the classes covering entertainment and education before it appears on artwork.

Then consider what the name commits you to. A name containing a number, a year, a format word like interview, or a place name is a promise you will have to keep or break in public. A name built on the host works once the host is known and gives a browsing listener nothing before that. Ask what the show looks like at episode sixty and whether the name still fits. Only then record the intro, because the name is spoken in every episode and re-recording an intro across a back catalogue is the sort of job nobody ever finishes.