Selling tabletop RPG adventures as downloads: the session your buyer has to run for people who will test every door

Every other download is used by the person who bought it, roughly the way the maker intended. An adventure is not. It is run, live, by a game master who did not write it, for players who will ignore the villain's speech, befriend the monster that was supposed to be a fight, and ask what is behind the one door you left blank. If the adventure survives that table, you have a product. If it only survives a quiet read-through at your desk, you have a refund request that quotes page numbers. The craft of selling adventures is not writing a good story. It is writing a kit another person can run under pressure, with four expectant faces watching, and no time to search a forty-page PDF for one number.

The product is a kit, not a PDF

Say in the listing, in plain words, exactly what is in the download: the adventure itself, and everything that comes with it. A complete kit usually means the main PDF, separate battle maps, player handouts, and any tokens or images the encounters assume. List each piece by name and format. "Includes maps" is the sentence that generates the support email; "includes five maps, each in print and virtual-tabletop versions" is the sentence that prevents it.

Keep the pieces in clearly named folders, and keep the main PDF complete on its own. A game master who prints only the adventure the night before should still be able to run it — maps and handouts extend the session, they should not be load-bearing in a way that strands a buyer who missed a file buried three folders deep. Put a one-page contents list at the front of the download naming every file and what it is for. Ten seconds with that list is the difference between a buyer who feels equipped and a buyer who feels they have been handed a puzzle.

Name the system, the edition, and the level — exactly

An adventure is only correct for the game it was built for. The same dungeon written for one edition's rules will land wrong — numbers off, assumptions broken, a boss fight that is either a cakewalk or a massacre — under another edition, another system, or the same system at a different character level. "Works with any fantasy game" is the claim that generates your angriest reviews, because it is the claim a buyer tests first and hardest.

Name the operative facts in the listing and on the cover: the exact system and edition, the character level or tier the adventure is balanced for, how many players that balance assumes, and the expected run time in sessions, not hours you hope for. If you also ship a conversion or a system-neutral version, name it as a separate file rather than letting buyers discover a second stat block halfway through a page. Name what you did not test, too. An honest "balanced for four characters; not playtested for solo play" line prevents the review that calls your maths broken when the table was never the table you wrote for.

Maps are a second product hiding inside the first

A map has to work twice: printed on paper at a real table, and imported into a virtual tabletop on a screen. Those are different files. The print version needs a scale a home printer can honour, pages that tile without losing the doorway, and ink a buyer can afford — a full-bleed black dungeon is a toner bill with a map attached. The screen version needs resolution high enough to zoom without dissolving, a grid version and a gridless version, and dimensions stated in squares, not just pixels, so the buyer can line it up in their software without guesswork.

Name the files for the use, not for your art folder. A file named for its room, its version, and its grid — room first, version second — gets found mid-session; a folder of evocative one-word names gets opened once and renamed in frustration. Keep the names stable across updates for the same reason every file seller should: a campaign in progress has those maps already imported and aligned, and a renamed map is a missing map when the next session loads.

Separate what the players may see from what they must not

An adventure download contains spoilers by design — and the most damaging support case in this niche is not a broken file, it is a leaked one: the game master forwards the whole folder to the group chat, or a player handout turns out to have the secret-door version of the map, and a mystery built over three sessions ends in an accidental screenshot.

Build the separation mechanically, not by warning. Player handouts live in their own folder, named as player-safe, and contain nothing a player may not see — no GM map with secret markings, no letter whose reverse side shows the twist. The GM versions live separately and say so in the filename. Then test it the hostile way: open only the player folder and read it as a player. If anything in it gives the game away, the separation is a rumour, not a feature. State the split on the listing; buyers who run for spoiler-hunting groups — which is most groups — shop for exactly this discipline.

Write for the search, not the read-through

Nobody reads an adventure at the table. The game master searches it, mid-sentence, while a player waits. A beautiful narrative flow that buries a difficulty number in paragraph three is a product that fails at the only moment it is used.

Put the runnable facts where a search lands: encounter numbers, checks, and rewards in consistent, findable places — a stat line, a box, a bold lead-in, the same shape every time. Bookmark the PDF properly and hyperlink the contents page, the index, and every "see page" reference, then test those links in a fresh reader rather than your authoring tool, which will lie to you about what survived export. Include a one-page run summary — the plot in five lines, the important names with pronunciations if you invented them, and what must not be improvised away because a later scene depends on it. That page is the most-used page you will ever ship, and the one most adventures leave out.

The licence lines adventure buyers actually hit

Adventure licensing has two questions that generate nearly all the disputes, and both are about the buyer's own table becoming public. First: can a buyer run your adventure on a streamed or recorded actual-play show, including a monetised one? Second: can they share the files with the other game masters in their group, or print copies for their players? Spell out the operative lines in plain words, in the listing and in a licence file inside the download: running the adventure, live or streamed, is the use you are selling; redistributing the files themselves — uploaded, shared beyond the buyer's own table, or folded into a compilation — is not; and say plainly whether handouts may be printed and handed out, because that is the one sharing act your product is designed for and buyers should not have to guess that it is allowed.

System rights deserve their own honesty line. If your adventure relies on a publisher's open licence or community-content programme, name it and follow its terms exactly, including any required legal notice inside the file. Never imply an official endorsement you do not have. This niche runs on trust between independent creators and the publishers whose games they write for; a seller caught dressing a fan work up as an official product loses both audiences at once.

An update is errata, not a rewrite

Adventures get played, and play finds what playtesting missed: the clue chain that breaks if one roll fails, the encounter balanced for a party that does not exist, the map label that contradicts the text. You will ship a corrected version. One rule protects every campaign already in progress: never silently change a shipped adventure in an update.

A group three sessions into your dungeon has notes, handouts, and a shared memory built on the version they downloaded. Quietly renumbering rooms or rebalancing a boss means their saved prep no longer matches their file, and they discover it live, at the table, in the worst possible minute. Ship corrections as a dated version with a plain-language errata list at the front — what changed, on which page, and whether it matters to a campaign already running. Add new material under new names; leave the original files available or clearly superseded, never vanished. Put the version and date in a README inside the download so a buyer can tell in ten seconds whether the folder on their drive is current, and announce the update to past buyers with the errata first: "three fixes from real tables, nothing your running campaign depends on has moved" is the whole pitch, and it is only true if you kept the discipline above.

A short launch checklist for adventure sellers

1. Name the contents in the listing: adventure length, every included file by format, and maps and handouts listed separately.
2. Name the game exactly: system, edition, character level, assumed party size, and run time in sessions — plus what you did not playtest.
3. Ship maps twice: a printable version a home printer can afford, and a screen version in grid and gridless, sized in squares.
4. Separate the spoilers mechanically: a player-safe folder tested by reading it as a player, GM files named as GM files.
5. Write for mid-session search: runnable facts in consistent findable shapes, a bookmarked and hyperlinked PDF, and a one-page run summary.
6. State the licence lines buyers hit: streamed and recorded play, printing handouts, and the line at redistributing files.
7. Version like errata: dated updates, a front-page change list, stable filenames, and the original never silently rewritten.

One honest closing note on delivery: however you sell the kit, your buyers need the full set of files, in the right version, re-downloadable when a laptop dies mid-campaign, delivered to the person who paid without the files leaking to everyone who did not. That delivery layer is the part to choose carefully — and it is the part this site's sponsor, FileFreight, is built for: flat-rate download delivery with license keys, where payments settle into your own Stripe account. It does not handle tax or VAT (that stays with you), it has no adventure or map importer and no virtual-tabletop integration, and it is not a Shopify app — so judge it on the delivery job alone, and keep writing adventures your players cannot predict.