Most players looking for a D&D group online apply to too many tables, and the ones they apply to are the wrong shape for them. They open r/lfg on a Tuesday night, scroll past forty listings that all read like movie trailers, send three quick "hi, I'm interested!" DMs, and then wait. Two or three weeks later the response rate is zero, the patience is gone, and the working theory is that finding a table online is impossible.

It is not impossible. It is a different skill than playing in a table you have already joined. This guide is the player-side companion to our recruiting guide for GMs. Same idea, opposite seat at the table.

Why finding a D&D group online is hard

The market is lopsided. There are far more players looking for tables than there are GMs running them, and the gap is wider for online groups than for local ones. A typical r/lfg listing for a weekly 5e campaign collects fifteen to fifty applications in the first hour. The GM running it is reading those applications between dinner and putting the dog out. They are filtering hard, on signals that a casual reader might not notice.

The other half of the asymmetry is that most listings are written badly. They sell the campaign on tone and setting flavor, list a day of the week, and leave the rest to DMs. You will spend more time decoding what a listing actually means than you spend deciding whether to apply.

This is solvable. Not by applying to more listings, but by reading them with sharper eyes and writing applications that read like a partner, not a fan.

How to read a listing

The fastest way to filter listings is to read them in a fixed order, not top to bottom. The flavor paragraph is the last thing you should read, not the first.

Read the schedule line first. If it says "weekly" with no day and time, or "flexible" with no time zone, the GM has not actually nailed down when the campaign runs. That table will collapse by session four. Move on.

Read the boundaries section second. If the listing names content lines and the GM's own preferences on them, you have a GM who has thought about safety tools before recruiting. That is the table you want. If the boundaries section is missing entirely, the conversation will happen at session zero in a rush, or worse, at session three by accident.

Read the application question set third. If the questions are specific ("describe a character you played recently that you really enjoyed") you have a GM who will read your answers. If the questions are vapid ("why do you want to play 5e?") or there are none at all, the application is going to be ignored or filtered on profile alone.

Then read the flavor paragraph. This is where you find out whether the campaign is the kind of game you want to play. By the time you get here, you have already filtered out half the listings on schedule and structure. The flavor is the last filter, not the first.

Listings to skip

A short list, drawn from a few hundred reads of r/lfg recruiting posts.

• No time zone on the schedule. Means the GM does not know who they are recruiting yet.
• "DM me if interested" with no questions. Means the GM will pick the first three responders, not the three best fits.
• A long world-flavor opener with no logistics. The GM is selling the campaign, not staffing it.
• Promises of "epic", "found family", or "the campaign of a lifetime". Movie-trailer language usually means the GM does not have a clear sense of what the table is yet.
• A capacity of seven or eight players. Tables that big almost always collapse around scheduling. Four to six is the workable range.
• No mention of session zero. The campaign that does not have a session zero on the calendar is the campaign that surfaces incompatibility at session three.

None of these are absolute. A new GM running their first campaign might have a weak listing and still be a great fit. But if a listing has three of these signs at once, the table is not built yet.

How to write an application that gets read

Treat the application as a filter for the GM, not a sales pitch from you. The GM is reading fifteen to fifty of these. The ones that get read end to end are the ones that answer the actual questions, in the GM's language, with specifics.

Three principles.

Answer the questions, in order. Do not write a cover letter that ignores the question set. The GM will assume you did not read the listing.

Lead with the unsexy answer. If the question is about availability, your first sentence is your real availability through the end of the year, including the weeks you know you will miss. Reliability beats enthusiasm, every time. The GM cannot tell from a paragraph of enthusiasm whether you will show up. They can tell from a calendar.

Be specific. "I really like roleplay" is a non-answer. "The last 5e character I really enjoyed was a tiefling warlock who lied constantly about their pact and got caught at level four" is signal. The GM can picture your play style from one sentence.

What to leave out: long lists of systems you have played, your D&D resume, the campaign you ran in 2019 that fell apart. The GM does not need your CV. They need to know if you are reliable and if your taste matches theirs.

A working application is between 150 and 350 words. Shorter than that and the GM cannot tell whether you read the listing. Longer and you are competing with yourself for the GM's attention.

Session zero is your last filter

If the GM accepts your application, do not skip session zero. Session zero is where the listing's promises are tested. Your job in session zero is the same as the GM's: figure out, before anyone rolls dice, whether the table is the table the listing described.

Bring questions. "What does weekly actually mean at this table, including holidays?" "How do you handle a player not being able to make a session?" "What does a bad session look like to you, and what do you do about it?" The answers are signals. A GM who has run a table before will have specific answers. A GM who hasn't will tell you they will figure it out as they go.

If session zero raises a real concern, raise it. You can leave a table after session zero. You can leave a table at any point. Leaving on good terms is part of being a good player. The campaign that you exit at session zero is a campaign that did not waste your or anyone else's session three.

Where to look

A few specific surfaces, with the trade-offs.

r/lfg and r/lfgpremium. The biggest pool. Highest noise. Most listings here are sales pitches, not filters. Read the schedule line first, every time.

LFG Discords by system. Smaller pools, higher signal. A Pathfinder 2e LFG Discord with a few hundred active members will often have better-written listings than r/lfg.

Roll20 and Foundry community boards. Tied to specific platforms, so the GM has at least committed to the tool. Listings tend to be more structured because the platform asks for it.

Paid GM listings (StartPlaying, Roll20 paid). A different shape entirely. You are paying for a curated experience. Schedule reliability is usually better. The GM has more skin in the game.

Guildhall's Quest Board. The flow is built around the filter model: schedule is structured, content boundaries are on the listing, compatibility is computed before you apply. Smaller pool while we are in Foundation Release, growing as we onboard more GMs. The badge of "applying makes the GM read a compatibility snapshot" is the part that changes how the conversation starts.

Whichever surface you use, the reading order is the same: schedule, boundaries, questions, flavor.

How long it actually takes

Realistic numbers, from the cohort we have data for.

A player applying to two or three listings a week, with serious applications, finds a table they want in three to six weeks. A player applying to ten or fifteen listings a week with quick DMs finds nothing for two months and then quits.

The difference is not effort. It is shape. The serious applications get read. The quick ones get filtered out by the same GM filter that you are trying to pass.

The honest version

Finding a D&D group online is hard because the listings are written badly and the GMs are reading fast. The way through is not to apply more. It is to read sharper, apply slower, and be specific about who you are and what you want at the table.

The applications you write should sound like the kind of player you would want at your own table if you were running it. Reliable, specific, honest about taste, willing to say what you do and do not want. Not enthusiastic for its own sake.

The table you want exists. Three good weeks of reading and applying will find it. The right table starts at the listing, on both sides.