Chess960 castling: the one rule, and the moves that look illegal
Chess960 castling seems to have four rules. It has one. The king and rook finish on the same squares as in standard chess. Castling short, the king ends on g1 and the rook on f1. Castling long, the king ends on c1 and the rook on d1. Black uses g8/f8 and c8/d8. Only the squares they start on change.
Hold that and the rest follows, including the cases that make people call the arbiter. In 162 of the 960 starting positions you can castle on move one. In some positions the king does not move at all. In others the rook does not move at all. In one family the king travels to the right to castle queenside. None of those is an exception to the rule. They are all the rule.
What is the castling rule in Chess960?
Choose a side. Put the king on g1 and the rook on f1, or the king on c1 and the rook on d1. Both pieces arrive in a single move, from wherever they were standing, in either order, and one may pass over the other.
Which rook goes with which side is fixed by geometry, not by names. The rook to the king's right is the short rook and it castles to f1. The rook to the king's left is the long rook and it castles to d1. FIDE calls these h-side castling and a-side castling, because the words kingside and queenside stop meaning anything once the king can start on b1.
Why does the king start between the rooks?
Because otherwise there is no rule to apply. Castling is defined as a move between the king and one of two rooks, one on each side. Put both rooks to the king's left and short castling has no rook to use, and the king on g1 has nothing to travel toward.
So the shuffle is constrained: the king must have a rook to its left and a rook to its right. That single requirement is what keeps castling a legal move in every one of the 960 positions, and it is one of the three rules that make the count 960 rather than 5,040. The arithmetic is on the page about why there are 960 positions.
When is castling legal?
Three conditions, and they are the standard ones read carefully.
- Neither the king nor that rook has moved. Rights are tracked per rook. Moving the a-side rook costs you a-side castling and leaves h-side castling intact. Moving the king costs you both.
- Every square the king passes over, and every square the rook passes over, must be empty, except for the king and that rook. Count both paths from start to finish, inclusive of the finishing squares.
- The king may not start in check, pass through an attacked square, or land on one. Only the king's squares matter. The rook may cross an attacked square and it may land on one.
Which Chess960 castling moves look illegal?
Set up the position and try them. Every example below is a real starting position, named by its number, and the resulting back rank is written out. The position generator will put any of them on a board.
The king does not move
Position 96 is BBQNRNKR. The king starts on g1, its short rook on
h1, and a knight sits on f1. Move the knight, then castle short. The rook goes h1
to f1 and the king stays exactly where it was. The back rank reads
BBQNRRK1. You have castled. Both rights are now spent, and the king
has not touched another square.
BBQNR.KRBBQNRRK.It is also the position where an attack on f1 does not stop you. The only square the king has to be safe on is g1, which it is already standing on, so a black rook raking the f-file is irrelevant. The rook lands under fire and the move is legal.
The rook does not move
Position 15 is QNNRKRBB. The king starts on e1 with rooks on d1
and f1. Clear g1 and castle short. The king walks e1 to g1 and the rook stays on
f1. The back rank reads QNNR1RKB. Note what the king did on the way:
it stepped over f1, which its own rook occupies. Passing over the castling rook
is allowed. Passing over anything else is not.
QNNRKR.BQNNR.RKBThe king moves to the right to castle long
Position 709 is RKBBQNNR. Rook a1, king b1, bishops on c1 and d1.
Develop the bishops, then castle long. The king goes b1 to c1, one square to its
right, and the rook goes a1 to d1. The back rank reads 2KRQNNR.
Queenside castling has moved the king toward the h-file.
RK..QNNR..KRQNNRThe mirror of that cannot happen. The king never moves left to castle short, because the king can never start to the right of g1. There has to be a rook on its right, and h1 is the only square left.
The king and rook swap places
Position 3 is BQNNRKRB. King f1, short rook g1. Castle short: the
king goes to g1 and the rook goes to f1. Nothing else on the board has to move
first, so O-O is a legal first move for White, and the two pieces trade
squares.
BQNNRKRBBQNNRRKBThere are 90 positions where short castling is legal at move one and 72 where
long castling is, 162 in all. The long version wants a rook on c1 and the king on
d1, as in position 74, NNRKBBQR, where 1.O-O-O gives
NNKRBBQR. Roll the generator until one appears, then
play it against the engine.
How do you actually castle?
Over the board, move the king first and put it on its finishing square, then move the rook. That order makes the intention unambiguous, since a hand that reaches for the rook first can be read as playing a rook move. If you are in the case where the king finishes on its own square, lift the king, set it back down, and then move the rook, or say castling as you make the rook move.
Online, drag your king onto your own rook. Lichess and chess.com both take
that as the castling move, and it is unambiguous in a way that clicking a
destination square is not: the king's target may be occupied by another piece, or
the click may read as an ordinary one-square king move. Engines do the same
thing. In UCI, Chess960 castling is sent as the king capturing its own rook, so
e1h1 means castle short. The interface convention and the engine
protocol agree because they solve the same problem.
How is Chess960 castling written?
O-O and O-O-O, unchanged. Nothing about the notation moved.
In FEN, the castling field has to say more than it used to. KQkq
is shorthand for the outer rook on each side, which works only because everyone
agrees what it points at. Shredder-FEN names the rook's file instead, so the
standard array is written HAha, and position 3 above is
GEge, its rooks on e1 and g1. X-FEN keeps KQkq where
nothing is ambiguous and falls back to file letters where something is. Any
Chess960 engine reads both. The file letters are the safe form to write, because
they name a square rather than a convention, and after a promotion on the back
rank a convention is not always enough.
What do people get wrong?
Assuming the squares between the king and the rook must be clear. What must be clear is the two paths and the two destinations. Position 15 shows the difference: the king on e1 and its rook on f1 are adjacent, there is nothing whatever between them, and short castling is still illegal until g1 is empty.
Assuming the king moves two squares. It moves as far as it
needs to, which is anything from five squares to none. Position 959,
RKRNNQBB, has the king on b1 and its short rook on c1, and O-O
carries the king five files to g1.
Assuming the rook has to be safe. It does not. Only the king's path and its destination are tested for attack.
Assuming g1 is a safe square because it is g1. In standard chess the castled king sits behind three pawns with a knight on f3. In a shuffled position the pieces that would guard it may all be on the a-side, and short castling can leave the king on g1 with nothing near it. Look at the back rank before you castle toward it, not after.
The rest of the rules are ordinary chess, set out on the Chess960 rules page. The harder skill is seeing tactics on a back rank you have never met, which is what the puzzle trainer and the books are for.