How to Organize Your D&D Homebrew (So You Can Actually Find It Later)

You've got a folder somewhere. Maybe it's Google Drive. Maybe it's a stack of Notion pages. Maybe it's seventeen browser tabs you keep meaning to close.

Inside that folder is a custom subclass you built two years ago, a magic item you're pretty sure was balanced, three half-finished campaign settings, and a faction you designed for a one-shot that never happened.

You can't find any of it when you need it.

Homebrew accumulates. Most GMs never build a system for managing it — they just keep creating, keep saving things wherever, and eventually lose track of what they actually have. Here's how to fix that.

The Core Problem: Creation vs. Organization

Most homebrew tools are optimized for creating — GM Binder for PDFs, Homebrewery for formatting, Notion for notes. Almost none of them are optimized for finding what you made or sharing it with someone else.

The result: brilliant homebrew gets used once, never found again, and eventually recreated from scratch.

A good organization system does three things:

1. Makes it fast to find something you made months ago
2. Makes it easy to share a specific piece with your table or the internet
3. Keeps related pieces grouped so your homebrew feels like a coherent body of work, not a pile of files

The Folder Structure That Actually Works

Whether you're using Topicfolio, Notion, or a plain folder system, this structure works:

🧙 Classes & Subclasses

One document per class or subclass. Include: the full mechanics, any playtesting notes, and the version number. Yes, version number — homebrew gets revised.

⚔️ Magic Items

Organized by rarity. A single searchable list is more useful than individual documents for items — you want to be able to scan "uncommon items" quickly when prepping a session.

🌍 Campaign Settings

One folder per setting. Inside each: world overview, factions, major locations, NPCs. Even if you never run this setting, having it organized means you can cannibalize pieces for other campaigns.

🗺️ Adventures & One-Shots

One document per adventure. Include: premise, key NPCs, maps (linked), encounter notes. Tag completed adventures so you know what's been played.

🎲 Rules & Variants

House rules, variant mechanics, optional systems. Keep this flat — one searchable document is better than a nested folder structure.

The Two Decisions That Matter Most

Decision 1: Public vs. Private

Some homebrew you want to share with the world. Some is table-specific. Some contains spoilers for your current campaign. Decide on a default — most GMs should default to shareable and lock things down selectively, rather than the reverse. Shareable homebrew gets feedback and gets better.

Decision 2: Living vs. Archived

"Living" homebrew is actively being used or refined. "Archived" is stuff you've finished or retired. Separate these. Archived homebrew clutters your active workspace and makes it harder to find what you're currently working with.

Making Your Homebrew Actually Findable

Three things make homebrew findable:

Consistent naming. "Ranger Subclass - Swarmkeeper (v2)" is findable. "new ranger thing FINAL" is not. Pick a naming convention and stick to it.

Tags or categories. When you save something, tag it: class type, campaign it was used in, whether it's been playtested. Even 3-4 tags dramatically improves searchability later.

One canonical home. The moment your homebrew lives in three different places (Google Drive, Discord, Notion), you will lose track of which version is current. Pick one place. Put everything there. Link to it everywhere else.

Sharing Homebrew with Your Table

This is where most organization systems break down. You've organized everything beautifully — for yourself. But when a player asks "can I use that custom subclass you mentioned?" you're still copying text into Discord.

A better approach: publish your homebrew to a permanent, shareable URL. When a player asks, you send one link. It's always current. No PDFs to re-export, no Discord messages to scroll through.

Topicfolio Folios work well for this — a homebrew subclass or magic item collection lives at a stable URL, readable by anyone without an account. Your table bookmarks it. You update it in place. The link never goes stale.

Try it: The D&D Campaign Starter Kit shows how this looks in practice — a living document your whole table can reference.

The 5-Minute Homebrew Filing Habit

Every time you finish a piece of homebrew:

1. Give it a proper name (with version number if it'll be revised)
2. Drop it in the right category
3. Note whether it's been playtested
4. Publish it if it's shareable

5 minutes. Do it before you close the tab. The alternative is spending 20 minutes searching for it six months later.

📂 Free template → D&D Campaign Starter Kit — a living document structure for campaigns, ready to fork and use.