Disclaimer
I'm a designer who has always been curious about data and storytelling. I also love baseball. When I discovered scorekeeping, something clicked. The way a scorecard captures a game on a single sheet of paper, with symbols and numbers to help tell the story with data, felt like the perfect intersection between my love for design and data.
Before you go filling in your scorebook based on what you see here, there are a few things you should know.
Where the data comes from
Everything on this site, the lineups, pitch sequences, play by play, boxscores, standings, all of it, comes from the MLB Stats API. You might hear it called the GUMBO feed. It's the same data that powers MLB's own apps, and it's free to use.
The wOBA calculations use published linear weights from FanGraphs. These weights shift a little each year depending on the run environment across the league. The values currently in the code are from the 2025 season.
Weather icons are from Erik Flowers' Weather Icons project, and the math formulas on the Guide page use MathJax to render properly. Both are loaded from CDNs.
Not affiliated with MLB
BaseballScorecard.org has nothing to do with Major League Baseball, any MLB team, or MLB Advanced Media. Same goes for FanGraphs and every other source mentioned here. This is a fan project, built by one guy with a little help from Claude Code, for no reason other than the joy of it. There's nothing to buy and nothing to sign up for. I make this purely out of a love for the game and for telling its stories through data, and that's reward enough. All trademarks belong to their respective owners.
The scorecards might be wrong
The site is still in the early innings. There are 80+ play event types in the MLB API, and new edge cases crawl out of the woodwork every game.
The scorecards are generated automatically from raw API data. Sometimes a play gets parsed wrong, or a substitution renders in a way that looks off. It's hilarious how it breaks sometimes. But I'm working on it.
Please double check what you see here before committing pen to paper, and keep some white-out nearby.
If something looks wrong, send a message through the contact page. Those reports are how the site gets better.
Analytics
I use Simple Analytics to see how many people visit and which pages they look at. That's it. Simple Analytics doesn't use cookies, doesn't collect personal data, and doesn't track you across pages. No fingerprinting, nothing sold to anyone. I just want to know which parts of the site people actually use so I can focus my time there.