Every serious chess player ends up with the same thing eventually: a drawer, a binder, or a shoebox stuffed with paper scoresheets. Tournament games, club nights, that one brilliant attack you still think about years later. Those sheets are your chess history, and right now most of it is sitting in a format that fades, tears, and gets lost in a move.
The plan below has four parts: get each game off the paper and into PGN, save it somewhere it can be searched, name it so it can be found again, and keep enough copies that no single accident can take it.
Why Your Scoresheets Are Worth Saving
Scoresheets aren't just paper records. They're two things at once:
- Study material. Your own games are the best source of improvement you have. Every loss is a lesson, and you can only learn from a game you can still find.
- Memories. The draw against a stronger opponent, your first tournament win, a club rivalry that ran for years. These are the moments that made you a chess player.
The problem is that paper is a fragile medium for something this valuable.
The Problem With a Shoebox of Paper
A box of loose scoresheets feels like an archive, but it fails in every practical way. Pencil smudges, ink bleeds, and cheap tournament paper yellows within a few years. One house move, one flood, or one overenthusiastic spring cleaning, and decades of games are gone. Nothing in the box is searchable: finding every game you played against a particular opening means flipping through 300 sheets by hand. And a paper scoresheet cannot be replayed; it will not step through moves, flip the board, or feed a game into an engine.
The fix isn't a bigger box. It's digitizing.
A Workflow for Digitizing Old Scoresheets
The goal is to get every game out of its paper prison and into PGN, the standard chess game format that any chess software can read. (If PGN is new to you, here's what PGN is and why it matters.)
Here's a workflow that scales from ten scoresheets to ten thousand.
1. Photograph each scoresheet and get the moves into PGN
You don't need a flatbed scanner. A phone photo is enough, as long as the sheet is flat, evenly lit and sharp. Either type the moves into a PGN editor from the photo, or upload the photo to a scanner that reads the handwriting for you and checks each move for legality, so a misread entry is flagged before it goes into the archive. Replay the game once before you file it; that is the moment to catch a wrong move, not a year later. Converting a handwritten scoresheet to PGN compares the two routes.
2. Keep the original photo and the PGN together
Store the photo of the sheet next to the PGN it produced. The photo is your ground truth if a move ever looks wrong, and it is also the copy of the original you get to keep when the paper sheet belongs to the organizer. If you scan with an account-based tool, the game history it keeps is a first cloud copy, but do not treat it as the only one.
3. Export and route the PGN where you want it
Once a game is PGN, it's portable. Common destinations:
- A personal game database in ChessBase or SCID, where you can search by opponent, opening, result, or date.
- Lichess Studies, which are free, shareable, and great for annotating club games or coaching material.
- A plain cloud folder (Google Drive, Dropbox, iCloud) full of
.pgnfiles, if you prefer simplicity over database features.
You don't have to pick just one. Export the PGN once and drop a copy in each place that matters to you.
Naming and Organizing Conventions
A thousand files named game.pgn is just a digital shoebox. A little discipline up front makes the archive usable for life. A reliable convention:
YYYY-MM-DD_event_opponent
For example: 2026-04-12_SpringOpen_Petrosian.pgn. Why this order:
- Date first (YYYY-MM-DD) so files sort chronologically on their own.
- Event to group tournament and club games.
- Opponent so you can scan a folder and find a specific matchup at a glance.
Mirror that structure in folders too: a top-level year, then a subfolder per event. Fill in PGN tags (Event, Site, Date, White, Black, Result) while you're at it. Tagged games are what make a database genuinely searchable later, and they are what let you review your openings across a whole season at once, as described in analyze chess games from scoresheets.
Backing It Up
Digital files fail differently than paper, but they still fail. Follow the 3-2-1 rule:
- 3 copies of every game.
- 2 different media or services (for example, your computer plus a cloud drive).
- 1 copy off-site, so a single fire or theft can't take everything.
A scanner's account history counts as one of those copies if you used one. Pair it with a local database and a backup drive and your archive is genuinely safe. Keep the original paper too, at least for a while, if it is yours to keep: it's your ground truth if you ever need to double-check a transcription.
What Clubs and Organizers Can Do
Event scoresheets are a record of the club's history, and under the FIDE Laws they belong to the organizer in the first place, which is why they end up in a filing cabinet at the club rather than in the players' bags. Instead of letting that paper rot there:
- Digitize the whole event so every round becomes a PGN bundle you can publish or archive.
- Share games with members through Lichess Studies or a downloadable PGN pack after the tournament.
- Build a club archive that shows your strongest games, historical rivalries, and progress over the years.
- Settle disputes with a clean, validated record instead of squinting at smudged handwriting.
For clubs handling a whole event's worth of paper, tournament scoresheet archiving lays out the batch workflow.
Start With One Stack
Don't try to digitize everything in a weekend. Grab the stack closest to you, photograph the first scoresheet, and file the PGN using the naming convention above. Once one game is preserved, the rest of the box stops feeling like a chore and starts feeling like reclaiming your chess history.
The scanning step is the one ScanChess does: a photo of the sheet comes back as a PGN with every move checked, and the scan stays in your account history as a first backup copy.