Packages

This section gives package-by-package coverage for every shippable library NuGet in the repository.

Packaged tools such as Svg.Skia.Converter and svgc stay documented under Samples and Tools.

Runtime packages

Package Start here when Guide
Svg.Skia You want the main SkiaSharp runtime renderer, export helpers, hit testing, or Android VectorDrawable support. Svg.Skia
Svg.Model You need the intermediate drawable and picture model for inspection, mutation, or custom pipelines. Svg.Model
Svg.Custom You want the underlying SVG DOM and parser that the renderer consumes. Svg.Custom
ShimSkiaSharp You need a cloneable command-model equivalent of key SkiaSharp drawing primitives. ShimSkiaSharp

UI packages

Package Start here when Guide
Svg.Controls.Skia.Uno You want Uno Platform SVG controls backed by Svg.Skia and the live Skia canvas. Svg.Controls.Skia.Uno
Svg.Controls.Skia.Avalonia You want the richest Avalonia SVG integration, backed by Svg.Skia and real SkiaSharp.SKPicture output. Svg.Controls.Skia.Avalonia
Svg.Controls.Avalonia You want the same high-level Avalonia SVG concepts but rendered through the Avalonia drawing stack. Svg.Controls.Avalonia
Skia.Controls.Avalonia You want reusable Avalonia controls and IImage wrappers for raw SkiaSharp content, with or without SVG. Skia.Controls.Avalonia

Editor packages

Package Start here when Guide
Svg.Editor.Skia.Avalonia You want the full interactive editor workspace and Skia-backed canvas extracted from AvalonDraw. Svg.Editor.Skia.Avalonia
Svg.Editor.Avalonia You want reusable side panels, standalone editor views, and dialog abstractions without the default workspace. Svg.Editor.Avalonia
Svg.Editor.Skia You want selection math, path editing, align/distribute helpers, and editor overlay rendering for your own surface. Svg.Editor.Skia
Svg.Editor.Svg You want SVG document mutation services, property models, and resource-browser data structures. Svg.Editor.Svg
Svg.Editor.Core You want host-agnostic editor session, settings, outline nodes, artboards, clipboard, and history state. Svg.Editor.Core

Generated-code packages

Package Start here when Guide
Svg.CodeGen.Skia You want to turn the intermediate picture model into checked-in or pipeline-generated C# code. Svg.CodeGen.Skia
Svg.SourceGenerator.Skia You want .svg assets turned into generated Picture classes during the build. Svg.SourceGenerator.Skia

Choosing quickly

  • Choose Svg.Skia for direct runtime rendering and export.
  • Choose Svg.Controls.Skia.Uno for Uno Platform usage on the Skia-backed path.
  • Choose Svg.Controls.Skia.Avalonia for interactive Avalonia usage on the Skia-backed path.
  • Choose Svg.Editor.Skia.Avalonia when you want a reusable SVG editor instead of only a viewer/control package.
  • Choose Svg.Editor.Avalonia, Svg.Editor.Skia, Svg.Editor.Svg, and Svg.Editor.Core when you need only parts of that editor stack.
  • Choose Svg.Controls.Avalonia for Avalonia drawing-context integration without the SKSvg runtime surface.
  • Choose Svg.Model and ShimSkiaSharp when the main task is inspection, transformation, or code generation rather than direct display.
  • Choose Svg.CodeGen.Skia or Svg.SourceGenerator.Skia when startup cost should move from runtime to build time.