Avalonia vs WPF

The same XAML instincts, two different reaches.

Trusted by industry leaders and developers worldwide

How they differ

WPF got the model right. Windows is where it stops.

Avalonia exists because WPF’s ideas deserved more platforms. The open questions are where the result is allowed to run, and what happens to the WPF code you already have.

AvaloniaWPF
Your application
AvaloniaXAML and C#
WPFXAML and C#
The model
Avalonia
Bindings, templates, styles, MVVM

The same pattern, with additions like compiled bindings and selector styles.

WPF
Bindings, templates, styles, MVVM

The pattern WPF proved across two decades of desktop software.

What draws a button
Avalonia
The framework, through its compositor

Drawn-controls (like WPF), but designed for cross-platform.

WPF
The framework, through DirectX

Vector-based, resolution-independent rendering; nothing wrapped.

Where it runs
Avalonia
WindowsmacOSiOSAndroidLinuxBrowser

One project, with embedded Linux beyond the desktop.

WPF
Windows

By design.

In one line

True cross-platform.

Stuck on Windows.

Why it matters

A WPF team evaluating Avalonia is weighing the same philosophy with a different reach. Skills transfer becomes the default rather than the risk, and the real decisions are lifecycle, tooling and what to do with the application you’ve already shipped.

Sometimes the answer is staying on WPF.

The model is shared, so what’s left to weigh is reach, tooling and lifecycle.

Choose Avalonia when

The next thing you build shouldn’t inherit the Windows ceiling.

  • You’re starting a product, a module or a UI rebuild you’d already planned
  • macOS, Linux or the browser is anywhere in the product’s future
  • Your team’s WPF fluency is an asset to spend
  • You want compiled bindings, selector styles and theme variants
  • MIT licensing matters, with no per-seat framework licence

WPF is a fair choice when

The product is Windows, and that’s the end of the sentence.

  • Your users, deployment and roadmap are Windows-only by nature
  • The codebase leans on HwndHost, WindowsFormsHost or DirectX interop
  • Your team works through the Visual Studio designer, and needs one that’s out of preview today
  • The product ships well today, and needs a reason to move

Transferable skills

You’re already an Avalonia expert.

If you’ve ever built or maintained a WPF application, then developing with Avalonia will feel incredibly familiar. Most users with existing WPF experience report that they’re productive immediately and that the rich documentation helps them quickly understand the differences.

The mental model, not just the syntax.

The shape of an Avalonia app is the shape of a well-built WPF app. The concepts transfer with the team rather than requiring everyone to relearn.

  • XAML views over view models
  • Commands, DataTemplates, resources and styling
  • View models, services and tests are .NET, not WPF
WPFAvalonia
{Binding Path, Mode=TwoWay}Same
DataTemplateSame
ICommandSame
StaticResource and DynamicResourceSame
Grid, StackPanel and DockPanelSame
<Style TargetType="Button"><Style Selector="Button">
Style.TriggersPseudo-classes (:pointerover, :pressed)
DependencyPropertyStyledProperty
VisibilityIsVisible

A dialect, and it’s documented.

Styles select like CSS, with classes and pseudo-classes, instead of triggers. Bindings can compile, so a typo in a path can fail the build instead of a demo.

  • Strongly typed StyledProperty registrations
  • Pointer-based events
<Style Selector="Border.status">
    <Setter Property="Background" Value="Red" />
</Style>
<Style Selector="Border.status[(vm:MyViewModel.IsActive)]">
    <Setter Property="Background" Value="Green" />
</Style>

Shipping today

The software WPF built, shipped beyond Windows.

Two routes off Windows, both shipping today.

LINQPad

A long-running WPF codebase, on macOS without a rewrite.

Through Avalonia XPF, with one maintainer and one codebase for Windows and macOS in LINQPad 9.

LINQPad, built with Avalonia XPF

LINQPad running natively on macOS, showing a C# query and its results
“As our tools use WPF, Avalonia was an easy choice for us.”

The dotTrace and dotMemory team

Developers compiled Avalonia applications 410M times in the first half of 2026.

5.7M

Projects built on Avalonia

Icons8 Lunacy

From Windows-only WPF to four platforms.

A port the team believes would have taken at least 3x longer on another framework.

Sergey Mikolaitis, Team Lead, Lunacy at Icons8

The Lunacy design application on macOS, showing a vector canvas, a layers panel and an inspector

The decision

Three futures for a WPF codebase.

For years the only advice for a WPF team that needed macOS or Linux was a rewrite, and working products rightly decline rewrites. That’s the constraint that changed.

ILSpy, a WPF application, running on Linux through Avalonia XPF, with decompiled C# in its editorLINQPad 9, a WPF application, launching on macOS through Avalonia XPF; its splash screen reads using Avalonia.XPF

Stay on WPF, on Windows.

Legitimate, and for many products correct. Microsoft’s own platform overview marks WPF actively maintained, and new versions ship yearly with .NET.

Run the application you have, everywhere, with XPF.

XPF is a binary-compatible WPF runtime, so the same application runs on Windows, macOS and desktop Linux. Licensing is per application, perpetual. Autodesk, KLM and Stryker ship on it.

Build what’s next on Avalonia.

For the new product or the next module: the same model your team already thinks in, MIT licensed. Teams that bet a product on it can put the framework’s own engineers behind them with Avalonia Enterprise.

Developer experience

Day-to-day use

Your XAML and C# skills transfer immediately. Avalonia’s IDE extensions already provide the live preview workflow that professional WPF developers rely on, while preserving the fast, precise XAML-first development model they know.

WPF has the Visual Studio designer. Avalonia has Reframe.

With Reframe you pick controls from a toolbox, edit their properties, and every change lands in your project’s own XAML. It’s part of Avalonia Plus and free for everyone while in preview, which is coming soon.

  • A live XAML previewer in Visual Studio, VS Code and Rider
  • Avalonia DevTools inspecting the running app
  • An MCP server so your agents can drive it too
Reframe with a toggle switch selected on the canvas: the toolbox of controls on the left, the document outline below it, and the switch’s alignment, size and layout properties on the right

Two answers, for two kinds of code.

WPF’s commercial ecosystem has two decades of depth. New Avalonia work has native commercial suites, including Actipro’s, and the WPF code you already have keeps the major vendor suites under XPF.

  • 429 controls tested in the public database
  • 90% working, as a snapshot
  • DevExpress
  • Actipro
  • Syncfusion
  • Telerik
  • Infragistics
  • SciChart

One pipeline, every desktop.

A WPF app ships to Windows with MSIX or ClickOnce. An Avalonia app ships self-contained to each desktop, and Parcel produces the installers for every target from one run.

  • Trimmed and compiled ahead of time where startup matters
Parcel packaging Helio, a sample app: Windows, macOS and Linux side by side, each with its architectures and its installer formats ticked

Side by side

A fair comparison.

A balanced perspective on where Avalonia and WPF both offer value.

AvaloniaWPF

Where it runs

Windows
AvaloniaSupported
WPFSupported
macOS
AvaloniaSupported
WPFWith Avalonia XPF
Desktop Linux
AvaloniaSupported
WPFWith Avalonia XPF
iOS and Android
AvaloniaSupported
WPFNot a target
Browser
AvaloniaSupported, via WebAssembly
WPFNot a target
Embedded Linux
AvaloniaSupported, framebuffer or DRM
WPFNot a target

The model

UI definition
AvaloniaXAML
WPFXAML
Draws its own controls
AvaloniaYes
WPFYes
MVVM and commands
AvaloniaThe native pattern
WPFThe native pattern
Data binding
AvaloniaBindings; compiled bindings can fail the build
WPFBindings, resolved at runtime
Styling
AvaloniaSelector-based styles and theme variants
WPFStyles with triggers

The lifecycle

Framework licence
AvaloniaMIT
WPFMIT
Release rhythm
AvaloniaContinuous, with LTS versions
WPFYearly, with each .NET release
Cross-platform path for existing code
AvaloniaAvalonia XPF, binary-compatible
WPFNone from Microsoft
Vendor’s pick for new Windows apps
AvaloniaNot its market
WPFMicrosoft recommends WinUI

The working week

Visual designer
AvaloniaThe Reframe designer (preview coming soon) and a live XAML previewer
WPFThe Visual Studio XAML Designer
Inspecting the running app
AvaloniaAvalonia DevTools, with an MCP server
WPFLive Visual Tree in Visual Studio
Third-party controls
AvaloniaNative suites, plus WPF suites under XPF
WPFTwo decades of commercial depth
Installers
AvaloniaParcel, every target from one run
WPFMSIX and ClickOnce, Windows only

WPF rows were checked against Microsoft’s published pages in August 2026: the Desktop Guide overview, the Windows developer platform comparison, the .NET 10 release notes for WPF and the .NET support policy. When Microsoft’s pages change, so should this table; tell us if we’re behind.

FAQ

The questions
WPF teams ask.

If you’re weighing this up for a real codebase and something here doesn’t cover it, ask us directly.

No, and this page doesn’t argue otherwise. Microsoft’s own platform overview marks WPF actively maintained, new versions ship yearly with .NET, and a Fluent theme for Windows 11 arrived in .NET 9 and grew in .NET 10, with Microsoft’s own note that “Fluent UI style support is still in progress”. What WPF is, in Microsoft’s words, is Windows-only: “Even though .NET is a cross-platform technology, WPF only runs on Windows”. So WPF is healthy. What remains to decide is whether Windows-only is a constraint your product can afford.

If the product is Windows-only by nature, forever, and your team leans on the drag-and-drop XAML designer in Visual Studio, WPF remains a sound choice, and Microsoft would also point you at WinUI for new Windows apps. The calculation changes the moment any other platform enters the roadmap: the same XAML and MVVM investment on Avalonia buys Windows plus five more targets, and you never face the port later because there’s nothing to port from.

No. Avalonia is an independent implementation of the same model: XAML, bindings, templated controls, MVVM, built from scratch to be cross-platform, with deliberate differences like selector-based styling and compiled bindings. The fork exists too, and it’s a different product: Avalonia XPF is a binary-compatible WPF runtime, derived from WPF’s code, for running existing WPF applications on macOS and Linux. Avalonia is where new work goes; XPF is how shipped WPF apps travel.

Different enough to notice, small enough to look up. Styles select like CSS, with classes and pseudo-classes, where WPF uses triggers. Properties register as strongly typed StyledProperty fields rather than DependencyProperty. Events are pointer-based rather than mouse-specific. Bindings can compile, so a bad path can fail the build. The migration guide documents each mapping, and the cheat sheet compresses them to one page.

Keep the model. Lose the ceiling.

Avalonia takes the model to six platforms under an MIT licence, and XPF takes the application you already shipped to macOS and Linux without a rewrite.