GG hand history import problems: a practical checklist
Separate three questions: is this a supported text format, did the action replay correctly, and can that hand be mapped to a supported analysis? Each failure needs a different fix.
Check the first line and the file type
The current GG text parser recognizes histories beginning with Poker Hand #. A screenshot, a video or a formatted chat summary is not that text format. If your export has an introductory message before the actual hand, test a copy containing only the complete hand.
Download the synthetic GG sample below as a control. It is designed to exercise the supported parser structure; it does not claim every GG product or client exports exactly the same format.
If Hero or cards are missing
Look for the Dealt to line and confirm that the player name matches the seat list. Check that hole cards and board cards retain their rank-and-suit notation, such as As Ah. Replacing suit letters with decorative symbols can change the format the parser sees.
Do not make up unknown hole cards just to get past an error. When asking for help, report whether Hero was detected and which street first looks wrong. Redact personal data consistently and share only what is needed.
If the replay pot or order looks wrong
Keep blind posts, antes, returned bets and the original bet/raise wording. A raise-to amount and a raise-by amount have different meanings. Start with one hand instead of combining several partially copied histories.
Compare the sample and your file in a text editor. Look for missing street markers or truncated final lines. Preserve the source export before editing; a guessed correction may make the hand parse while changing what actually happened.
If import works but analysis does not
A readable history may describe an unsupported game or a multiway flop. The current analysis mapper’s supported two-player scope is narrower than the set of hands that can be displayed. Do not remove a participant to force a multiway hand into a heads-up model.
For useful feedback, include your client/export type, the stage that failed, the error text and whether the downloadable sample worked. Never send login credentials. Unsupported analysis should remain visible as a limitation rather than a fabricated score.
Recorded web interface example. Layouts and available controls can vary by version.