Table Canon is a tool for tabletop RPG game masters that turns uploaded game-night audio into a session recap, an outline, and a prep desk. It is built for the person running the game — the game master who wants to stay in the scene while playing and then sit down later with the whole night in one place. The product states its promise plainly: play the session, prep from the recap. Rather than asking a GM to write notes while the story is moving, Table Canon takes the recording of the session and turns it into written material the GM can actually use when preparing the next game. Callbacks from earlier sessions show up when you prep, so the campaign's own history becomes the source of future hooks. The site frames the whole product around a simple idea: solid foundation, lasting stories.
The problem Table Canon addresses is stated directly on its site: you meant to write it down, but the scene had already moved on. Prep night should not start by reconstructing the last session from memory. Notes capture only what you had time to scribble during play, and a general chatbot only knows what you paste into it. Table Canon puts the recap, the outline, and the open threads in one desk, so a promise made three sessions ago can become next week's hook without pausing the table to record it. The goal is to let the GM focus on the game and then prep from what already happened, instead of losing the thread between sessions or hunting through old chats and documents for details that may never have been written down at all.
The process begins with uploading a recording. The audio is the notes: you played, and the recording stands in for the note-taking you did not do. Today, on the web, a game master uploads an audio file from game night. Live recording on the mobile app and in the browser is described as coming soon. Also marked coming soon are optional GM notes for secrets and corrections, layered on top of the audio — a way to add information the recording alone would not capture. This approach keeps the GM inside the scene rather than at the edge of it with a notebook, and it means the record of the session is created automatically rather than depending on how much time anyone had to write things down.
Once a recording is uploaded, the night lands in one place. Table Canon produces a transcript, speaker labels, an outline, and a Recap. The site states that this material is usually ready in about 15 to 20 minutes, depending on session length, and that users see a "Building your campaign…" indicator until the session is ready. Having the transcript, the speakers, the outline, and the recap assembled together means the GM does not have to piece the evening back together from scattered files, memory, or half-finished notes. The recap and outline are designed to be read before planning the next scene, so preparation starts from a written account of what actually happened at the table.
Preparation then starts from that desk. The prep desk surfaces open threads, hooks, and the people who mattered during the session. Earlier nights resurface as callbacks, which is how continuity across a long campaign is maintained without manual bookkeeping. This is described on the site as "the desk you open on prep night" — a single place where the loose ends from previous sessions are already visible. Instead of asking the GM to remember which promise, faction, or unresolved question is still live, the prep desk collects those elements from the campaign's own history and puts them in front of the person planning the next game.
The campaign's world is also kept current. Table Canon maintains NPCs, places, and factions that are updated from play, described as "a world that keeps up." When the AI gets something wrong, the site says that this happens and provides tools to fix it: voice samples can be calibrated for better speaker labels, and on any World dossier a GM can use GM corrections to fix names, blurbs, aliases, and mistaken duplicates, merging or marking them distinct. Reviewing the session Recap before sharing it is recommended, and corrections stick for Ask and future sessions. When a fact is fuzzy, the GM can ask — for example, "What did they promise the tavern keeper?" — and the answers cite the sessions they came from. That citation behaviour is a stated differentiator from pasting text into a chatbot: the memory is derived from play, with evidence.
The site positions Table Canon against do-it-yourself approaches with a direct comparison. Taking notes while you play means you leave the scene; Table Canon keeps audio as the record and notes optional. Reconstructing the last session before you can even prep leads to scattered memory and old chats; Table Canon puts recap, outline, and prep in one place. Coming back next week and pasting into a new chat causes names to drift; Table Canon keeps the same campaign desk, updated from each night. Building a campaign wiki by hand drifts from what players actually did; Table Canon's memory is derived from play, with evidence. And asking "what did they promise in session 4?" normally means hunting old chats and docs, while Table Canon lets you ask with citations into your actual sessions.
The stated outcomes for users follow from that design. After game night you get the night in one place: a recap and outline you can read before planning the next scene. You get a prep desk with open threads and hooks, including callbacks from earlier nights. And you get a world that keeps up, with NPCs, places, and factions updated from play. Together these pieces mean prep time is spent planning forward rather than reconstructing backward. The memory of the campaign evolves each session rather than being frozen at whatever was written down at the time, and answers about past events are backed by the sessions they came from.
Concrete use cases appear throughout the site. A game master can upload a recording after game night and, roughly 15 to 20 minutes later, read the recap and outline before planning the next scene. During prep, they can open the desk to see open threads and hooks, including callbacks from earlier nights that become next week's hooks. When a detail is fuzzy, they can ask a question such as what the party promised the tavern keeper and get an answer citing their sessions. They can browse a real campaign from a live table — World, Story, and night-by-night Recaps — and try Ask on the sample campaign, including questions that pull from an earlier night, before uploading anything themselves. After a session is processed, they can review the Recap before sharing it, calibrate voice samples for better speaker labels, and use GM corrections on World dossiers to fix names, blurbs, aliases, or merge mistaken duplicates.
Table Canon is built for the table and works with the systems game masters already run, listing Dungeons & Dragons, Pathfinder, Call of Cthulhu, and indie TTRPGs. The site notes that memory stays campaign-shaped, not system-locked. Pricing starts with a free tier: 6 hours of processed audio lifetime, no login and no credit card required, with the option to try as a Guest. Free access includes the full desk — campaigns, World, Story, Prep, and Ask — and the sample campaign tour can be explored without uploading anything. Plans are priced on processed audio hours once a user outgrows Free. The site states that session audio and campaign content run on your account only and are not used for public model training, and that live recording on the mobile app and in the browser is coming soon, while the web beta today supports uploading a session recording.
Table Canon's core value proposition is that the session itself becomes the campaign's memory. By turning uploaded game-night audio into a transcript, speakers, outline, Recap, a prep desk of open threads and hooks, and an evolving world of NPCs, places, and factions — all searchable with answers that cite your sessions — it removes the need to take notes during play or reconstruct the last session from memory before prep. Game masters stay in the scene while playing, then open one desk on prep night where earlier nights surface as callbacks, corrections stick, and the story keeps its foundation from session to session.