Skip to main content

FAQ

Frequently asked questions

Quick answers about what PixiJS is, what it costs and how to get going.

The basics

What PixiJS is, and what it isn't.

What is PixiJS for?

Everything! PixiJS is a rendering library for rich, interactive graphics, cross-platform apps and games. You don't have to learn the WebGPU or WebGL APIs, or deal with browser and device compatibility. Killer performance makes your content better, and the clean API makes it faster to build.

Is PixiJS a game engine?

No. PixiJS is what we've come to think of as a "creation engine". At its core, PixiJS moves things around on screen as quickly and efficiently as possible. It just so happens that's brilliant for making games.

Why should I use PixiJS?

Because you care about speed. PixiJS's number one mantra has always been speed. We keep it as lean and fast as we can, while still offering as many useful features as possible.

Can PixiJS do 3D?

Yes. PixiJS 3D adds meshes, lights, PBR materials and glTF models to the same stage you use for 2D.

Getting started

Where to get it, and where to begin.

Is PixiJS free?

PixiJS is and always will be free and open source. Financial contributions let us build features faster and write more in-depth documentation. You can become a sponsor through Open Collective or GitHub Sponsors. It's a massive help, and it'll make you feel good about yourself. Win-win.

Where do I get it?

Install it from npm with npm install pixi.js, or start a new project with npm create pixi.js@latest. The source and every release are on GitHub, which is always the most up-to-date place to look.

How do I get started?

Right here! Read the guides, follow a tutorial or open one of the examples and start changing things.

The project

Who builds it, and how to help.

Who makes PixiJS?

PixiJS has three core developers, who work on it part-time:

The project also relies on an active community of contributors and sponsors. Because the maintainers are part-time, sponsorship gives us more time to improve PixiJS, fix bugs and write better documentation. Meet the team, or support the work through GitHub Sponsors or Open Collective.

I found a bug. What should I do?

Two things. Let us know by opening an issue on GitHub. Even better, if you know how to fix it, open a pull request! We're always keen to welcome new contributors.

Still have a question?

Ask the community. Someone has usually run into the same thing.