Getting started

    A native-XAML HTML editor for WPF apps - one NuGet install, clean XHTML, Word paste that survives, source code if you need it. In production since 2015, ready for .NET 11. About WPF HTML Editor Control →

    The HTML Editor gives your desktop application a visual editing surface for formatted text, images and tables, with HTML available for storage or export. Start by installing the WPF NuGet package, then add the control and load your first document.

    Supported target frameworks

    The package multi-targets the following frameworks, so a single PackageReference works whether you are on classic .NET Framework or modern .NET:

    net10.0-windows, net9.0-windows, net8.0-windows, net7.0-windows, net6.0-windows, net5.0-windows, net48, net472, net45.

    Your host project must be a WPF application (an SDK-style project with UseWPF set to true, or a classic .NET Framework WPF project). NuGet will automatically resolve the right asset folder for the target framework you build against, so there is no per-framework DLL to copy or reference by hand.

    Install via NuGet

    Visual Studio's NuGet Package Manager with the SpiceLogic HTML Editor for WPF package selected from nuget.org, showing its details pane and the Install button used to add it to a WPF project.

    From the Package Manager Console in Visual Studio, run:

    Install-Package SpiceLogic.HtmlEditor.WPF

    Or, from a terminal in your project directory, run:

    dotnet add package SpiceLogic.HtmlEditor.WPF

    Or, if you prefer to edit the project file directly, add this PackageReference inside an ItemGroup in your .csproj:

    <ItemGroup>
    
      <PackageReference Include="SpiceLogic.HtmlEditor.WPF" Version="*" />
    
    </ItemGroup>

    Pin Version to a specific number (for example 3.0.13) for reproducible builds, or leave it floating with * while you are evaluating the trial. The package pulls in every dependency the control needs at design time and at runtime; you do not need to add any other references.

    Open the XAML file for the Window, Page, or UserControl that should host the editor and add the following xmlns declaration to the root element:

    xmlns:editor="clr-namespace:SpiceLogic.HtmlEditor.WPF;assembly=SpiceLogic.HtmlEditor.WPF"
    xmlns:editor="clr-namespace:SpiceLogic.HtmlEditor.WPF;assembly=SpiceLogic.HtmlEditor.WPF"

    The prefix editor can be any identifier you choose; the C# and XAML samples throughout this documentation use editor consistently, so keep it unless you have a reason to rename it.

    Ask your AI to do this

    Connect the SpiceLogic MCP server, then give your coding assistant this prompt.

    I use the SpiceLogic WPF HTML Editor. Help me install the correct NuGet package and host the editor with a starter document. Confirm the exact API names, types and defaults with the SpiceLogic MCP documentation, then show the changes for my project.

    Last updated on Oct 10, 2026

    Put this into practice.

    Clone the C# and VB.NET sample projects from GitHub. Start with Quickstart, then explore the feature samples.

    Prefer a guided look? Book a free live demo with our engineers - live on Zoom or Teams, never a chatbot.