SkiaSharp 4.0, now stable and co-maintained by Uno Platform and Microsoft, ships as version 4.148.0 on NuGet, syncing the underlying Skia engine to milestone m148. It brings a cleaner API with legacy APIs retired, up to 24% faster GPU rendering (up to 30% for Uno Platform apps), 6x faster Perlin-noise shaders on CPU, variable font support, color font palettes, animated WebP encoding, and fixes for use-after-free crashes via proper reference counting. Going forward, releases follow a predictable cadence with Stable and Preview channels tracking Chrome's Skia milestones.
Table of contents
Why SkiaSharp MattersStability & Co-MaintenanceExplore What's PossibleWhat's in SkiaSharp 4.0Try It YourselfQuestions this post answers
What's new in SkiaSharp 4.0 compared to previous versions?
SkiaSharp 4.148.0, the first stable v4 release, updates the native Skia engine to milestone m148, retires legacy APIs for a cleaner surface, fixes use-after-free crashes through proper native reference counting, and adds variable font support, color font palettes, and animated WebP encoding. GPU-accelerated rendering is up to 24% faster, and Perlin-noise shaders run about 6x faster on CPU. Developers planning a SkiaSharp upgrade can track rendering and API changes like these on daily.dev.
How much faster is rendering in SkiaSharp 4.0 on the GPU backend?
Rendering that relies on shadows and layered surfaces, such as elevated cards, is up to 24% faster on SkiaSharp 4.0's GPU-accelerated backend compared to the previous stable release. A dashboard of shadowed cards went from 65 to 80 FPS, and a scrolling activity feed improved from 47 to 58 FPS; Uno Platform apps saw up to 30% improvement in early testing. Teams weighing a rendering engine upgrade can follow real-world performance benchmarks like this on daily.dev.
What release cadence does SkiaSharp follow after version 4.0?
SkiaSharp now ships on a predictable cadence with two channels tied to upstream Skia milestones: a Stable channel matching Skia milestones in Chrome's Stable and Extended Stable channels, and a Preview channel matching the milestone in Chrome's Beta channel. This replaces unpredictable prior release timing for teams maintaining production applications. Developers planning dependency upgrades can track release cadence changes like this on daily.dev.
101.5K Impressions1 Comment