What Is an SGF Viewer and How Do You Use One to Study Go Games?

Updated

An SGF viewer is software that opens Smart Game Format (SGF) files — the standard file type for Go (Baduk/Weiqi) game records — and lets you step through the moves, follow variations, and read any comments attached to the game. You need one whenever you want to review a finished game, study a professional or AI game, or work through a commented problem collection. Kaya (kayago.app) is one example: a free, open-source Go app with SGF support, game tree navigation, and built-in KataGo AI analysis, available on desktop and web.

What SGF actually is

SGF is a plain-text format that stores a game as a tree rather than a flat list of moves. Each node holds one or more properties — the move played, a comment, a markup label, the player names, the result — and branches off the main line represent variations.

That tree structure is the whole point. A single SGF file can contain a main game plus dozens of alternative continuations, each with its own commentary, without needing separate files.

Core features to expect in an SGF viewer

Feature What it does Why it matters for study
Open/load SGF Reads a .sgf file from disk or a URL The basic entry point
Move navigation Forward/back one move, jump to start/end Lets you replay at your own pace
Game tree view Shows the branching structure visually You can see where variations split off
Variation switching Move between sibling branches Essential for commented pro games
Comments and markup Displays text notes, letters, and shapes on the board Where the actual teaching lives
AI analysis Runs an engine like KataGo on the current position Turns "what happened" into "what was better"

Not every viewer has all of these. A minimal viewer may only step through moves; a full study tool adds the tree, comments, and engine.

How to open and navigate a record

  1. Get an SGF file. Download one from a game server, a pro-game archive, or export your own finished game.
  2. Open it in the viewer. In a desktop app this is usually a file-open dialog; in a web app you typically upload or paste the file.
  3. Step through the moves. Use the forward/back controls to replay. The board updates one stone at a time.
  4. Check the tree panel. If the file has variations, the tree shows the main line and any branches. Clicking a branch jumps you onto it.
  5. Read the comments. When a node has a comment, it appears in a side panel — this is usually the reason the file exists.

Expected result: you can move freely between any two positions in the record and see exactly what the author wrote about each one.

Following variations in a commented game

This is where beginners get lost. A commented pro game often looks like this:

  • Main line: the moves actually played.
  • At key moments, the commentator adds a branch: "If Black had played here instead…" followed by several moves.
  • That branch may itself branch again.

To follow it, treat the tree as a map. Note which node you branched from, walk the variation to its end, then return to the branch point before continuing the main line. Most viewers mark the current node and let you jump back with a single click. If you lose your place, jump to the start and step forward — the tree structure stays intact.

Using AI analysis alongside the viewer

An SGF viewer with integrated engine support (Kaya uses KataGo) lets you do something a static record can't: ask what the engine thinks of each move.

A practical loop:

  1. Step to a move you didn't understand.
  2. Run the analysis on that position.
  3. Compare the engine's preferred move with the one played.
  4. Read the file's comment — does the human author agree with the engine, or explain why the game move was still reasonable?
  5. Step forward and repeat at the next turning point.

The value is in the disagreement. Where the engine and the commentator diverge, you've found something worth thinking about.

Practical tips for studying a collection

  • Keep files organized by theme, not just by date — "opening problems," "endgame," "games I lost" are more useful folders than a single dump.
  • Annotate your own games. Add comments to your own SGFs right after playing, while you still remember your reasoning. Future-you will thank present-you.
  • Don't analyze every move. Pick the 3–5 positions where the game actually turned. Engine-checking all 250 moves is exhausting and teaches less.
  • Revisit files. A commented game you read at 15 kyu reads differently at 10 kyu. The file doesn't change; you do.

Choosing a viewer

If you only need to replay moves and read comments, almost any SGF viewer will do. If you want to combine record study with engine review in one place, look for a viewer with built-in AI analysis — Kaya is free and open-source and covers SGF viewing, game tree navigation, and KataGo analysis on desktop and web. The right choice depends on whether your study is mostly reading (comments and variations) or mostly checking (engine evaluation), and whether you'd rather work in a browser or a desktop app.