Lichess vs Chess.com for Academies: Platform Pick

Most Lichess vs Chess.com articles answer a different question: which site is nicer for an individual player. That debate is saturated and mostly a matter of taste. An academy's question is narrower and more consequential: which platform should every student in the academy play on, so that coaches can retrieve games, run engine analysis, track ratings, and build homework from one consistent source? Standardizing matters because a coaching workflow built on synced games breaks down when half the batch plays on one site and half on the other, under usernames nobody recorded.

So the criteria change. An individual player cares about interface polish, puzzle variety, and who their friends play on. An academy cares about programmatic access to games, the cost of putting forty students on the platform, how cleanly PGN files come out, whether eight-year-olds can use it safely, and whether the club tools support batch-level organization. This comparison scores both platforms on those academy criteria only. If you want the player-side debate, this is not that article.

Standardize on Lichess if your priority is a clean coaching data pipeline: its API is open and free, every game exports as PGN without a paid plan, and the kid mode covers child safety for school-age students [1]. Standardize on Chess.com if your priority is very young children inside the ChessKid environment, or if your students and their families are already invested in Chess.com's content and community [2]. Most academies we have seen land on Lichess as the system of record and tolerate Chess.com as a secondary source.

The verdict pattern that holds up in practice: Lichess is better for API access, cost, and openness; Chess.com is better for the kids ecosystem and content; and a dual-platform setup is workable as long as one platform is named the system of record. The sections below walk through each criterion, because the table compresses real trade-offs that deserve a paragraph each.

Game syncing differs sharply: Lichess offers a free, open API that can export any user's complete game history in PGN format, while Chess.com offers a read-only public API limited to published data [1][2]. For a coach, this is the single most important difference between the platforms, because everything downstream of syncing, from engine analysis to homework to progress reports, depends on getting the games out reliably.

On Lichess, the export endpoints are documented, free, and do not require the student to hold any paid account [1]. A coach or a tool acting for the coach can request a student's games filtered by date, time control, or opponent, and receive standard PGN, the universal text format for recording chess games. PGN matters because it is portable: the same file opens in any analysis interface, feeds any engine, and archives cleanly. The Lichess API also supports streaming formats for tools that process games continuously, and the documentation states its rate limits plainly, so a workflow built on it behaves predictably from week to week.

On Chess.com, students can download their own games as PGN from the site, and the public API exposes published game archives for reading [2][3]. That is genuinely useful, and read-only import from Chess.com is a perfectly viable secondary pipeline. The friction is directional: the access model is built around reading what the platform has published rather than around third parties operating on a user's behalf, so coaching tools generally treat Chess.com as an import source rather than a fully integrated platform. In day-to-day terms, Lichess sync tends to be first-class and automatic, while Chess.com retrieval is periodic import.

What does this mean for your weekly routine? If your review loop is manual, either platform works: ask students for PGN files and load them into your analysis tool of choice. If your review loop is automated, the gap widens. An automated pipeline wants to wake up on Monday, pull every student's weekend games, queue them for Stockfish analysis, and flag the ones worth a coach's attention. Lichess was designed to allow exactly that [1]. With Chess.com you can approximate it through the published-data API, but you are working with the grain on one platform and against it on the other. Either way, insist that every student's username is recorded in your own records before the first lesson, because no API can recover games from an account nobody wrote down. Our pillar on engine analysis for chess coaching covers what to do with the games once you have them.

Both platforms take child safety seriously, but they solve it differently: Lichess builds a kid mode into the main site, while the Chess.com family runs ChessKid, an entirely separate platform for children [4]. Which approach fits depends on the age band you teach.

Lichess kid mode is an account setting that disables communication features, so a child can play and train without chat or messages. The strength of this approach is continuity: the student plays on the same platform, with the same games and the same rating history, from age eight to eighteen, and the coach's syncing workflow never changes. The limitation is that the surrounding site is the adult site; kid mode restricts communication, not the general environment.

ChessKid takes the opposite approach: a separate world designed for children, with restricted communication, adult oversight, and lessons built for young learners [4]. For an academy with a strong under-10 intake, that purpose-built environment is a real advantage and the reason many academies put their youngest group there even if older students play elsewhere. The trade-off is a migration: when a student outgrows ChessKid and moves to Chess.com or Lichess, their history starts over, and your records need to bridge the two identities.

Lichess costs an academy nothing: it is free and open-source software run as a nonprofit, funded by donations, and all play, analysis, and study features are available without payment [5]. There is no premium tier to evaluate because there is no premium tier. For an academy of forty students, the platform bill is zero, and the API access that powers a syncing workflow is also free [1].

Chess.com runs a freemium model. Free accounts can play rated games and use a limited slice of the training features; paid memberships remove the limits on puzzles, lessons, and game reviews [3]. For an academy, the question is not whether one membership is good value, it is who pays at scale: if your curriculum leans on Chess.com's lessons or unlimited reviews, either the academy subsidizes memberships or each family buys one, and either way it is a recurring line item that Lichess simply does not have. If your curriculum only needs students to play games that you then analyze with your own tools, free Chess.com accounts are sufficient and the cost difference shrinks to zero.

The honest framing for a budget meeting: Lichess is free at any scale; Chess.com is free if you only need the games, and a per-student subscription if you want its training content. Neither platform charges for the thing an academy needs most, which is rated games that can be exported and reviewed.

Both platforms use rating systems from the Glicko family, designed by Mark Glickman: Lichess uses Glicko-2 and Chess.com uses a Glicko-based system [5][6]. Glicko systems track not just a rating but also a rating deviation, a measure of how uncertain the number is, which is why a new account's rating swings wildly for its first games and then settles.

Two consequences matter for academies. First, the numbers are not comparable across platforms: a 1500 on Lichess and a 1500 on Chess.com are produced by different systems against different player pools, so never put them side by side in a progress report as if they were the same scale. Second, neither number is a FIDE rating. Online ratings are useful trend lines for coaching decisions, but the official over-the-board rating a parent may eventually care about comes from federation-rated tournaments, not from either website. Saying this to parents early, in plain words, prevents a predictable misunderstanding later; our guide on showing parents rating progress has the full script.

Yes, and many academies do, because students arrive with existing accounts and habits that are not worth fighting. The dual-platform setup fails only when nobody decides which platform is the system of record. Decide that, and the rest is bookkeeping.

1. 1Name one platform the system of record, usually Lichess for its open API and free export [1], and run all rating tracking and weekly review from it.
2. 2Record every student's username on both platforms in your student records, against written parent consent for minors.
3. 3Ask students to play their serious rated games, especially slow games, on the system of record.
4. 4Import games from the secondary platform on a fixed schedule, for example monthly, as PGN [2].
5. 5Report one rating trend line to parents, labeled by platform, and treat the secondary platform's rating as background information only.

This setup gives you the best of each: the open pipeline and zero cost of Lichess, plus whatever a family already values on the Chess.com side, including ChessKid for younger siblings [4]. What it costs you is discipline about usernames and one import routine. The follow-up question, what to actually do with the synced games each week, is the subject of our 15-minute game review method and our guide to building chess homework from games.