v0.1.15215 Aug 2026·Rendering

GPU image blit: pictures draw on the device, pixel-for-pixel

Images now rasterise on the GPU. A picture uploads to the device as a texture and is drawn with the exact same nearest-neighbour mapping the software rasteriser uses, so an opaque image scaled to its box comes out bit-for-bit identical to the software path - not close, identical. Rounded-corner images (avatars, thumbnails) reuse the same one-pixel edge ramp and match within a level. With rects, rounded rects, borders, gradients, and now images on the GPU, everything a page paints except text and WebGL is hardware-rasterised. The GPU aspect moves 14 to 17; a glyph atlas for text is the next and largest step. The overall holds at 57.

Parity with the reference browser

74overall, as of v0.1.343

Web APIs / DOM surface42

Security architecture66

GPU / graphics acceleration68

DevTools / extensions72

Networking85

Media85

Accessibility85

Real-world site compatibility99

HTML parsing100

CSS parsing + selectors100

Layout: block / flex / grid / tables / writing-modes100

Paint + visual100

JavaScript language100

JavaScript performance (JIT)100

HTML parsing100

What changed 3 changes

Rendering	Images rasterise on the GPU: the source uploads as a texture and the fragment shader samples it with the identical integer nearest-neighbour mapping the software path uses, so an opaque scaled blit is bit-exact - zero differing pixels in the parity test.
Rendering	Rounded-corner images reuse the signed-distance coverage ramp and match software within one level at the very edge, so avatars and rounded thumbnails composite the same either way.
Rendering	The GPU raster path now covers solid rects, rounded rects, border rings, linear and radial gradients, and images - the whole of a page's non-text, non-WebGL painting - leaving a text glyph atlas as the next milestone toward a fully GPU-accelerated pipeline.