Getting Started with WPF HTML editor control

    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 10. About WPF HTML Editor Control →

    The SpiceLogic WPF HTML Editor Control is a drop-in WYSIWYG HTML editor for WPF applications. It gives end users a familiar word-processor-style surface for authoring rich HTML - with an MVVM-friendly API, a customizable vector-graphic toolbar that scales cleanly across all screen sizes, an in-place spell checker, a Microsoft-Word-compatible paste pipeline, image and table editing, two-way data binding for BodyHtml, and synchronized switching between visual, HTML-source, and preview modes - while exposing a strongly-typed .NET API for everything you would want to do programmatically.

    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 NuGet Package Manager UI installing the SpiceLogic WPF HTML Editor Control package into 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.

    Add the XAML namespace import

    Visual Studio XAML editor with IntelliSense showing the SpiceLogic WPF HTML Editor namespace import being added to a Window declaration.

    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

    wpf-page-139-tail-closed-v1

    Ask your AI to do this

    Let your assistant do this for you. With the SpiceLogic MCP server connected, paste this into Claude Code, Cursor, or VS Code Copilot in agent mode.

    Using the SpiceLogic WPF HTML Editor, set up SpiceLogic.HtmlEditor.WPF from scratch in my WPF app: install the NuGet package, add the editor xmlns declaration to MainWindow.xaml, drop in a WpfHtmlEditor named ArticleEditor, and two-way bind its BodyHtml property to a view-model property named ArticleHtml so authored content round-trips through my MVVM layer. Target net8.0-windows since that is what my project already builds against. Check the SpiceLogic MCP tools for the exact package name, xmlns string, and BodyHtml binding details before writing any XAML.

    Last updated on May 14, 2026

    Put this into practice.

    WPF HTML Editor Control ships with free C# and VB.NET sample projects and a 14-day evaluation.

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