Set up your own Google Cloud API key
Google's best voices, on your own account, at Google's prices. Expect about 15 minutes of clicking around in a console you may never have opened before.
Google Cloud Text-to-Speech has the best voices Speakybara can use, including Chirp 3 HD and WaveNet. They are not built into the app: you bring your own key, the key stays on your PC, and Google bills you directly if you ever go past the free tier.
Being honest about the work: you need a Google account, a Cloud project and a billing account attached to it, even though the free tier costs nothing. If that sounds like a bad evening, Speakybara Managed does the same thing for €59 a year and nothing to set up.
What Google gives away each month
Per voice family, per month, on your own key. A page of running text is about 3,000 characters.
| Voice family | Free per month | About |
|---|---|---|
| Standard | 4,000,000 characters | 1,333 pages |
| WaveNet | 4,000,000 characters | 1,333 pages |
| Neural2 | 1,000,000 characters | 333 pages |
| Chirp 3 HD | 1,000,000 characters | 333 pages |
1,000,000 characters of Chirp 3 HD is roughly 333 pages a month. Most personal use never leaves the free tier; past it, Google charges your billing account at its own rates.
From nothing to a working key
Step 1
Create a Google Cloud project
Sign in to the Google Cloud Console with your Google account and create a project. The name is yours to pick; nothing in Speakybara refers to it.
Step 2
Enable the Cloud Text-to-Speech API
In that project, find the Cloud Text-to-Speech API and switch it on. This is the step people forget: a key without the API enabled returns an error on every sentence.
Step 3
Attach a billing account
Google asks for a billing account before it hands out Text-to-Speech quota, including the free part. You are not charged while you stay inside the free tier, but the card details do have to be there.
This is the part Speakybara Managed removes. Same voices, one key you paste, no Google account of your own.
Step 4
Create an API key and restrict it
Create a key under Credentials and copy it. Then restrict it to the Cloud Text-to-Speech API, so a leaked key cannot be used for anything else in your project. Restricting is a minute of work and worth doing now rather than later.
Step 5
Paste it into Speakybara and test
Open Speakybara, go to Models, switch on Your own models and keys and choose Google Cloud as the voice service. Paste the key in the API key field and press Test. The line under the field says whether the key works. The key is stored in your own settings file on your PC and is only ever sent to Google.
Google Cloud selected, the key masked in the field, and the Test button next to it. Screens come from the app itself.
Step 6
Watch the usage meter
The Models page has a Usage this month section with a bar per voice family: characters used, the percentage of the free allowance, and how many pages you have left. It counts as you read.
Speakybara keeps its own counter because Google's console shows requests rather than characters, and the billing overview stays at zero while you are inside the free tier. Six months of history are kept on your PC.
Usage this month, per voice family, counted on your PC.
Worth knowing
- Sentences you have already heard are cached on your PC, so re-reading the same text starts instantly and costs no characters.
- Each voice family has its own free allowance, which is why the usage meter counts them separately.
- The key sits in your settings file in the Speakybara folder. Copying it to a second PC works; treat it like a password.
- If Google is unreachable mid-text, Speakybara carries on with the local voice and tells you once.
If something goes wrong
It goes to Google, and nowhere else. The key is stored in Speakybara's settings file on your own computer and is sent with each request to Google's Text-to-Speech service. Speakybara has no server in that path.
Google charges your billing account at its published rates for anything above the free characters. Speakybara cannot stop that for you, which is why the usage meter shows how far into the month's allowance you are.
Almost always one of three things: the Cloud Text-to-Speech API is not enabled in that project, no billing account is attached, or the key restriction is set to a different API. Check them in that order.
Rather not do any of that?
Speakybara Managed gives you the same Google voices without a Google account, a project, a key or a billing setup: €59 a year, and a licence key you paste into settings.
See pricing