Created a new multi-room hand replayer. Looking for feedback

A couple things I’d personally love to see to make it “daily-driver” useful: first, a super clear list of what formats you support per room (cash/MTT/Zoom/PKO, antes/straddles, all-in run-it-twice, etc.), because the edge cases are where tools usually break. Second, some kind of “import sanity check” that flags parsing issues (missing actions, ambiguous seat mapping, currency/blinds weirdness) so people trust the output when they share a link. Feature-wise, tagging + quick navigation would be huge: jump to street, jump to last aggressive action, highlight bet sizes as %pot, and a one-click “copy/share as text” alongside the replay link. If you ever go beyond replaying, the next killer step is lightweight filters (“show me all 3-bet pots” / “all river check-raises”), even without full database features, a simple session-level search would make it stand out.

Also worth thinking about privacy: a visible “redact player names” toggle and a clear statement on what you store (and for how long) will make people more comfortable pasting hands from multiple sites.

How are you handling tricky stuff like all-in side pots, multiway with dead blinds/antes, and fast-fold formats? If you tell us what currently breaks most often, some ppl here can probably help you stress-test it with nasty HH samples.

Hey Andy,

First off, apologies for the delay. I didn't get notifications on the forum so I'm only seeing this now, two weeks later. But seriously, thank you for taking the time to write such detailed and thoughtful feedback. This is exactly the kind of input I was hoping for.
You've hit on a bunch of things I'm actively working on, so let me address them:

Format support & edge cases:
You're right that I need a clearer breakdown of what's supported per room. In theory, the replayer handles cash/MTT/Zoom/PKO/antes/straddles/run-it-twice across all the rooms, but the reality is that edge cases are everywhere. I'm constantly finding and fixing them. We have more than 1M hands in the database now, but people still upload hands every day that fail on some obscure parsing issue.

The validation trade-off:
This is probably the most important thing to explain. Unlike some other replayers that might display a hand even when actions are missing or math doesn't add up, I built this with very strict validation. The hand history is validated from entry to exit, and there's a headless player that detects math mismatches (pot sizes, stack changes, etc.).
The bad news? This means a lot more hands fail. Someone uploads a hand, it fails, they probably think "fuck, this is another sloppy replayer" and never come back. But the truth is the opposite. It's failing because it's strict. Sometimes it fails on something that wouldn't even affect the replay (like a date parsing error), but I still want everything to be accurate.
When hands fail, they go into a folder I personally review. I fix the edge case, but by then the person is gone. I've even contacted some people by email to let them know their hand now works, but I get the frustration on their end.

What I'm working on:
Better error messages so people understand why it failed instead of just seeing "parsing error"
A dashboard where you can see all your hands, filter them, sort them, and soon analyze them with GTO. It's experimental right now but I'm actively improving it daily. I'd love for you to check it out and tell me if the filtering/navigation features there work for you, or if you think they should be in the replayer itself.

Privacy:
Not interested in monetizing or selling hand data. Private flag is on by default. Unless someone has the link, no one sees your hands. If you want even more protection (only visible to owner), I can do that too, but it complicates sharing.

Features you mentioned that already exist:
Anonymize toggle: Top right header > Settings. You can anonymize players, show chips in BB, show known hole cards, etc.
Database: Already built. Log in and you can access your hands from any device. (Log in is required for this)

Testing help:
Your point about stress-testing is huge. If you (or anyone reading this) have a good collection of hands with nasty edge cases (multiway with dead blinds, complex side pots, fast-fold formats, whatever usually breaks tools), I'd love to get them. Catching these edge cases proactively would be way better than discovering them when someone tries to upload and bounces.

Filters & navigation:
I'm building out the dashboard filtering now (show me all 3-bet pots, river check-raises, etc.). Try it and let me know if it's what you had in mind or if you'd rather see this directly in the replayer. If you have other feature ideas, I'm happy to implement them.

If you want to continue this conversation or have more feedback as you use it, feel free to reach out directly at [email protected].

Seriously, this kind of detailed input is incredibly valuable.

Thanks again for the thoughtful reply.