PGN Analysis: How to Analyze Your Games From a PGN File

Disclosure: this guide was written by the team behind Chess DNA, the free AI chess-analysis app you'll see recommended below. About us

By Yuval Incze · Published Jul 5, 2026 · Updated Jul 5, 2026 · ~6 min read

A PGN is the plain-text file that stores your chess games. To analyze one, upload it to a free engine like Lichess, a desktop program, or a tool that reads your whole batch at once.

TL;DR A PGN holds 100% of a game — every move, plus the players, result, and date — as plain text. You can export a PGN from Chess.com or Lichess in a few clicks, then feed it to a free engine for move-by-move analysis. Analyzing one game shows what went wrong that day; analyzing your last 25–50 games together shows the mistake pattern that actually costs you rating. Both matter, but the batch is where real improvement hides. Players have used computer analysis to study their games for over 30 years.

What is a PGN file?

PGN stands for Portable Game Notation. It is the standard plain-text format for storing a chess game — the moves in algebraic notation, plus tags for the players, event, date, result, and often the time control and each player's rating. Because it is just text, a PGN opens in any editor and imports into any chess program. One file can hold a single game or thousands stacked one after another.

A minimal PGN looks like this: a block of bracketed tags, then the moves — 1. e4 e5 2. Nf3 Nc6 3. Bb5 and so on, ending with the result. The tags at the top matter more than they look. The rating and time-control tags, for instance, let an analysis tool know whether a mistake happened in a blitz scramble or a slow game, which changes how much weight to give it. If you want the full breakdown of the format and its tags, see our PGN glossary entry. PGN is different from FEN, which describes a single frozen position rather than a whole game — you would use a FEN to share one tricky spot, and a PGN to share the game that led to it.

The practical point: every move you have ever played is recoverable as a PGN, which means every game is analyzable. Nothing is lost — you just need to get the file out of the site you played on. And because the format is universal, a PGN exported from one site analyzes perfectly well on another, so you are never locked into a single platform's tools.

How to export a PGN from Chess.com and Lichess

Both major sites let you download your games as PGN, and both make it easy — the exact menu wording shifts over time, so look for the intent rather than a specific button.

The result is a .pgn file on your computer. That single file is now portable — you can open it in any engine or analysis tool, keep it as a backup, or feed it to something that reads all the games together. If the download gives you many games in one file, that is not a problem to fix; it is exactly what you want for batch analysis, covered below.

One tip: name the file something you will recognize later — the date range, or the time control — because once you have a habit of reviewing, you will accumulate several of these and a folder of games.pgn, games(1).pgn, games(2).pgn gets confusing fast.

Where to analyze a PGN for free

Once you have the file, several free routes give you a real engine going over every move:

For a fuller walk-through of turning a raw game into useful takeaways, read how to analyze your chess games.

Why analyzing 25–50 games beats one at a time

Analyzing a single game answers one question: what went wrong that day. That is useful for the immediate loss, but it is a sample size of one. The mistake that actually holds your rating down rarely shows up as a single dramatic blunder — it shows up as the same kind of error, repeated across many games.

Batch analysis is where that becomes visible. Feed 25–50 recent PGNs into one engine pass and the pattern jumps out: you keep losing material in the middlegame, or you keep drifting in equal endgames, or your openings are fine but you crack under time pressure. No single game tells you that. Twenty-five do.

This is the gap that neither platform's game-by-game review closes on its own, and it is exactly what cross-game tooling is for. See how to find your chess weaknesses for the method, and a purpose-built chess analysis app for doing it without exporting anything.

What to look for across your games

When you review a batch, sort your mistakes by phase rather than by game. Ask which phase of the game leaks the most, then attack that first.

PhaseRepeated-mistake signal to watch for
OpeningFalling behind in development, walking into the same trap, or leaving the opening already worse.
MiddlegameHanging pieces, missing two-move tactics, or making plans that ignore the opponent's threat.
EndgameMisplaying won or drawn king-and-pawn endings, or converting an advantage too slowly.
TimeBlunder rate spiking in the last few minutes — a clock problem, not a chess problem.

Whichever row lights up most across your batch is your training priority. Fixing the phase that leaks most often is worth more than polishing the phase you already play well.

One more thing to track: the type of mistake, not just the phase. Are you hanging pieces to a threat you did not see, or are you seeing the threat and miscalculating the response? The first is an awareness problem — solved by a blunder-check habit. The second is a calculation problem — solved by slower, more careful puzzles. A batch review that separates the two tells you which drill to actually do, instead of guessing.

Common PGN problems and how to avoid them

A few snags come up often enough to be worth naming, so you do not lose time on them:

None of these are hard, but they are the friction that stops people from reviewing at all. Removing the friction — auto-import, batch handling, a clear view of your own mistakes — is the whole reason a dedicated tool exists rather than juggling files by hand.

Frequently Asked Questions

What is a PGN file in chess?

A PGN — Portable Game Notation — is the standard plain-text file that stores a chess game: every move in algebraic notation, plus tags for the players, date, result, and usually the time control. Because it is just text, it opens in any editor and imports into any engine or analysis tool. One PGN file can hold a single game or thousands stacked together, which is why it is the format sites use when you export your history.

How do I analyze a PGN file for free?

The simplest free route is Lichess's import page: paste or upload the PGN and it runs server-side computer analysis, flagging inaccuracies, mistakes, and blunders with no cost and no cap. For local control, free desktop programs like SCID or Arena load a PGN and run Stockfish on your own machine. And some apps auto-import your games as PGN so you skip the export step entirely.

How do I export my games as a PGN?

On Chess.com, open a finished game and choose the PGN download from the share or download menu; the archive view of your games offers a bulk download for many at once. On Lichess, use a game's export option, or the games export on your profile to pull your whole history into one file. Either way you end up with a .pgn file you can open in any engine.

Is it better to analyze one game or many games at once?

Both have a place, but they answer different questions. One game tells you what went wrong that day. Analyzing your last 25–50 games together reveals the mistake pattern — the same kind of error repeated across games — that actually costs you rating. A single dramatic blunder is a sample of one; a recurring weakness only shows up in the batch, which is why cross-game analysis is where real improvement hides.

Can I open a PGN file without a chess site?

Yes. A PGN is plain text, so it opens in any text editor to read the raw moves. To actually replay and analyze it with a board and engine, load it into a free desktop program like SCID or Arena, or import it into Lichess in a browser. You do not need the original site you played on — the file is fully portable.

Analyze your games free →

Related guides

About the author

Yuval Incze is the founder of Chess DNA and a long-time competitive chess player. He built Chess DNA to automate the diagnostic loop — game analysis, pattern detection, weakness ranking — so players study the specific things costing them rating instead of generic advice.