Based on Chuck Litka’s post Adventures in Audiobooks, I decided to go with Google’s audiobook option only. So this post refers exclusively to auto-narrated audiobooks on the Google Play platform.
I have finished setting up and editing one audiobook, which is now live. From that experience, I can make the following observations.
Once you have an ebook live on Google Play Books, it’s surprisingly easy to create an audiobook. That said, I fumbled my way through the process, and my first book went live in an unedited state. I will have to figure out how to keep that from happening with any others I publish, because it is absolutely necessary to listen to the entire book before finalizing it. There are step-by-step instructions in something called the Auto-Narrated Audiobooks Learning Center, but when I started the process, I found myself being hustled through a number of steps without really knowing what was happening. No harm done, however, as far as I know.
On the plus side, once the audiobook was live, it was easy to whip it into shape. I called up the Audiobook Text, which allowed me to both listen to and see the text. I could start and stop playback, make changes in the text, and save them. It’s possible to have more than one version of an audiobook (with different narrator voices, for example), but only one can be live.
There is a large number and variety of narrator voices available, including male and female voices in different age ranges (18-30, 31-45, 45-60, and 60+) with “standard” American, British, or Australian accents. Voices for a few languages other than English are available, but it’s recommended to use these only for texts in those languages. There are no options for English spoken with accents other than those I’ve already mentioned, or with regional accents.
It’s possible to use more than one voice in a book! Theoretically, you could have dialogue in as many voices as you have characters, but I think this would complicate the setup process. So far, I’ve used only one main voice, with a second one to read brief quotations that open a few chapters in my book.
Changes made to the audiobook text are not reflected in the ebook version. One hazard here is I was sorely tempted to improve the text! I don’t know how many instances of the word “that” I was tempted to delete, but I decided to make no changes except those needed to improve or correct the speech. I want the audiobook, ebook, and paperback versions to be essentially the same, stylistic problems and all. However, I did find it helpful to add or delete commas on occasion.
The computer-generated voices sound human, much more so than the rather robotic voice of Word’s text-to-speech feature. Nevertheless, they can’t be expected to represent the full range of emotion that may be found in a work of fiction. Google’s info about auto-narrated audiobooks cautions that they work best for texts that do not require a lot of drama and emotion. Still, I found the voices I selected to be better than adequate. Quite often, the main narrator was spot-on, to the point he seemed to embody the first person narrator of the book.
Quirks and Issues
- Stress and emphasis does not always fall where it should in a sentence. This can’t be changed by adjusting the speed of the narration, but deleting or adding commas helps sometimes. Still, I admit there are occasions when a word or sentence sounds a little “off.”
- Sometimes there is an awkward pause between a word or sentence spoken by a character and the dialogue tag such as “he said” or “I asked.” The best solution might be to delete selected dialogue tags, but I resisted the temptation to do this, not wanting my spoken and written texts to diverge. But this is another reason to use fewer dialogue tags!
- Weirdly, a few names are pronounced quite differently when a possessive is added. For one name, I had to provide a correct pronunciation for possessives because the default was unacceptable.
- Homographs are common enough that you have listen for instances where the wrong pronunciation pops up. For example, the default pronunciation of the word “read” is the present tense (pronounced “reed”). When the past tense pronunciation (“red”) was needed, I had to intervene. Fortunately it’s easy to fix these; a right click on the word in the text takes you to both versions, and you can listen to them before selecting the correct one. There is an option to change the pronunciation of all instances of a word, or only one.
- Abbreviations such as Mr. and Dr. are usually pronounced correctly, but I encountered a few situations where “Dr.” came out as “drive,” for some reason. I fixed these by spelling out the word.
- Uncommon words, place names, or words in other languages may be mispronounced. In such cases, you can insert a different pronunciation by spelling the word differently, speaking it into your computer’s mic, or by using the International Phonetic Alphabet. I actually did that for a few place names; fortunately Wikipedia sometimes provides IPA spellings in its articles, so I was able to reproduce them with good results. You can listen to the new pronunciation before selecting it. This was about the most challenging part of the editing process.
So what do I think of Google’s Auto-Narrated Audiobooks?
I think it’s an excellent option for authors who would not otherwise consider producing audiobook versions of their books. It doesn’t cost anything and produces acceptable results.
There’s no doubt that a competent human reader or voice actor would produce a superior listening experience, but at a cost that’s likely prohibitive for most indie authors. Some may have the talents and equipment to be their own reader, but I suspect those are a minority. The AI-narrated option is available for free to anyone.
A few more considerations:
- You have to publish your books as ebooks on Google Play before you can create audiobooks. Google requires book files in ePub, not Word. I used Calibre (a free program) to convert a copy of the Word doc I used for the Amazon Kindle version of my book into an ePub, which I then uploaded to Google Play Books. It helped that the Word doc was properly formatted and had a linked table of contents.
- You need a square cover image for the audiobook, but it looks like the rectangular ebook cover image is squared up automatically with a block of matching colour, so you can get away with that.
- You need to commit the time needed to listen to your audiobook from start to finish in order to correct any serious or even mildly annoying problems in the finished product. The book I worked with is a fairly hefty tome, which ended up being more than 15 hours of listening time. It took me a solid week to complete, spending 2 to 3 hours each day. (Actually, this reminded me why I prefer reading fiction rather than listening to it.)
I encourage anyone who wants to offer their books in audio format to give this a try. The only cost is your time.
Once I’ve converted one more book to auto-narrated audio format I will write a post on my own blog with more details. That should appear in another week or two.
Featured image from Pexels

