How to: Retain the Image URI in an HTML Document

  • 4 minutes to read

This example provides more details on HTML export and describes how to store the original image URI in the exported document.

When RichEditControl loads an HTML document, it imports the document and converts it into a native document model, and then converts the native document to the resulting document's format when it is saved.

The list below describes the two options to images on export to HTML.

  • Embed images into the resulting file as base64-encoded data.

    <img src="data:image/png;base64,,iVBORw0KGgoAAAANSUhEUgAAAQQAAA<!-- base64 data -->" width="260" height="90" alt="" style="border-width:0px;" />
  • Save images as separate files.
    The images are named using the "image" word followed by its sequential number in a file. Images are saved to the folder with a name that combines the file name, an underscore and the "files" word. For example, the first png image in the resulting Test.html file is saved to Test_files\image0.png.

    <img src="test_files/image0.png" alt="" style="border-width:0px;" />

Implement a Custom URI Provider

The HTML exporter uses a URI provider instance to obtain each image's URI string. There are two built-in URI providers - the FileBasedUriProvider which provides image file names, and the DataStringUriProvider that constructs a tag for embedded base64 data. The built-in URI provider service (a service that implements the IUriProviderService interface) is used to obtain a provider instance.

You can implement a custom URI provider to specify a custom location for each image when the document is saved to HTML format. To accomplish this, create an IUriProvider descendant and register it in RichEditControl services.


The SubDocument.GetHtmlText method allows you to specify a custom URI provider as the method's parameter, bypassing the URI provider service and the RichEditControl.ExportOptions.HtmlOptions.EmbedImages option.

Each image in the RichEditControl has the OfficeImage.Uri property that is the original image URI. To save an original image URI to the exported HTML document, our custom UriProvider returns the OfficeImage.Uri value.

using DevExpress.Office.Services;
using DevExpress.Office.Utils;
using System;
    public class CustomUriProvider : IUriProvider
        public string CreateCssUri(string rootUri, string styleText, string relativeUri) {
            return String.Empty;

        public string CreateImageUri(string rootUri, OfficeImage image, string relativeUri) {
            return image.Uri;

Export the Result

The following table shows the different methods used to embed images and export the document to HTML format:

Export Result
RichEditControl.HtmlText property Images are contained in the resulting file as base64-encoded data.
SubDocument.GetHtmlText method The HtmlDocumentExporterOptions parameter allows you to specify embedded or standalone images by setting the HtmlDocumentExporterOptions.EmbedImages property.
RichEditControl.SaveDocument or RichEditControl.SaveDocumentAs methods The DXRichEditHtmlDocumentExporterOptions.EmbedImages property, accessible using the RichEditControl.ExportOptions.HtmlOptions.EmbedImages notation, determines whether images are embedded or saved as separate files. Specify this property in the RichEditControl.BeforeExport event handler.

The code sample below specifies the HtmlDocumentExporterOptions properties and retrieves the document content in HTML format.

private void richEditControl1_ContentChanged(object sender, EventArgs e)

private void ReloadHtml()
    DevExpress.XtraRichEdit.Export.HtmlDocumentExporterOptions exportOptions = new DevExpress.XtraRichEdit.Export.HtmlDocumentExporterOptions();
    exportOptions.EmbedImages = (bool)embedImagesCheck.IsChecked;
    string sText = richEditControl1.Document.GetHtmlText(richEditControl1.Document.Range, new CustomUriProvider(), exportOptions);
    memoEdit1.Text = sText;