https://ironwoodchess.com/blog/Recent content in Journal on Ironwood ChessHugoen-usTue, 22 Sep 2026 00:00:00 -0500https://ironwoodchess.com/blog/private-analysis-portable-results/Tue, 22 Sep 2026 00:00:00 -0500https://ironwoodchess.com/blog/private-analysis-portable-results/<p>Ironwood&rsquo;s analysis workspace now follows a game from import to review without moving the game to a server. Stockfish 19 evaluates each position in its dedicated browser Worker, the board remains available for navigation while analysis runs, and the resulting timeline can be saved in formats intended for different jobs.</p> <h2 id="one-analysis-three-forms">One analysis, three forms</h2> <p>The versioned Ironwood JSON format is the lossless archive. It records the position timeline, evaluation, mate score, depth, node count, best move, principal variation, engine configuration, and summary measurements. Re-importing it restores the analysis immediately rather than asking Stockfish to calculate the game again.</p>https://ironwoodchess.com/blog/stockfish-in-your-browser/Mon, 21 Sep 2026 00:00:00 -0500https://ironwoodchess.com/blog/stockfish-in-your-browser/<p>Ironwood Chess began with a demanding premise: the browser version should not quietly substitute a cut-down chess engine or send positions to a server. The game should run a serious engine locally, preserve the complete NNUE evaluation network, and keep the board responsive while Stockfish calculates.</p> <p>That requires more than compiling an engine to WebAssembly. Stockfish runs behind a dedicated Worker boundary so search never occupies the browser&rsquo;s rendering thread. <code>SharedArrayBuffer</code> and <code>Atomics</code> provide the primitives its pthread build needs for parallel evaluation, while cross-origin isolation headers make those capabilities available safely.</p>