Abstract file-rank board fragment with one umber file column and one sand rank row on ash paper.
File-rank mark: one olive file and one sand rank meet on a selected square for a local chess client install. Rank Timber original file-rank geometry for factory-chess (not a PyChess logo).

A local chess client and an online platform are not the same product. Cluster page: vs online platforms.

Local wins

Named GitHub assets, offline play after download, PGN on disk, engines you attach, GPL-3.0 source. PyChess is the mapped client.

Website wins

Live pools, ratings, studies, and paid extras. Chess.com and Lichess stay better at that job. This guide does not funnel a signup.

Arena and GNOME Chess

Arena still wins some Windows engine rooms. GNOME Chess is a simpler GNOME board. Cute Chess is strong for engine tournaments. Longer Arena notes: vs Arena.

Switch: switch from online platforms. Home table: home. Files: PGN and engines.

Rank Timber publishes the comparison so searchers who want a desktop board can tell a desktop MSI from a website. Upstream remains at pychess.github.io.

Club policy should name which path owns rated games and which path owns analysis. Mixing those jobs on an adware download page is how labs lose an afternoon. Safe door: download safe.

Two jobs, two doors

Rated blitz on a website is one job. A GTK board with files on disk is another. Search ads collapse those jobs into one “download” button. Keep them separate.

PyChess answers the desktop job with a named MSI and .deb. Chess.com and Lichess answer the website job on their own domains. Arena answers a Windows engine-room job.

If install rights are missing, a browser board still wins. If the network is gone, a local client still wins. If you need both, keep both and write the policy down.

This comparison is not a ranking of who has more users. It is a map of install doors. Safe desktop door: download safe. Cluster: vs online platforms.

Rank Timber publishes the map. Upstream remains at pychess.github.io. Club charts should name the official GUI for demos so a substitute does not add a third program from a portal.

Related: vs Arena, switch from online platforms, home.

Desk policy without the website job

A classroom can document the GTK window as the analysis tool and leave rated play in the browser. Write that sentence on the wall chart so a substitute does not add a third installer from a search ad. The chart should name the GitHub org, the MSI or .deb filename class, and the PGN folder.

Backups and travel kits

Shared laptops need a backup of the PGN folder before every reimage. Browser bookmarks survive more often than local packages. After the image lands, install PyChess from Releases again, then open one saved PGN to prove the files still replay.

Coaches who want Hint Mode should attach one documented engine binary, not a zip sitting in Downloads. Hint arrows that point at nothing make the window look broken even when the client is fine.

Travel bags should carry the already-installed client. Offline trains are the whole reason a local board exists. Website studies can wait until the hotel network returns.

Rank Timber maps filenames and habits. Upstream remains GPL-3.0 at pychess/pychess. Keep portal wrappers out of the lab. First hour: installed. Safe door: download safe. GitHub: GitHub.

One official window

If two volunteers disagree about GUIs, pick one official window for demos and let the other stay optional. Arena can remain for engine rooms. PyChess can remain for mixed Windows and Linux tags. Cute Chess can remain for tournaments. The failure mode is three unofficial copies and no ticket.

After policy exists, stop hunting new download pages. Return to the same Releases URL for the next bump. That boring rhythm is the product.

What a map is for

A comparison page exists so a volunteer can point at one GUI and one website without arguing in the hallway. The GUI owns files and engines. The website owns live ratings if the room still wants them. Write those two sentences and stop adding products.

When a portal collapses both jobs into one setup.exe, the lab spends the afternoon uninstalling toolbars. Named GitHub assets prevent that afternoon. PyChess is the mapped GTK door. Arena remains available for engine rooms that already standardized on it.

Teachers can demo from the GTK window even when the filter blocks game websites. That is a practical reason to keep a local client, not a slogan. After the demo, students can still use the website at home if policy allows.

Rank Timber will not rank platforms by user count. Upstream remains at pychess.github.io. Keep the Releases URL on the ticket. Keep the PGN folder off the package tree. Keep the engine binary on a documented path.

Prove the GTK window before you add engines, servers, or a second installer. The proof is the gate.

  • One named GitHub asset
  • One local game
  • One PGN folder on the ticket

Frequently asked questions

Should I drop online chess sites after installing PyChess?

Only if local files and engines are the whole job. Websites still win at live ratings. Many desks keep a website bookmark and a GTK client. This guide maps the desktop install, not a campaign to close accounts.

Is PyChess a Chess.com or Lichess clone?

No. PyChess is a desktop GTK client with engines, variants, and optional FICS or ICC. Chess.com and Lichess are websites. They solve different jobs. Comparison cluster: vs online platforms on the cluster page.

Where should I download the chess client?

Prefer GitHub Releases for pychess/pychess when you want named chess assets. Take pychess-*-mingw_x86_64_msvcrt_gnu.msi on Windows or python3-pychess_*.deb on Linux. Keep Softonic-style mirrors out of the loop. Document the update door on the machine ticket so the next bump stays honest for shared desks.