Everything you prepped, in your hands at the table.
Session Two is where you write your session — and where it comes back as pages you can print, hand out, and run from. The layout, the maps, the cards, the tidying up: handled. You write the game.
Free plan, no card. Your writing stays plain markdown you can take with you.
The part nobody signs up for
You know this feeling
Not the part where you invent a villain. The part after.
It's 11pm on Wednesday
You sat down to write the reveal and spent forty minutes nudging margins so the stat block wouldn't split across two pages.
“I wrote that down somewhere”
The innkeeper's name is in a document, or a notebook, or a message you sent yourself in January. Five people are waiting while you scroll.
It looked fine on screen
Then the handout came out four pages long with two orphan lines, and the battle map printed at a scale where nobody's miniature fits the squares.
You're not sure what “ready” looks like
Plenty of tools will hold your notes. Almost none will tell you that three NPCs in Thursday's session still have nothing written under them.
How it works
Write it. Print it. Run it.
There's no new discipline to learn. It's notes — with the mechanical half done for you.
Write like you'd write notes
Headings, bullets, links between pages. A normal editor, saving plain markdown, so what you wrote is still readable in ten years and still yours.
Say what each thing is
This file is an NPC, that one's a battle map, this folder is Session 9. That's the whole setup — layout, printing, and sharing all follow from it.
Print the session
One packet: your outline, the stat blocks, the cards, the map tiled to scale. Fold it, put it in the binder, close the laptop.
Video
Two-minute walkthrough: writing a session, then printing the packet.
Why it's different
Made for the printer, not just the screen
Most tools treat printing as an export button and hope for the best. Here it's the point — the layout is doing the work you'd otherwise do by hand, an hour before the game.
Pages that fit, without you nudging anything
Session Two packs what you wrote into the fewest pages that still read well: columns balanced, blocks kept whole, no lonely paragraph stranded on page four. Change something an hour before the game and print again — the layout re-solves itself every time, so late edits don't cost you a re-layout.
Screenshot
Print preview of a session packet: two balanced columns, a stat block kept whole, page count in the corner.
Battle maps that tile to scale on a normal printer
Drop in a map image and Session Two finds the grid. Pick your square size and it splits the map across letter pages with every cut falling on a grid line, so the seams line up when you tape it together. One-inch squares that measure one inch, from the printer you already own.
Screenshot
A battle map split across four letter pages, grid lines aligned across the seams.
Cards and coins you'd otherwise build by hand
Spells, items, abilities — write them once and print them as cards whose text shrinks to fit its box instead of getting clipped. Portrait coins print in sheets, fronts and backs aligned, for the NPCs the party will actually meet.
Screenshot
A sheet of spell cards and a sheet of portrait coins, cut lines visible.
The rest of the busywork
Handled, so you can stop thinking about it
None of this is why you started running games. All of it is why prep takes longer than it should.
Find it before anyone notices
One shortcut from anywhere: match a file by name, or search the full text of everything you've ever written for this campaign.
Every save, kept
Versions happen on their own. See what changed, put a file back the way it was, or restore a whole folder — and stop keeping session-9-FINAL-v3.
Share a page, or don't
Public, secret, or private, page by page. Players get a link that works on a phone; your notes stay on your side of the screen.
Links that don't rot
Link between your pages as you write. Move or rename anything later and every link pointing at it follows along.
The 5e SRD, already in there
Spells, items, monsters, and feats you can reference, link to, and print as cards — without retyping a stat block ever again.
Your files on your machine
Optional: a small desktop app and a command-line tool keep a real folder in sync both ways, so your own editor and local tools can work on the same files.
Two different jobs
A place to build the world, built around the session
Worldbuilding is for you. Prep is for Thursday.
Your factions, your maps, your fifteen pages on the succession crisis — keep all of it here. But what you carry to the table is a different animal: short, ordered, and about what's happening tonight. Session Two holds both, and it's the second one it's built to produce.
Screenshot
A campaign library beside a session folder: the world on one side, tonight's four pages on the other.
A shape to fill in, not a blank page
A new campaign arrives with shelves already in place — NPCs, spells, items, battle maps, scenes — so a file you drop in lands somewhere and knows what it is. Open a session and it tells you what's still thin: the NPC that's a name and nothing else, the scene with no map, the folder you made and never came back to.
Screenshot
A session view listing what's prepared and what's still missing.
Questions people ask
Do I need to know markdown?
Do I have to use the command line?
Is this a virtual tabletop?
What can my players see?
I already keep everything in a notes app. Why move?
What does it cost?
Where can I use it?
Your next session is on Thursday.
Start with that one. Write it, print it, and see how it feels to walk in with the whole thing in your hands.
Free plan, no card required.