FEN — Forsyth-Edwards Notation — is the standard one-line text format for describing a single chess position: where every piece stands, whose turn it is, and the small handful of invisible facts (castling rights, en passant, move counters) needed to continue the game correctly. A FEN string is a snapshot, not a story — it captures one moment on the board with no memory of how the game got there. Every chess engine, server, and database uses FEN under the hood, and being able to read one by eye is a surprisingly practical skill for any player who studies with a computer.
What Is FEN?
The name honors two people separated by a century. David Forsyth, a Scottish-born journalist, invented the core idea in the 1800s so that newspapers could print positions compactly. Steven J. Edwards extended it in the 1990s for computer use — adding the fields machines need that a newspaper reader could infer — and that extended version is what we all use today.
A FEN is a single line of text with six fields separated by spaces. Here is the starting position of chess:
rnbqkbnr/pppppppp/8/8/8/8/PPPPPPPP/RNBQKBNR w KQkq - 0 1
Reading left to right: the piece placement, the side to move (w), the castling rights (KQkq), the en passant target square (- for none), the halfmove clock (0), and the fullmove number (1). Six fields, six questions answered — and together they contain almost everything about the state of a game, a qualification we will return to, because the "almost" is where the interesting subtleties live.
Why should a human learn to read this? Because FEN is how positions travel. When a student sends me "can you look at this?", it arrives as a FEN. When you set up a custom position in any analysis tool, the tool is building a FEN. When a book position needs checking with an engine, you type its FEN. It is the postal address of a chess position.
Field 1: Piece Placement
The first field is the longest and describes the chessboard rank by rank, from rank 8 down to rank 1 — that is, from Black's side of the board to White's, the same direction you read a printed diagram. A slash / separates each rank from the next.
Within a rank, you read from the a-file to the h-file. Letters are pieces: K king, Q queen, R rook, B bishop, N knight, P pawn. Uppercase means White, lowercase means Black — N is a white knight, n a black one. Digits count consecutive empty squares: 3 means three empty squares in a row, and a completely empty rank is 8.
So the fragment r1bqkbnr says: black rook, one empty square, black bishop, black queen, black king, black bishop, black knight, black rook — rank 8 after Black has developed a knight from b8. And 8/8/8/8 in the middle of the starting FEN is simply the four empty central ranks.
Two habits make you fluent quickly. First, find the kings: scan for K and k, and you immediately know the geography of the position. Second, check the digits: the numbers in each rank must sum with the letters to exactly eight squares, which is also the first thing to verify when a FEN refuses to load. If you are still getting comfortable with files, ranks, and square names, our guide on how to set up a chess board covers the coordinate system from zero.
Field 2: Whose Move Is It?
The second field is a single letter: w if White is to move, b if Black. It looks trivial, and it is the field beginners most often get wrong when composing positions by hand — with dramatic consequences. Whole branches of endgame theory hinge on whose turn it is: the same king-and-pawn position can be a win with one side to move and a draw with the other, which is the entire subject of the opposition and zugzwang. When an engine gives you a bizarre evaluation for a position you typed in, check this field before anything else. In my experience helping students debug their analysis, "wrong side to move" explains half of all mysterious evaluations.
Fields 3 and 4: Castling Rights and the En Passant Target
The third field records which castling moves are still legally available in the future: K means White can still castle kingside, Q White queenside, k and q the same for Black. KQkq means all four rights survive; a dash - means nobody can ever castle again.
The key subtlety: this field is about rights, not possibilities. A right disappears permanently when the king moves or the relevant rook moves (or is captured) — but it is not affected by temporary obstacles. If White's king and h1-rook have never moved, the FEN says K even if castling is momentarily illegal because a bishop sits on f1 or an enemy piece attacks a transit square. The right endures; only the immediate execution is postponed. This is precisely the information you cannot see by looking at the board — a position with king on e1 and rook on h1 might or might not allow O-O, depending on the game's history — which is why FEN must record it explicitly. Our castling article covers the movement rules themselves, including the conditions that block the move temporarily versus forever.
The fourth field exists for exactly one rule: en passant. If the previous move was a pawn advancing two squares, this field names the square behind that pawn — the square where an enemy pawn would land by capturing en passant. After 1. e4, the field reads e3. If the last move was not a double pawn push, the field is a dash -.
Like castling rights, this is history the board cannot show. Imagine a white pawn on e5 and a black pawn on d5, side by side. May White play exd6 en passant? From the diagram alone, it is impossible to know — everything depends on whether ...d7-d5 was played on the previous move. The FEN answers definitively: d6 in field four means yes, - means no. When you set up a position mid-game by hand, this is the field almost everyone forgets, and once in a while it matters enormously — there are studies and even practical games where the only winning or drawing move is an en passant capture.
Fields 5 and 6: The Move Counters
The halfmove clock (field five) counts halfmoves — single moves by one side — since the last capture or pawn move. Its sole purpose is the 50-move rule: when this counter reaches 100 halfmoves (fifty full moves by each side with no capture and no pawn move), a draw can be claimed. Engines read this field to know how close a defensive fortress is to salvation, and endgame tools use it when a theoretical win needs more moves than the rule allows.
The fullmove number (field six) is the number that would appear in the game score: it starts at 1 and increases by one after each of Black's moves. It has no effect on legality or evaluation — it is bookkeeping, useful when you convert a position back into a numbered game continuation.
A complete example. After 1. e4 c5 2. Nf3, the position is:
rnbqkbnr/pp1ppppp/8/2p5/4P3/5N2/PPPP1PPP/RNBQKB1R b KQkq - 1 2
Read it back: Black's queenside is intact except the c-pawn has gone to c5 (2p5 on rank 5); White has a pawn on e4 and a knight on f3; Black to move; all castling rights alive; no en passant square (Black's ...c7-c5 was two squares, but wait — it was a double push, yet no white pawn can capture on c6, and modern convention only records the square when a capture is actually possible; the classic standard would write c6); one halfmove since the last pawn move (Nf3); and we are in move 2. That little parenthesis is a real corner case: you will meet FENs written both ways, and good software accepts both.
What a FEN Cannot Tell You
FEN describes a position's present and just enough of its past to play on legally. But two rules of chess depend on deeper history that FEN deliberately omits.
The first is threefold repetition: a draw claim requires the same position to have occurred three times, and a single snapshot cannot know how many times it has appeared before. Two players could reach an identical FEN, one of them entitled to claim a draw and the other not.
The second is subtler: FEN cannot prove a position is reachable. You can write a syntactically perfect FEN of a position that no legal game could ever produce — say, with both kings adjacent, or nine pawns of one color. Software will usually load it anyway, and engines will analyze it happily. For composers and puzzle designers this freedom is a feature; for students checking their setup, it means the tool will not always catch your mistakes.
This is the honest division of labor between the two great chess formats: FEN stores where you are, a game record stores how you got there. A position snapshot is enough for tactics, endgame theory, and engine analysis; it is not enough to adjudicate repetition claims or reconstruct the narrative of a game. Knowing which tool answers which question is part of working efficiently with chess software.
FEN in Everyday Training
Let me give you the practical uses that come up constantly in my own work as a coach and author.
Sharing positions. A FEN pastes into any message. When my students and I discuss a critical moment, we trade FENs, not screenshots — the recipient can immediately analyze, not just look.
Reproducing book positions. When you study a classic manual and want to check a line — a Lucena position rook endgame, a Philidor defense — type the FEN into an engine and interrogate it. Ten seconds of typing converts a static diagram into a living training partner, and this is exactly how I verified hundreds of positions while writing my own books.
Debugging engine analysis. As noted above: when an evaluation makes no sense, read the FEN fields in order. Wrong side to move, phantom castling rights, and a missing en passant square are the three classic culprits, in that order of frequency.
Compact note-taking. During opening preparation I keep files where each critical position is one FEN plus one line of prose. It is the densest possible chess notebook — an entire middlegame tabiya in under eighty characters.
FEN and Your Training at ChessMind AI
Positions are the atoms of everything we build, so FEN is quietly everywhere on this site. The most direct experience of it is the board scanner: photograph a physical board or a diagram from a book, and the scanner reconstructs the position — producing, in effect, its FEN — so you can analyze it immediately instead of dragging pieces one by one. From there, the analysis board lets you explore any position with engine support, which is the modern version of the "type the book diagram into the engine" habit I described above. Every exercise in our tactics puzzles is served from a stored position snapshot, and the endgame trainer is built on exactly the kind of precise theoretical positions — often differing only in that second FEN field, whose turn it is — where these details decide the result. And if you want to strengthen the underlying skill of holding a position in your head, square by square, our visualization exercises drill precisely the board-picture fluency that makes reading a FEN by eye feel natural.
Frequently Asked Questions
What does FEN stand for?
Forsyth-Edwards Notation, after David Forsyth, the 19th-century journalist who invented the compact piece-placement scheme for newspapers, and Steven J. Edwards, who standardized the modern six-field computer version in the 1990s.
What are the six fields of a FEN string?
In order: piece placement (rank 8 to rank 1, uppercase for White, digits for empty squares), active color (w or b), castling rights (KQkq subsets or -), en passant target square (or -), the halfmove clock counting moves since the last capture or pawn move, and the fullmove number.
How is FEN different from PGN?
FEN records one position with no history; a game-record file records an entire game move by move. They are complementary: a game score can regenerate the FEN of any moment in the game, but a FEN alone can never regenerate the game. Use FEN when the position is the point, and a game record when the story matters.
Why does my engine give a weird evaluation for a position I set up?
Check the FEN fields in order of likely error: side to move first (w vs b — by far the most common mistake), then castling rights that should not exist (did that king really never move?), then a missing en passant square. Any one of these can turn a winning position into a lost one.
Can a FEN describe an illegal position?
Yes. FEN is syntax, not law — it will happily encode positions no legal game could reach, and most software loads them without complaint. This is useful for composed studies and teaching diagrams, but it means you, not the format, are responsible for the position making sense.