Software · head to head
libGDX vs DragonBones
The short version
- Each has a real cost: libGDX libGDX is a Java framework built on OpenGL ES, so projects are tied to the JVM toolchain; DragonBones javaScript/TypeScript runtime limited to specific game engines (Egret, PixiJS, Phaser, Hilo, Cocos Creator)
- They diverge on capability: libGDX covers Java language support, DragonBones covers Skeletal animation.
Where they differ
Only the attributes on which libGDX and DragonBones actually diverge.
| Attribute | libGDX | DragonBones |
|---|---|---|
| Pricing model | free | open-source |
| Platforms | Windows, Macos, Linux, Ios, Android, Web | Egret, PixiJS, Phaser, Hilo, Cocos Creator |
| Founded | 2010 | 2014 |
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Unknown).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in libGDX
- Java language support
- Graphics rendering
- Audio engine
- Input handling
- Physics integration (Box2D)
- Particle effects
- Animation system
- 2D and 3D rendering
Only in DragonBones
- Skeletal animation
- Mesh deformation
- IK system
- Texture atlas
- Animation blending
- Bone constraints
- FFD
- Multi-resolution
Both cover
- Local deployment
- Windows support
- Macos support
What people use each for
The jobs each tool is most often brought in to do.
libGDX
- Writing 2D or 3D games in Java from a single codebasenot DragonBones
- Publishing a Java game to desktop, Android, iOS and HTML5not DragonBones
- Rapid prototyping where an opinionated engine workflow is unwantednot DragonBones
DragonBones
- 2D skeletal animation for JavaScript and TypeScript game enginesnot libGDX
- Cross-engine animation library for indie game developmentnot libGDX
- Animation creation with LoongBones editornot libGDX
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
libGDX
- libGDX is a Java framework built on OpenGL ES, so projects are tied to the JVM toolchain
- Publishing targets are limited to Windows, macOS, Linux including Raspberry Pi, Android, iOS and HTML5
- libGDX is a community-maintained Apache 2.0 project with no vendor and no paid support tier
- libGDX ships as a framework rather than an editor, so there is no visual scene editor included
DragonBones
- JavaScript/TypeScript runtime limited to specific game engines (Egret, PixiJS, Phaser, Hilo, Cocos Creator)
Pricing, plan by plan
libGDX
Free- FreeFree
- Full framework
- Java support
- Cross-platform
DragonBones
FreeNo published plan breakdown. See the DragonBones review.
Which should you pick?
Choose libGDX if
- You need java language support.
- You want to start without paying.
- You work on Windows, Macos, Linux, Ios, Android, Web.
- You also want graphics rendering.
Choose DragonBones if
- You need skeletal animation.
- You want to start without paying.
- You work on Egret, PixiJS, Phaser, Hilo, Cocos Creator.
- You also want mesh deformation.
Questions people ask
- Is libGDX or DragonBones better?
- Neither clearly leads. libGDX starts at Free and DragonBones at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, libGDX or DragonBones?
- libGDX starts at Free and DragonBones at Free.
- Does libGDX or DragonBones run on more platforms?
- libGDX runs on Windows, Macos, Linux, Ios, Android, Web. DragonBones runs on Egret, PixiJS, Phaser, Hilo, Cocos Creator.
- Can I use libGDX for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is libGDX best used for?
- libGDX is most often used for writing 2d or 3d games in java from a single codebase, publishing a java game to desktop, android, ios and html5, rapid prototyping where an opinionated engine workflow is unwanted. Of those, writing 2d or 3d games in java from a single codebase and publishing a java game to desktop, android, ios and html5 are not what DragonBones is typically brought in for.
- What can libGDX do that DragonBones cannot?
- libGDX covers Java language support, Graphics rendering, Audio engine, Input handling. DragonBones covers Skeletal animation, Mesh deformation, IK system, Texture atlas. Both handle Local deployment, Windows support, Macos support.
Related pages
More on DragonBones
Keep looking
Other head to heads
- libGDX vs Unity
- libGDX vs Aseprite
- libGDX vs Godot Engine
- libGDX vs Cascadeur
- libGDX vs Construct 3
- libGDX vs GameMaker Studio 2
- libGDX vs Mixamo
- libGDX vs Pico-8
- libGDX vs Substance 3D Painter
- libGDX vs Adventure Game Studio
- libGDX vs AppGameKit
- libGDX vs Armory3D
- libGDX vs Bevy
- libGDX vs Buildbox
- libGDX vs Clickteam Fusion
- libGDX vs Cocos2d-x
- libGDX vs CryEngine
- libGDX vs Defold
- DragonBones vs Unity
- DragonBones vs Aseprite
- DragonBones vs Godot Engine
- DragonBones vs Cascadeur
- DragonBones vs Construct 3
- DragonBones vs GameMaker Studio 2
- DragonBones vs Mixamo
- DragonBones vs Pico-8
- DragonBones vs Substance 3D Painter
- DragonBones vs Adventure Game Studio
- DragonBones vs AppGameKit
- DragonBones vs Armory3D
- DragonBones vs Bevy
- DragonBones vs Buildbox
- DragonBones vs Clickteam Fusion
- DragonBones vs Cocos2d-x
- DragonBones vs CryEngine
- DragonBones vs Defold

