RangeSharp
RangeSharp
Paste solver output, auto-detect format, confirm. PioSolver, HRC, Equilab, Flopzilla, and more. No wizard needed.
If you've ever tried to move a range from PioSolver or HRC into a training tool, you know the pain. Export to CSV. Convert to some proprietary format. Map columns. Hope the hand notation matches. Maybe it works. Maybe you get 50% through and hit an error. Start over.
FreeRangeLab does it differently. Paste. Done.
I used FreeBetRange for a while. Their import flow: a multi-step wizard. Step 1: choose your source (PioSolver, HRC, etc.). Step 2: upload a file or paste text. Step 3: select which nodes from the solver tree you want. Step 4: map the output format to their grid. Step 5: preview. Step 6: fix mapping errors because "AhKd" didn't match their "AKs" format. Step 7: try again. Steps 8 through 11: swear, take a break, consider learning Python to write a converter.
I timed it once. Thirty-seven seconds from copy to usable range. When it worked. When it didn't, I gave up.
Here's the FreeRangeLab flow:
Open your solver. PioSolver, HRC, Equilab, Flopzilla, Simple Preflop, GTO Wizard. Any of them.
Copy the range output. Ctrl+C (or Cmd+C). The raw text. No export, no conversion.
In FreeRangeLab, open the spot where you want the range. Click the spot in the strategy tree. The grid loads.
Paste. Cmd+V (or Ctrl+V).
The system auto-detects the format. A toast or banner appears: "PioSolver format detected" or "HRC format detected."
A preview appears on the grid. You see the range mapped to the 13x13 matrix. Check it. Looks right?
Click Apply. Or press Enter.
Done.
Three seconds. Maybe five if you're slow. No wizard. No column mapping. No format guessing.
The auto-detection handles the common ones:
PioSolver: The text output you get when you copy a range node. Combo notation, percentages, whatever Pio spits out. The parser recognizes it and maps to the grid.
HRC (Holdem Resource Calculator): Same idea. Copy from the range viewer or solver output. Paste. Detected.
Equilab: Range strings, combo lists. Works.
Flopzilla: Range format. Works.
Simple Preflop: Their export format. Works.
GTO Wizard: Copy from their interface. Works.
FreeRangeLab native (.frlab): If you exported a strategy from FreeRangeLab, you can paste that too. Useful for sharing complete strategies with teammates.
I've pasted PioSolver, HRC, and Equilab output. All three detected correctly on the first try. Your mileage may vary with obscure formats, but the common ones are covered.
If you've got a pile of HRC solutions in a .zip, you don't want to paste each one. Elite subscribers get mass import: upload the .zip, the system parses all the files, and you get a list of detected ranges. Pick which ones to add to which spots. Bulk apply. Useful when you're migrating from HRC or building a strategy from a full solution set.
Free users get paste. Pro gets paste. Elite gets paste plus mass .zip import. The paste path works for everyone.
You can export your full strategy (all spots, all ranges, notes, colors) as a .frlab config file. Share it. Someone else imports it. They get your exact strategy. No "send me your PioSolver trees" and hope the formats line up. One file. One import. The strategy tree, the ranges, the overlays you use. All of it.
Good for coaches sending ranges to students. Good for study groups. Good for backing up your work.
The parser reads the pasted text. It looks for hand combos (AhKh, AKs, 22+, etc.), range notation (ATo+, KQs), and format-specific markers. It builds an internal representation of the range, maps it to the 13x13 grid cells, and shows the preview. When you Apply, it writes to the spot. The existing undo stack works, so if something goes wrong, Undo brings back the previous range.
Mixed strategies (e.g., "raise 75%, fold 25%" for a hand) are supported. The parser detects frequencies and maps them. You paint with Shift+click for manual frequency entry, or the import brings them in if the source has them.
The old model: your solver is the source of truth, and the training tool is a separate system. You have to bridge them. Export, convert, import. The bridge is annoying.
The new model: the training tool accepts solver output directly. No bridge. Your solver and your trainer speak the same language. Copy from one, paste into the other. The barrier between "I have the correct range" and "I'm training the correct range" disappears.
I run PioSolver for custom spots (weird stack depths, specific rake, etc.). I paste the output into FreeRangeLab. I'm training the exact range I solved for. No transcription errors. No "I think that's close enough."
Sometimes the parser gets confused. Very weird custom notation, or a format that's almost-but-not-quite one of the supported ones. In those cases, you can paste and then manually adjust. The import gets you 90% there. You fix the remaining 10% with clicks.
If auto-detection fails, you might see "Format not recognized." Paste the raw text anyway. Check the support docs or the in-app format guide. There might be a small tweak (e.g., remove a header line) that makes it detectable. I haven't hit this with PioSolver or HRC. YMMV with niche tools.
I solve a spot in PioSolver. I tweak rake, stack depth, whatever. I copy the range. I switch to FreeRangeLab. I open the matching spot in my strategy tree. I paste. I see the preview. The grid lights up with the right cells. I hit Enter. I'm done. Total time: under five seconds. I've done this dozens of times. It hasn't failed yet for standard Pio output.
For HRC, the process is the same. Copy from their tree view or range display. Paste into FreeRangeLab. The format differs from Pio, but the auto-detection handles it. Same for Equilab. I've imported from all three in a single session when building a strategy from multiple sources. No need to remember which format goes where. Paste. Apply. Next spot.
I've thought about this. The multi-step wizard exists because the tool has to support dozens of formats and the developers can't reliably auto-detect all of them. So they make you pick. "Are you pasting PioSolver or HRC?" That reduces ambiguity. It also adds friction. Every step is a chance to quit or mess up.
FreeRangeLab's approach: try to detect first. If we recognize it, we map it. If we don't, we show an error and maybe suggest a format. For the major solvers, detection works. That removes the friction. You might hit an edge case. Most of the time you won't.
I use the library for standard spots. BTN Open, CO Open, BB vs BTN. The Simplified GTO (rounded to 25%) is fine for learning. I use paste when I've run a custom solve. Different stack depth. Different rake. A specific spot I'm working on. The solver output goes straight in. No "close enough" library substitute.
Some people paste everything. They have a full PioSolver tree. They import it spot by spot. Takes longer than library for the first pass, but you get exact ranges. Your call. The paste path supports both workflows.
Different solvers use different notation. AhKh vs AKs vs AK suited. The parser normalizes. It understands combo format (AhKh, AdKd), shorthand (AKs, AKo), and range notation (22+, ATs+). When you paste, the preview shows the grid. If a hand is in the wrong cell (e.g., suited vs offsuit mix-up), you'll see it. Fix it manually. The import handles 95% automatically. The last 5% is rare and easy to correct with a few clicks on the grid. I've imported hundreds of ranges. I've had to fix something manually maybe three times. All three were from a solver output that included custom annotations or formatting I'd never seen before. Standard PioSolver, HRC, and Equilab output? Zero issues. The parser is tuned for the formats people actually use. If you're on the fence about whether your solver will work, paste a sample. The worst case is "format not recognized." You lose five seconds. The best case is a working range in three. I've converted entire strategy trees in under ten minutes. Spot by spot, paste and Enter. No wizard, no mapping, no headache.
Eleven steps and 30+ seconds in the old flow. Paste and Enter in the new one. That's the difference. Your solver stays your solver. Your trainer stays your trainer. The handoff is three seconds.
Master your preflop ranges.