← Back to app
About

WHY WE
BUILT THIS

The short version: a drawer full of scoresheets I never looked at again.

ChessDiary started as a problem I had, not a business plan. I'm a student and a club-level tournament player, and for years my chess record lived in three places that never talked to each other.

Every over-the-board game I played left a paper scoresheet behind. I'd fold it up, drop it in my bag after the round, and — almost without fail — never open it again. By the end of a season I had a shoebox of handwritten notation I couldn't be bothered to transcribe, covering losses I knew I should study but never did. Meanwhile my online games were somewhere else entirely: blitz and rapid on Chess.com, correspondence games on Lichess, each platform holding its own slice of my history with no way to see all of it side by side.

The actual losing pattern was hiding in plain sight across all three of those places at once, and I had no way to see it. I'd blunder the same type of tactic in a paper tournament game in March and again in a Lichess game in June, and never connect the two, because nothing put them in front of me together.

I didn't need another chess app. I needed one place that already had all my games — paper, Chess.com, and Lichess — and told me what I kept getting wrong.

So I built that. ChessDiary reads a photo of a handwritten scoresheet with Gemini AI and turns it into a clean move list. It pulls your existing history straight from the Chess.com and Lichess public APIs with one-time account linking, no manual PGN exports. And every game, regardless of where it came from, gets run through Stockfish — the same engine used at the top level of the game — so the blunders, mistakes, and inaccuracies are flagged with real centipawn numbers, not a guess.

WHAT CHESSDIARY IS NOT TRYING TO BE

It's not trying to replace Chess.com or Lichess as a place to actually play. It's not a coaching platform with a human on the other end. It's the layer underneath all of that — the diary part — that collects everything you've already played and makes the patterns visible, whether the game happened on a board with a pencil or on a phone screen at midnight.

WHERE IT STANDS TODAY

ChessDiary is free to use on Web and in closed beta on Android, built from a single codebase for both. It's ad-supported rather than subscription-based, which is also why you'll see a privacy policy that's honest about Google AdSense and AdMob rather than pretending they're not there. If you've read this far, you probably have the same shoebox-of-scoresheets problem I did — the guides are a good place to start, or jump straight into a real example analysis report to see what the engine actually flags in a full game.


HOW THE GUIDES ARE CHECKED

The guides explain chess ideas and how ChessDiary works. Where a guide shows a board position, the diagram is generated from the exact position described in its caption, the move lines are checked for legality, and tactical claims (a forced mate, a winning capture, a drawn ending) are only published once the Stockfish engine agrees with them. The explanations are editorial writing; the engine is used as a fact-checker, not as a ghostwriter.

The sample analysis pages are a separate thing: they show what ChessDiary's analysis looks like on famous public-domain games, with the engine's numbers shown rather than hidden, including the moves where the famous players went wrong.

HOW CHESSDIARY USES AI AND ENGINES

Two different tools do two different jobs. Gemini AI reads a photo, PDF or screenshot of a game and turns it into a move list, which you review before it is saved. Stockfish, a chess engine, calculates the evaluation behind every flagged move. If the Stockfish server cannot be reached, ChessDiary falls back to Gemini for the analysis rather than failing, and the guide on that fallback spells out what changes.

CORRECTIONS

If you find an error in a guide or a diagram, a wrong move, a claim you disagree with, a broken link, please tell us and include the page address. Corrections are made to the page itself.


THE AUTHOR

V
Venugopal Ramamoorthy
Builder, ChessDiary

Student and club-level tournament chess player. Built ChessDiary to solve his own problem — scattered scoresheets and online games with no single place to see the patterns across them — and kept building once it turned out other players had the exact same drawer full of paper.

Questions, feedback, or just want to say the shoebox-of-scoresheets thing resonated? Get in touch.