Cocos2d is one of the most successful open-source engine families in mobile gaming — and one of the most confusingly named, because “Cocos2d” has referred to several different frameworks, branches, and generations depending on the year and the language you mean. This page untangles the family: the original Python framework, the Objective-C iPhone branch, the C++ Cocos2d-x branch that made the engine famous, and Cocos Creator, the rewritten modern engine that has quietly replaced all of them.
It also corrects the record. Earlier versions of this article listed FarmVille as a flagship Cocos2d game — it was not; FarmVille was an Adobe Flash / ActionScript title and never touched Cocos2d. And the article predated the single most important fact about the engine today: Cocos2d-x, the C++ branch this page is nominally about, was deprecated after its final 4.0 release in 2019, and active development moved to Cocos Creator 3.x, a from-scratch engine that no longer uses the Cocos2d-x codebase at all. What follows is the verified version history, the genuinely Cocos-built games, the current state in 2026, and how the engine compares to Unity and Godot for 2D work.
Table of Contents
- What Is Cocos2d?
- The Cocos2d Family, Untangled
- History: From a Village Named Los Cocos to Cocos Creator
- Cocos2d-x Is Deprecated — Here's What Replaced It
- Languages and Platforms
- Games Built with Cocos2d
- How Cocos Compares to Unity and Godot for 2D
- Key Takeaways
- Frequently Asked Questions
- Conclusion
What Is Cocos2d?
Cocos2d is a family of open-source game engines built around 2D sprite-and-scene rendering, first created in Python in 2008 by Ricardo Quesada. Its most influential branch, Cocos2d-x (C++, 2010, MIT-licensed), powered a generation of mobile hits before development ceased in 2019; the maintained successor is Cocos Creator, a rewritten (also MIT-licensed) engine whose 3.8 long-term-support line reached version 3.8.8 in December 2025. Cocos has particularly strong adoption in China’s mobile and mini-game ecosystem.
The Cocos2d Family, Untangled
The naming is the single biggest source of confusion, so here is the whole tree in one place. The sprite is the shared foundation across every version — a 2D image that can be positioned, scaled, rotated, animated, and nested inside other sprites, with sprites grouped into scenes that act as game levels or screens.
- Cocos2d (Python, 2008) — the original, created by Ricardo Quesada and collaborators. Still exists as a Python framework but is not the commercial branch.
- Cocos2d for iPhone / Cocos2d-ObjC (Objective-C, 2008) — the first branch, built for the new App Store. Later renamed Cocos2d-Swift; development effectively ended in the mid-2010s.
- Cocos2d-x (C++, 2010) — the cross-platform branch created by Zhe Wang, MIT-licensed, that made Cocos famous. One C++ codebase compiling to iOS, Android, Windows, macOS and more. This is the influential C++ branch that became the dominant Cocos2d generation of the 2010s — and the one whose development has now ceased.
- Cocos2d-HTML5 / Cocos2d-JS — the JavaScript branch for web, later folded into the Cocos-JS lineage.
- Cocos Creator (2018 onward) — an editor-driven engine, originally on the Cocos2d-x core (2.x), then completely rewritten for 3.x (2021) as a new 2D-and-3D engine — native C++ core, JavaScript runtime for web builds, TypeScript scripting. This is the maintained product today.
Older sibling names still floating around the web — Cocos2d-XNA, Cocos2d-Android (Java), Cocos.Net (C#), Cocos2d-windows — were community or platform-specific ports, most long since inactive.
History: From a Village Named Los Cocos to Cocos Creator
The engine was born in February 2008 in the Argentine village of Los Cocos, where Ricardo Quesada and Lucio Torre built a 2D game framework in Python with a few collaborators and named it after the village. Version 0.1 shipped under the name Cocos2d.
Seeing the potential of Apple’s new App Store, Quesada ported the framework to Objective-C and released Cocos2d for iPhone in June 2008 — the first branch of the family and the one that seeded a wave of early iOS games. In November 2010, Chinese programmer Zhe Wang created Cocos2d-x, re-implementing the ideas in C++ for true cross-platform compilation from a single codebase. Cocos2d-x was the breakout: MIT-licensed, free, and able to target every major mobile and desktop platform, it became one of the dominant 2D mobile engines of the 2010s, especially across China and the wider Asian market.
The stewardship story is messier. Cocos2d-x and Cocos2d-HTML5 were maintained and sponsored by Chukong Technologies, whose team also built the CocoStudio editor toolkit. Quesada joined the Cocos2d-x team in 2013 after leaving the iPhone project, and was laid off from Chukong in March 2017. CocoStudio was retired in 2016 and replaced by Cocos Creator, and the company (now simply “Cocos”) pivoted the entire product line toward Creator — first on the Cocos2d-x core, then, from 2021’s 3.x, onto a wholly new engine. That rewrite is why Cocos today is best understood as descended from Cocos2d-x rather than being it.
Cocos2d-x Is Deprecated — Here’s What Replaced It
This is the fact the old version of this page was missing, and it changes how you should approach the engine. Cocos2d-x shipped its final major release, version 4.0, in late 2019 (its headline feature was Metal support for iOS/macOS). After that, official development of the C++ branch ceased — the repository was archived (its URL literally carries a “deprecated” label), and Cocos redirected all development to Cocos Creator. Community forks exist to keep 3.x-era projects building on modern toolchains, but there is no first-party Cocos2d-x development anymore.
What replaced it is Cocos Creator 3.x, and it is genuinely a different engine, not a renamed Cocos2d-x. Per Cocos’s own documentation, 3.x “completely abandons the Cocos2d-x base,” adopting a new high-performance cross-platform core; it is explicitly no longer considered a direct extension of Cocos2d-x. Architecturally it splits the work by target: native builds run on a C++ engine core, while web and mini-game builds use a JavaScript-based runtime, with gameplay scripted in TypeScript in both cases. It does both 2D and 3D. The line is actively maintained — 3.8 is the current long-term-support (LTS) branch, and its latest release, 3.8.8, landed in December 2025, with the GitHub repository pull requests in active flow.
So if you’re evaluating “Cocos” for a new project in 2026, the real choice is Cocos Creator, and this page’s original framing — Cocos2d-x as the thing to build with — is a decade out of date.
Languages and Platforms
The family spans several languages by branch: Python (original), Objective-C (iPhone branch), C++ (Cocos2d-x, and still the language of Cocos Creator’s native engine layer today — though Creator 3.x is a fresh C++ codebase, not the Cocos2d-x one), JavaScript/TypeScript (web branches and Creator’s scripting layer), plus older C# and Java ports. In current Cocos Creator, developers primarily write gameplay in TypeScript, over that native C++ layer.
Platform support in Cocos Creator 3.x is broad: iOS, Android, Windows, macOS, HTML5/web, and a wide range of “mini-game” platforms (WeChat, ByteDance and other in-app game runtimes that are a major reason for Cocos’s strength in the Chinese market). Cocos2d-x historically also reached platforms like Windows Phone and Tizen that have since faded.
Games Built with Cocos2d
Here the old page needs the most correction, because its headline example was simply wrong. The verified list:
- Geometry Dash (2013) — the rhythm-platformer by Robert “RobTop” Topala is the cleanest confirmation on the list; Topala has stated directly that he used Cocos2d-x. It is probably the single most famous Cocos2d-x game.
- Plague Inc. (2012) — Ndemic Creations’ mobile strategy game was built on Cocos2d-x, and Cocos’s own site lists Ndemic among its developers. Important distinction: the later PC/console remake Plague Inc: Evolved (2015) runs on Unity, not Cocos — the original page blurred the two together.
- Badland, Clash of Kings, and many others across the 2010s mobile market used Cocos2d-x; the engine’s strength was exactly this high-volume 2D mobile category.
Correction — FarmVille was never a Cocos2d game. Earlier versions of this article listed FarmVille (Zynga, 2009) as a flagship Cocos2d title. It was not: FarmVille was an Adobe Flash / ActionScript 3 browser game that ran via Flash until Flash’s 2020 shutdown, and has no connection to Cocos2d. The misattribution likely crept in from a scraped “popular mobile games” list; it is removed here.
How Cocos Compares to Unity and Godot for 2D
For a 2D mobile project in 2026, Cocos Creator sits in a specific niche against the two obvious alternatives. Against Unity, Cocos is built around lightweight deployments — an advantage on mobile, and effectively a requirement on mini-game platforms where package size is tightly constrained — and is free and open-source with no licensing fees or revenue thresholds — where Unity carries a more substantial runtime and tooling stack for small 2D projects, is closed-source, and is commercially licensed, but has a vastly larger ecosystem, asset store, and hiring pool. Against Godot, the comparison is closer: both are free, open-source, MIT-ish/permissive, lightweight, and strong at 2D. Godot has broader Western community momentum, its own GDScript plus C#, and a more unified 2D/3D editor; Cocos has deeper roots and tooling for the Asian mobile and mini-game market and a mature C++ native core. The honest summary: Godot when an open ecosystem and its unified 2D/3D editor are the priority, Cocos Creator when you’re shipping to WeChat/ByteDance mini-games or the lightweight mobile targets it’s purpose-built for, and Unity when ecosystem size and hiring outweigh a heavier stack.
Key Takeaways
- “Cocos2d” is a family, not one engine — Python original (2008), Objective-C iPhone branch, the famous C++ Cocos2d-x (2010), JS/web branches, and modern Cocos Creator.
- Cocos2d-x development has ceased. Its last major release was 4.0 in 2019; the C++ branch was archived (commonly described as deprecated) and development moved entirely to Cocos Creator.
- Cocos Creator 3.x is a rewritten engine — it explicitly abandoned the Cocos2d-x base in 2021, runs a C++ native engine with a JavaScript web runtime and TypeScript scripting, does 2D and 3D, and remains the maintained line (3.8 LTS; v3.8.8, December 2025).
- Geometry Dash and the original mobile Plague Inc. are verified Cocos2d-x games; Plague Inc: Evolved is Unity, a distinction the old page missed.
- FarmVille was never a Cocos2d game — it was an Adobe Flash / ActionScript title; the old attribution is corrected.
- For new 2D work: Cocos Creator for mini-game and lightweight mobile targets, Godot when an open ecosystem and unified editor matter most, Unity when ecosystem size and hiring win.
Frequently Asked Questions
Conclusion
Cocos2d’s real story is a generational handoff most write-ups miss: a Python experiment from a small Argentine village became, through its C++ Cocos2d-x branch, one of the defining 2D mobile engines of the 2010s — and then the company retired that branch and rebuilt the whole thing as Cocos Creator. The engine that made Geometry Dash and the original Plague Inc. is not the engine you’d start a new game with today, and understanding that distinction is the difference between current knowledge and a decade-old snapshot.
For where Cocos fits among the broader C++ engine landscape — and the many alternatives, from Godot to the heavyweight 3D engines — see the best C++ game engines directory.
