HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
official-stockfish
Stockfish
C++2016–2026
official-stockfish / Stockfish

Stockfish

A free and strong UCI chess engine

39Distinct people
45Mentions
1Explicit recommenders
17.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A free and strong UCI chess engine

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I recommend anyone who's interested in this topic, or in data structures and optimisation, to pick apart Stockfish' transposition table implementation[0,1]. It's essentially a…

mtlmtlmtlmtl used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:57:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year45 dated mentions

Observed mentions: 2016-11-12 18:05:22 UTC to 2026-09-16 15:28:55 UTC.

02468102016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC303
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC404
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC514
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC1019
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC606
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC321
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC615

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Stockfish A free and strong UCI chess engine. Explore Stockfish docs » Report bug · Open a discussion · Discord · Blog Overview Stockfish is a free and strong UCI chess engine derived from Glaurung 2.1 that analyzes chess positions and computes the optimal moves. Stockfish does not include a graphical user interface (GUI) that is required to display a chessboard and to make it easy to input moves. These GUIs are developed independently from Stockfish and are available online. Read the documentation for your GUI of choice for information about how to use Stockfish with it. See also the Stockfish documentation for further usage help. Files This distribution of Stockfish consists of the following files: README.md, the file you are currently reading. Copying.txt, a text file containing the GNU General Public License version 3. AUTHORS, a text file with the list of authors for the project. src, a subdirectory containing the full source code, including a Makefile that can be used to compile Stockfish on Unix-like systems. a file with the .nnue extension, storing the neural network for the NNUE evaluation. Binary distributions will have this file embedded. Contributing See Contributing Guide. Donating hardware Improving Stockfish requires a massive amount of testing. You can donate your hardware resources by installing the Fishtest Worker and viewing the current tests on Fishtest. Improving the code In the chessprogramming wiki, many techniques used in Stockfish are explained with a lot of background information. The section on Stockfish describes many features and techniques used by Stockfish. However, it is generic rather than focused on Stockfish's precise implementation. The engine testing is done on Fishtest. If you want to help improve Stockfish, please read this guideline first, where the basics of Stockfish development are explained. Discussions about Stockfish take place these days mainly in the Stockfish Discord server. This is also the best place to ask questions about the codebase and how to improve it. Compiling Stockfish Stockfish has support for 32 or 64-bit CPUs, certain hardware instructions, big-endian machines such as Power PC, and other platforms. On Unix-like systems, it should be easy to compile Stockfish directly from the source code with the included Makefile in the folder src. In general, it is recommended to run make help to see a list of make targets with corresponding descriptions. An example suitable for most Intel and AMD chips: cd src make -j profile-build Detailed compilation instructions for all platforms can be found in our documentation. Our wiki also has information about the UCI commands supported by Stockfish. Terms of use Stockfish is free and distributed under the GNU General Public License version 3 (GPL v3). Essentially, this means you are free to do almost exactly what you want with the program, including distributing it among your friends, making it available for download from your website, selling it (either by itself or as part of some bigger software package), or using it as the starting point for a software project of your own. The only real limitation is that whenever you distribute Stockfish in some way, you MUST always include the license and the full source code (or a pointer to where the source code can be found) to generate the exact binary you are distributing. If you make any changes to the source code, these changes must also be made available under GPL v3. Acknowledgements Stockfish uses neural networks trained on data provided by the Leela Chess Zero project, which is made available under the Open Database License (ODbL).
Read the full README on GitHub

What Hacker News says

10 sources
No. Magic Bitboards are what you use if you don't have PEXT available. EDIT: I expect the WASM version to use magic-bitboards (which is just a "magical" multiply instruction + a lookup). Every single sliding piece (ie: Rooks, Bishops, and Queens) use PEXT (or magic-bitboards if the PEXT code is unavailable) to determine where to go. Its a fundamental calculation to determine very, very quickly which moves are legal or not. Both PEXT and Magic Bitboards are incredible techniques for solving the sliding-piece question. However, PEXT is much much much faster, but relies upon an obscure x86-only assembly instruction (that is slower on AMD Zen or Zen2 unfortunately. So you still need to know your hardware details, Intel machines should use the PEXT version). --------- Still, even AMD users want the BMI2 version, which has a bunch of bit-operat
Read the rest
ions that can be optimized that are used all the time. (And besides, AMD Zen3 is actually faster on PEXT now, so PEXT is looking good for the future) ----- In either case, I have my doubts that the NNUE neural-net runs anywhere near as good on WASM than on the hand-optimized SIMD / AVX kernels that the Stockfish team wrote. Even if there's some auto-vectorization that WASM can do, its really hard to beat handcrafted assembly / intrinsics (https://github.com/official-stockfish/Stockfish/blob/master/...)
In Chess.com vs. Lichess
> Note that it’s legal to sell stockfish as long as you’re compliant with GPLv3. ChessBase seems to be compliant. Unless your license has been terminated by the copyright holders, in which case you cannot be compliant with the license because don't have a license to distribute the material at all. > Stockfish argues that ChessBase isn’t compliant because they refuse to release the weights. I haven't seen them argue this anywhere. You've linked to their previous statement in which they only say that they "condemn" the fact that the weights are not being released. The announcement says that they've filed the lawsuit "to enforce the consequences of the license termination" because "ChessBase is ignoring the fact that they no longer have the right to distribute Stockfish, modified or unmodified, as part of their products." > But GPLv3 doesn’t
Read the rest
give you the ability to terminate a license arbitrarily; it requires you meet some specific criteria, and it’s unclear that ChessBase meets it. You seem to be talking about this paragraph in the GPLv3 (https://github.com/official-stockfish/Stockfish/blob/sf_14/C...) : "Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice." However, this is not ChessBase's first violation. They've also tried to pass off Houdini as original work: https://shop.chessbase.com/en/products/houdini_6_pro_multipr... Houdini 6 is also a stockfish clone. https://chess.stackexchange.com/questions/29181/is-houdini-6...
In Our lawsuit against ChessBase
> 1. ChessBase was in violation of the GPL, but then cured the violation by releasing code (https://stockfishchess.org/blog/2021/statement-on-fat-fritz-...). But the post claims they refused to release the weights. They mean that the weights are not open sourced. If the weights are distributed separately and not considered part of the "Corresponding Source", that may not be a GPL violation, and the blog post does not imply that it is. (They only say that they condemn the approach.) > 2. But the weights are already being released with the program they're selling. Otherwise, how would the program run? Why would they refuse, when they already distribute the weights with every copy of the program? I thought maybe Fat Fritz 2 was a cloud-hosted solution (weights aren't provided locally), but https://en.chessbase.com/post/running-leela-and-fat-
Read the rest
fritz-on... seems to indicate it can run on a laptop with a GPU. The GPL can be interpreted to require that all the input necessary to reproduce and run a functioning binary must be distributed. If the weights and engine are integrated in one binary, and not "all the source code needed to generate, install, and run the object code and to modify the work, including scripts to control those activities" is provided, that could be a GPL violation. This does not apply if the weights are distributed separately under a different license. > I'm on Stockfish's side here, because I suspect ChessBase simply duplicated StockFish's training methodology and tried to pass it off as their own. (The engine's performance seems almost identical.) But I hope Stockfish has an airtight case for court. It'd be a bad idea to hinge the GPL violation on "they refused to release the neural net weight training code." They may have terminated the license in response to the Houdini revelations[1] which is another chess engine based on Stockfish that Chessbase has sold as original work, disguising its Stockfish origins in violation of the GPL. As the GPLv3 says under Section 8 [2] the license can be reinstated if "this is the first time you have received notice of violation of this License (for any work) from that copyright holder" - the first violation would have been Fat Fritz 2. [1] https://groups.google.com/g/fishcooking/c/DygaIdBvJm0 [2] https://github.com/official-stockfish/Stockfish/blob/sf_14/C...
In Our lawsuit against ChessBase
The Stockfish mentality is: not everybody owns a GPU and Stockfish should be available for everybody and perform well [1]. So they went for a CPU micro-arch optimized neural net, which is great. Maybe this is ultimately not the best for tournaments. What I would find interesting is if they could give engines an energy budget instead of a time limit. Maybe that makes CPU vs GPU games more interesting & fair. [1] https://github.com/official-stockfish/Stockfish/issues/2823
In The neural network of the Stockfish chess engine

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.