Can You Castle if Your Rook Is Attacked?

Yes, you may castle while the rook is attacked if every other castling condition is satisfied. The king must not start in check, cross an attacked square, or finish in check, and the king and rook must retain castling rights. Run the Attacked h1 Rook case to watch the threatened rook relocate legally.

Castling safety restrictions protect the king rather than the rook's starting square. An attack on the rook does not attack the king's route unless the same enemy piece also controls one of the king's three tested squares. Compare the Attacked h1 Rook and f1 Transit Square cases in the Rook Attack Castling Trainer.

No, only a king can be in check. A rook may be attacked or en prise, but that fact alone does not make castling illegal. Open the Attacked h1 Rook case to distinguish an attacked rook from the checked king case.

No, an attack by itself does not remove castling rights. Castling rights are lost when the king moves, when the eligible rook moves, or when that rook is no longer available on its required square. Use the Castling Rights Lost case to compare an attack with an actual loss of rights.

Yes, castling may move an attacked rook to safety when the king's route is legal and all other conditions hold. The rook moves as part of the king's castling move rather than making a separate escape move. Play the Attacked h1 Rook demonstration to watch the rook move from h1 to f1.

Yes, White may castle kingside with an attacked h1 rook if e1, f1, and g1 are safe and castling rights remain. The attacker's piece type does not change that king-safety test. Try the rook, bishop, and knight attack cases in the Rook Attack Castling Trainer.

Yes, White may castle queenside with an attacked a1 rook if e1, d1, and c1 are safe, the path is clear, and castling rights remain. The rook's attacked starting square is not one of the king-safety squares. Run the Attacked a1 Rook case to watch O-O-O remain legal.

Yes, the same rule applies to Black. For kingside castling Black's king route is e8-f8-g8, while queenside uses e8-d8-c8; an attack confined to h8 or a8 does not prohibit the move. Apply the Three-Square King Test shown above the trainer with the board colours reversed.

No, a rook attacked by a queen, rook, bishop, knight, pawn, or king is not automatically barred from castling. What matters is whether that attack or another attack reaches the king's start, transit, or destination square. Compare the Bishop Attacks Rook and Knight Attacks Rook cases.

Yes, a bishop may attack the corner rook without making castling illegal. The bishop's line must still be checked against the king's route after the complete castling move. Run the Bishop Attacks Rook case to see White castle while h1 is attacked from e4.

Yes, a knight attack on the corner rook does not by itself prevent castling. Knight attacks must be tested separately against the king's start, transit, and destination squares. Run the Knight Attacks Rook case to see the h1 attack coexist with legal O-O.

Yes, a pawn attack on the rook is allowed when the king's route remains safe. Pawn attack directions matter only if they also cover a square the king occupies or crosses. Apply the Three-Square King Test before treating the rook attack as relevant.

Yes, a queen may attack the rook's starting square without automatically stopping castling. Because a queen controls long files, ranks, and diagonals, its line must also be checked for attacks on the king's route and final position. Use the Attacked h1 Rook case as the basic legal pattern, then compare the three illegal king-square cases.

No, a king may not castle from an attacked starting square. An attacked rook does not matter, but a checked king on e1 or e8 immediately makes castling illegal. Reveal the King Starts in Check case to see the e-file attack that overrides the rook condition.

No, the king may not cross an attacked transit square even when castling would save the rook. For White's kingside castle, an attack on f1 makes O-O illegal. Compare the Attacked h1 Rook and f1 Transit Square cases.

No, the king may not finish castling on an attacked destination square. For White's kingside castle, g1 must be safe regardless of the rook's condition. Run the g1 Destination Square case to see why the final king square decides legality.

For White, the king-safety squares are e1, f1, and g1; for Black they are e8, f8, and g8. The rook's h-file starting square is not part of this attacked-square test. Use the Three-Square King Test cards to inspect each stage.

For White, the king-safety squares are e1, d1, and c1; for Black they are e8, d8, and c8. The rook's a-file starting square and the b-file square are not king-safety squares, although the path between king and rook must be empty. Run the Attacked a1 Rook case to apply the queenside test.

Yes, an attacked square crossed only by the rook does not prohibit castling. In orthodox queenside castling, b1 or b8 may be attacked because the king never occupies that square, although it must be empty. Use the Attacked a1 Rook case and the Three-Square King Test to separate rook travel from king safety.

Yes, b1 may be attacked while White castles queenside because the king travels from e1 through d1 to c1. The b1 square must be empty, but it does not have to be safe from enemy attack. Trace the king's red e1-c1 arrow in the Attacked a1 Rook demonstration.

In orthodox castling the rook lands on f1 or d1 for White, squares the king crosses during O-O or O-O-O. Therefore an attack on the rook's destination also makes castling illegal because the king must cross that attacked square, not because the rook would be attacked there. Compare the f1 Transit Square case with the legal rook-start attack cases.

No, a rook that moved loses its castling eligibility even if it returns to the original corner and is later attacked. The board may look correct, but the missing castling right remains decisive. Run the Castling Rights Lost case to see the same pieces with O-O unavailable.

No, moving the king permanently removes both castling rights for that side. Returning the king to e1 or e8 does not restore them, regardless of whether a rook is attacked. Use the Castling Rights Lost case to practise checking history as well as geometry.

No, every square between the king and the castling rook must be empty. An attacked rook does not waive this clearance requirement. Reveal the Blocked Path case to see a bishop on f1 prevent kingside castling.

No, castling requires the eligible rook to be present on its castling corner. A missing rook cannot be replaced by an empty-square castle. Compare the required pieces in the Attacked h1 Rook board with the checklist under Castling Rights and Path.

No, a promoted rook does not gain castling rights, even if it reaches a1, h1, a8, or h8. Castling is tied to the original eligible king and rook that have not moved. Use the Castling Rights Lost case to remember that appearance alone does not establish the right.

No, another rook cannot inherit the original rook's castling right. A promoted rook or the rook from the opposite corner remains ineligible for that lost right. Review the Castling Rights and Path checklist before testing attacked squares.

No, castling never captures a piece. The king and rook move to their castled squares, and any enemy attacker remains unless the new position attacks it normally. Play the legal demonstrations to watch both friendly pieces relocate without a capture.

The board may be detecting a hidden attack on the king's start, transit, or destination square, a blocked path, or lost castling rights. The visible rook attack is often a distraction from one of those actual restrictions. Work through all nine Rook Attack Castling Trainer cases to identify the failing condition.

Confirm that the king and correct rook have never moved, the path is empty, the king is not in check, and every square the king crosses or occupies is safe. Then ignore attacks confined to the rook's starting square. Use the Castling Rights and Path checklist followed by the Three-Square King Test.