You recorded the session. That was the easy part, and it's also where most people stop, because what you have now is three hours of audio that nobody, including you, is going to sit through again.
Handing it over costs about a minute of your attention. Two things are worth knowing first, because neither is signposted anywhere and both change what you get.
It stops twice and waits for you. A DM who uploads a file and walks away comes back to something that looks stuck and is actually holding a door open.
What comes back is a draft. Nobody at your table sees it until you say so. That's deliberate, and it means you get to read the thing before your players do.
Before you start
You need a recording. It doesn't have to have been made in MythWeaver. MP3, M4A, WAV, OGG and WEBM all work, up to 500 MB, which is far more than an evening of audio.
You also want your players in the campaign, with their characters attached, before you upload. That's the difference between a recap that uses your party's names and one that guesses at them. More on that at the roster step, which is where it bites.
On the free plan you get one recorded session a month. It doesn't stop you at the door. It tells you afterwards, on the finished session, in as many words: that was your recorded session for this month, and here is what a paid plan records instead. Worth knowing before you spend it on a test file rather than on a real game.
Getting the write-up
1. Open the campaign, go to Sessions, and press New session. If the campaign doesn't have any sessions yet, the button says Record a session instead. Either way you get four ways in.
Upload audio is the one you want. "Record now" starts a live recording that runs from the nav on the left. "From a summary" is for when you already wrote the recap yourself and just want it in the campaign. "Plan a session" is for getting ready for the next game, not for one you've already played.
2. Drop the file in, or click to browse, then press Create session. It shows the name and the size first, which is the moment to notice you grabbed the wrong file.
3. First stop: who was at the table. The upload drops you straight onto the roster screen, and nothing else happens until you answer it. It wants to know who was there and, for each player, which character they were voicing this session. It starts everyone on the character they played last time, so switch anyone whose character changed.
Answer this one properly. It's the step that teaches the recap your party's real names. We ran it with the roster left empty and the write-up came back calling Sister Ovanne "Ovan" and Kadar Voss "Cada". It heard the sounds correctly and had nothing to check them against. Invented names are exactly what transcription is worst at, and the roster is the fix.
If you run solo, or you haven't invited your players yet, this screen will only show you. That's fine. Press Start the recap.
4. Second stop: whose voice is whose. Once it has listened, it comes back with the voices it separated out and asks which player each one is. Anyone it recognised from a previous session is already filled in, so this gets shorter every time. Voices that weren't part of play, someone's partner in the next room, get set aside here.
Both stops offer Skip for now, and both offers are honest. Each one asks you to confirm before it skips. Skipping costs you the per-player detail, not the recap.
5. Leave it alone for a couple of minutes. It transcribes, then reads the whole thing back looking for who turned up, where you went and what happened. Our short test clip took about a minute and a quarter from Start the recap to a finished draft. A real evening takes longer, and you don't need to sit and watch it.
How to tell it worked
The session gets a title it wrote itself, and a line telling you what it found: how many moments went on the timeline, and how many places, items and scenes. Under that's the recap in three parts, where we left off, a quick summary, and the full story. Along the top are tabs for the scenes, the characters, the cast and places, the audio with its transcript, the events, the rolls and the inventory.
It will say Draft. Only you can see this. That's the honest state. Your players have nothing yet.
Read it, then press Publish & send to players. That opens Share with your table, where you pick how it goes out: email each player their own recap, post it to your campaign's Discord channel, or both. Discord only lights up once a channel is connected to the campaign. If you skipped the roster, it tells you here that nobody's marked as playing, so there's nobody to email yet.
Press Publish and send and it's gone. Emails can't be recalled, so read first. Turn both switches off and the button becomes Publish quietly: the session is readable in the app and nobody gets told.
When it goes wrong
It looks stuck. Nine times in ten it's one of the two stops waiting for an answer. Open the session and see which question is on screen. This is the most common thing that happens by a distance, which is why it's at the top of this list.
The names are wrong. Fantasy names get mangled unless the roster gives it something to match against. Fill the roster in and run it again if you skipped that step, or fix them in the recap with Edit, which saves as you type.
It only heard one voice. Recordings where everyone shares a microphone, or where the audio has been flattened to a single track, give it much less to separate. You still get the recap. What you lose is the per-player detail, so set aside what it offers and move on rather than fighting it.
Where to go next
If you haven't settled how you record in the first place, that's worth sorting before next session rather than after: three ways to get the audio.
And if you've ever wondered why notes taken mid-game come out as unreadable fragments, we wrote about that. This page is the answer to the version of that problem where you gave up and hit record instead.