How to Use a Poker Solver to Study
A step-by-step workflow for studying with a GTO solver: set up the spot, run it to convergence, read the frequencies, and turn output into real edges.
On this page · 5 sections
To use a poker solver you define a spot precisely, run it until the strategy stabilizes, then read the output as frequencies and study why each hand acts the way it does. Do that and abstract theory turns into repeatable in-game patterns. Here is the workflow from setup to a study routine that actually fixes leaks.
Define the spot before you touch solve
Bad inputs produce useless strategy. Lock down five things first:
- Effective stacks — the smaller of the two stacks, in big blinds. 100bb and 40bb play completely differently.
- Positions — who opened, who defended, and from where.
- Ranges — the realistic hands each player holds entering the spot. Start from sensible preflop ranges rather than inventing them.
- The board — the exact flop, plus turn and river if you’re solving later streets.
- Allowed bet sizes — the sizings each side may use. Fewer, cleaner sizes make the output far easier to learn.
If you’re new, keep it minimal: heads-up, single-raised pot, one or two bet sizes. Every extra sizing multiplies the tree and blurs the pattern you’re trying to see. Add complexity only once the simple version is second nature.
Run it to convergence, then read it in layers
A solver doesn’t look up an answer — it plays the spot against itself thousands of times until neither side can improve, and that stable point is the equilibrium. Watch the exploitability number, which measures how much a perfect opponent could beat the current strategy for, fall toward zero. Once it’s low, the output is trustworthy; stopping early gives you a half-baked strategy that only looks authoritative.
The output itself is almost never “always do X.” It’s mixed — a hand might bet 70% and check 30%, because that blend is what keeps you unexploitable. Read it in layers rather than fixating on one cell:
| What you see | How to read it |
|---|---|
| A colored range grid | Each hand’s action mix at a glance — bet, check, call, fold |
| A single hand’s split | Its exact frequencies, e.g. bet big 40% / bet small 20% / check 40% |
| Overall action % | How often the whole range bets, and at what size |
| EV numbers | Which line earns more when two options are close |
Step back and ask which classes of hands bet — top pair, draws, air — and why. That reasoning is what transfers to new boards; a memorized percentage does not.
Turn each solve into a written principle
The step most players skip is writing the takeaway down. For every solve, note one or two conclusions in plain English:
- “On this dry board I c-bet small with my whole range.”
- “Flush draws prefer to raise here rather than call.”
- “My weakest bluffs are the ones with no backdoor equity — those give up.”
You’re assembling a library of principles, not a lookup table. Ten principles beat a hundred memorized cells.
Mine the gap between equilibrium and real opponents
The equilibrium is a defensive baseline: it can’t be exploited, but it also doesn’t punish anyone’s mistakes. The profit lives in knowing how a real opponent differs from it.
- Against a player who folds too much, over-bluff the frequencies the solver holds down.
- Against a station who never folds, cut the bluffs and value-bet thinner.
- Against a passive reg, size your value bets up, because they’ll pay them off.
A sharp drill is to solve a spot, then re-run it after nudging one player’s strategy toward a common mistake. You’ll see instantly how the optimal response shifts — and that shift is the exploit you carry to the table.
A weekly rhythm that compounds
- Pick one spot type you actually face — defending the big blind versus a button raise, say.
- Solve three or four boards in it — dry, wet, paired.
- Note the shared pattern across them, not each individual answer.
- Test it in postflop play and check the results in your tracker.
- Repeat next week with a new spot. Depth beats breadth every time.
If you’re still unsure what the engine is doing under the hood, start with what a GTO solver is, then work through the rest of the poker tools that make study systematic.
Frequently asked
How long should a solve take?
It depends on the spot's complexity and your convergence target, called exploitability. Simple single-raised pots resolve in seconds to minutes; complex multiway trees with many bet sizes take much longer. Aim for a low exploitability figure so the output is trustworthy.
Can you use a solver while playing?
No. Solvers are an off-table study tool. Real-time assistance during play is banned on virtually every site and treated as cheating. Study the patterns away from the table, then apply the understanding live from memory.