How to Narrate a Glossary, Appendix, or Map in a Fantasy Novel

Short answer: most back matter should not be narrated at all. A glossary earns its place if you move it to the front and read it as a pronunciation guide. A map cannot be read aloud in any form a listener can actually use, so it belongs in a companion document. Everything else gets tested one item at a time, against a single question: can a listener use this while the audio keeps running?

The test for whether back matter belongs in the audio

On the page, an appendix is a reference tool. The reader consults it out of order, at a moment of their choosing, and puts a finger in the chapter they left. Audio takes all of that away. A listener gets one pass, at the speed you set, usually while doing something else with their hands.

So the test is whether hearing it once, straight through, in the order you chose, leaves the listener better off. A glossary heard once at the start is a pronunciation lesson, and that is genuinely useful. The same glossary heard at the end is a list of words the listener has already survived without.

Run every piece of your back matter through that question separately. Fantasy novels tend to carry four or five kinds at once, and they do not all get the same answer.

A glossary works up front, as a pronunciation contract

Move it. A glossary at the back of an audiobook is dead weight, but the same content at the front does a job nothing else in the file can do: it teaches the listener how your invented words sound before the story starts leaning on them.

Keep it short. Fifteen or twenty entries is plenty, even if the print glossary runs to eighty. Pick the terms the listener meets in the first few chapters. For each entry, say the word and give a single clause of meaning. Anything longer turns into a lecture.

AudioProducer.ai narrates the text you give it, so a spoken glossary is something you write into the manuscript rather than a feature you switch on. Two practical notes on getting it to sound right. Invented names often need to be spelled phonetically in the text you paste, because the voice reads what is written and not what you meant. Our pronunciation guide for invented names covers how to build that list before you generate anything. And because a glossary is a list, it needs air between entries. A per-paragraph pause override, set longer than your project default, keeps the entries from running together into one breathless block.

A map cannot be read aloud

This is the honest part. There is no narration of a map that works. Read as prose it becomes a sequence of place names with compass directions attached, and a listener retains almost none of it.

You have two real options. The first is to cut it and let the prose carry the geography, which is what the prose was already doing. The second is to put the map in a companion PDF, which is how print-heavy nonfiction has handled charts for years.

One thing to be clear about: AudioProducer.ai exports an MP3 and stops there. We do not distribute or list your audiobook anywhere, and there is no place inside the product to attach a PDF to the audio. The companion document travels through whichever store or platform you publish on, under that platform's rules.

Dramatis personae, and the spoiler problem

Cast lists are the piece writers argue about most. Read at the front, a dramatis personae tells the listener that the quiet stablehand in chapter two is the exiled heir, forty pages before the book intended to. Read at the back, it arrives after the listener has already sorted everyone out.

The better answer is usually to let the casting do it. When each speaking character has a distinct voice, the listener builds the cast list in their head as they go, and they build it in the order you wrote. In AudioProducer.ai you assign a voice per character from the Voices page, and Auto-Assign Characters will do a first pass at tagging each line by speaker. Treat that pass as a starting point and re-tag what it got wrong in the editor before generating audio. Our guide to epic fantasy audiobooks with AI goes further into casting a large invented world.

Family trees, timelines, and the rest of the visual back matter

Family trees and timelines share a problem. They work because the eye can hold a whole structure at once and jump around inside it. Narrated, a family tree becomes a recitation of who begat whom, and a timeline becomes a list of dates with events bolted on. Neither survives the format.

Cut them from the audio. If the information genuinely matters, the fix is usually a sentence or two of orienting prose at the start of the chapter that needs it, written for the ear. A listener will hold "three generations after the sundering, the old house still had a claim" much more easily than a chart read aloud.

Where the surviving back matter should sit

Whatever survives the test needs a position in the running order and a boundary the listener can hear. Front matter comes first: opening credits, then a short glossary or a spoiler-free cast list if you kept one. The story follows. Author's notes and acknowledgements go at the end, after the last chapter, where a listener who is done can simply stop.

Give each piece its own section rather than gluing it onto the first or last chapter. In AudioProducer.ai you split the manuscript into chapters and generate them separately, which is covered in our post on splitting a manuscript into audiobook chapters, and it means a listener can skip the glossary on a re-listen without scrubbing through a chapter to find where it ends. Set a longer project-wide paragraph pause for these sections than you use in the prose, so the shift in register is audible. Our notes on opening and closing credits cover the standard wording for the top and tail, and the same triage logic applies to footnotes and endnotes, which are the nonfiction version of this problem.

You can test all of this before committing to a full book. AudioProducer.ai gives you 1,200 words free with no card, which is enough to generate a glossary section and a chapter opening and hear whether the pacing holds. Paid plans start from $39.99/month.