#pixels #2d #gpu #framebuffer


A tiny library providing a GPU-powered pixel frame buffer

10 releases (6 breaking)

0.6.0 Sep 2, 2021
0.5.0 Jul 17, 2021
0.4.0 Jun 18, 2021
0.2.0 Aug 21, 2020
0.0.2 Nov 4, 2019

#3 in Rendering

Download history 280/week @ 2021-05-29 575/week @ 2021-06-05 462/week @ 2021-06-12 317/week @ 2021-06-19 502/week @ 2021-06-26 455/week @ 2021-07-03 647/week @ 2021-07-10 458/week @ 2021-07-17 440/week @ 2021-07-24 822/week @ 2021-07-31 681/week @ 2021-08-07 579/week @ 2021-08-14 648/week @ 2021-08-21 400/week @ 2021-08-28 545/week @ 2021-09-04 544/week @ 2021-09-11

2,292 downloads per month
Used in less than 15 crates

MIT license

787 lines

Documentation CI Average time to resolve an issue Percentage of issues still open

Pixels Logo

A tiny hardware-accelerated pixel frame buffer. 🦀

But why?

Rapidly prototype a simple 2D game, pixel-based animations, software renderers, or an emulator for your favorite platform. Then add shaders to simulate a CRT or just to spice it up with some nice VFX.

pixels is more than just a library to push pixels to a screen, but less than a full framework. You're in charge of managing a window environment, event loop, and input handling.

MSRV Policy

The Minimum Supported Rust Version for pixels will always be made available in the MSRV.md file on GitHub.


  • Built on modern graphics APIs powered by wgpu: Vulkan, Metal, DirectX 12, OpenGL ES3.
    • DirectX 11, WebGL2, and WebGPU support are a work in progress.
  • Use your own custom shaders for special effects.
  • Hardware accelerated scaling on perfect pixel boundaries.
  • Supports non-square pixel aspect ratios. (WIP)



Cargo resolver

Starting with wgpu 0.10, the resolver version needs to be set in your Cargo.toml to avoid build errors:

resolver = "2"

Driver issues

The most common issue is having an outdated graphics driver installed on the host machine. pixels requests a low power (aka integrated) GPU by default. If the examples are not working for any reason, you may try setting the PIXELS_HIGH_PERF environment variable (the value does not matter, e.g. PIXELS_HIGH_PERF=1 is fine) to see if that addresses the issue on your host machine.

You should also try to keep your graphics drivers up-to-date, especially if you have an old Intel integrated GPU. Keep in mind that some drivers and GPUs are EOL and will not be supported.


You may want to use the RUST_LOG environment variable (see env_logger for full documentation) to gain additional insight while troubleshooting the examples. RUST_LOG=trace will spew all logs to stderr on debug builds:

$ RUST_LOG=trace cargo run --package minimal-winit

And also on release builds when default features are disabled:

$ RUST_LOG=trace cargo run --package minimal-winit --release --no-default-features

Comparison with minifb

The minifb crate shares some similarities with pixels; it also allows rapid prototyping of 2D games and emulators. But it requires the use of its own window/GUI management, event loop, and input handling. One of the disadvantages with the minifb approach is the lack of hardware acceleration (except on macOS, which uses Metal but is not configurable). An advantage is that it relies on fewer dependencies.


~140K SLoC