wgpu
Hacker ApprovedRanked 2 of 14 graphics libraries by recommenders
Cross-platform Rust graphics library implementing the WebGPU API, valued for portable rendering. Main caveat: it's a lowest common denominator that can lag behind native DX or Vulkan.
Cross-platform Rust graphics library implementing the WebGPU API, valued for portable rendering. Main caveat: it's a lowest common denominator that can lag behind native DX or Vulkan.
36 people gave an opinion
- recommend it
- 27
- criticize it
- 9
- approval share
- 75%
Recommended in 11 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it carries the badge
- 27 people recommend itNeeds 10 or more, met.
- 3 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 11 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Cross-platform rendering across backends
“wgpu makes more sense when you like the WebGPU headspace but want to target other backends”
Comment from 14 Jan 2026 in “Show HN: AwsmRenderer, a browser-native WebGPU renderer in Rust” “There's some libraries like wgpu that can fill this gap in practice”
Comment from 18 Oct 2026 in “macOS 15.8.2 Breaks OpenGL” “WGPU for cross-platform rendering”
Comment from 5 Dec 2025 in “eXoSpace – Built Using Rust, Rapier, WGPU and EGUI” Easy to use and mature
“once you have your first working example, it's smooth sailing from there”
Comment from 28 Dec 2025 in “Learn computer graphics from scratch and for free” “I bring these up as they're easy-to-use and mature.”
Comment from 10 Sep 2026 in “Rust is tier-1 language at Microsoft” Actively maintained, updates in sync
“anecdotally they have been updating in reasonable sync”
Comment from 13 Feb 2026 in “Zed editor switching graphics lib from blade to wgpu” “WGPU is very actively maintained.”
Comment from 13 Feb 2026 in “Zed editor switching graphics lib from blade to wgpu” Good abstraction level, close to WebGPU
“The WGPU implementation of WebGPU has a C API, which also has C++ headers, and a native Rust API.”
Comment from 23 Jul 2026 in “Learn OpenGL, extensive tutorial resource for learning Modern OpenGL” “wgpu in Rust is an excellent middle ground, matching the abstraction level of WebGPU”
Comment from 22 Nov 2025 in “How I learned Vulkan and wrote a small game engine with it (2024)”
What people warn about
Each mark is one comment
Slower than native APIs
“The downside is that it's the lowest common denominator, so it always lags behind what you can do directly in DX or VK.”
Comment from 13 Feb 2026 in “Zed editor switching graphics lib from blade to wgpu” “it's hard for it to ever be as fast as the native APIs it calls for you”
Comment from 13 Feb 2026 in “Zed editor switching graphics lib from blade to wgpu” “WGPU is hard to ship and also equivalent speed or slower”
Comment from 19 Jul 2026 in “Transcribe.cpp” Complexity from supporting many backends
“wgpu has a lot of constraints and complexity imposed on it by all the backends it has to support”
Comment from 14 Feb 2026 in “Zed editor switching graphics lib from blade to wgpu” “it can't avoid the pain that comes with different backends”
Comment from 14 Jan 2026 in “Show HN: AwsmRenderer, a browser-native WebGPU renderer in Rust” “Portable code has way too many cases.”
Comment from 10 Jan 2026 in “Bindless Oriented Graphics Programming” Large dependency footprint
“A WebGPU implementation isn't exactly slim either, especially when all is needed is just a very small 3D API wrapper”
Comment from 13 Feb 2026 in “Zed editor switching graphics lib from blade to wgpu” “Current wgpu seems to have a floor around ~100mb that isn't there with other rendering backends”
Comment from 13 Feb 2026 in “Zed editor switching graphics lib from blade to wgpu” “the amount of code that's pulled into the project is massive”
Comment from 13 Feb 2026 in “Zed editor switching graphics lib from blade to wgpu”
Other graphics libraries people recommend
The four most recommended other graphics libraries, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Three.js | 49 | 11 | 82% | 12 | — | Approved |
| wgpuThis page | 27 | 9 | 75% | 11 | — | Approved |
| Skia | 14 | 5 | 74% | 8 | — | Approved |
| LVGL | 10 | 2 | 83% | 5 | — | Approved |
| Dawn WebGPU | 9 | 6 | 60% | 6 | — | — |
What people said
40 of the 44 comments that mention it, newest first. Each links to the original comment.
“WGPU is based on the (outdated) first cut of Vulkan, not the current model”
“There's some libraries like wgpu that can fill this gap in practice”
“reverse engineering breaking changes of excessive cleverness”
“it kinda worked, but both terminal and web browser rendered poorly”
“I bring these up as they're easy-to-use and mature.”
“For grpahics, WGPU and Vulkan bindings are good paths.”
“it's a fast and convenient way for my code to just write the pixels into a spot in RAM”
“can even use native libraries like Dawn or WGPU”
“The WGPU implementation of WebGPU has a C API, which also has C++ headers, and a native Rust API.”
“WGPU is hard to ship and also equivalent speed or slower”
“I remember this being a nice API in wgpu”
“I'm dreading the "upgrade" from wgpu 24 to wgpu 29.”
“For the small percent that's left where speed is critical, I've just been using wgpu”
“Write a renderer, e.g. on top of wgpu or bgfx”
“things fall short of just being able to "write once, run anywhere" a renderer”
“You could use wgpu to replicate this demo.”
“wgpu has a lot of constraints and complexity imposed on it by all the backends it has to support”
“it's hard for it to ever be as fast as the native APIs it calls for you”
“anecdotally they have been updating in reasonable sync”
“Current wgpu seems to have a floor around ~100mb that isn't there with other rendering backends”
“wgpu's OpenGL support is kind of broken”
“EGUI and WGPU have great integration”
“The canonical Vulkan wrapper is wgpu.”
“The downside is that it's the lowest common denominator, so it always lags behind what you can do directly in DX or VK.”
“A WebGPU implementation isn't exactly slim either, especially when all is needed is just a very small 3D API wrapper”
“WGPU is very actively maintained.”
“the amount of code that's pulled into the project is massive”
“You can use wgpu or dawn in a native app and use native tools for GPU debugging”
“the difficulty and churn in Vulkan/WGPU has resulted in three abandoned renderers”
“Most of the big ones are things like skia, harfbuzz, wgpu - all totally reasonable IMO.”
“wgpu makes more sense when you like the WebGPU headspace but want to target other backends”
“it can't avoid the pain that comes with different backends”
“Portable code has way too many cases.”
“once you have your first working example, it's smooth sailing from there”
“It is a "lowest common denominator", but good enough for most use-cases.”
“WGPU for cross-platform rendering”
“Tons of native projects using both libraries.”
“I'd still hesitate to even call wgpu-rs an implementation of WebGPU”
“I would look into wgpu too”
“wgpu in Rust is an excellent middle ground, matching the abstraction level of WebGPU”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.