Scalable Vector Graphics (SVG) is an XML-based vector image format that is developed and maintained by the World Wide Web Consortium (W3C). This format will play a central role in future versions of TX Text Control.

SVG Image Import

In version 30.0, we introduced support for adding SVG images to documents in TX Text Control. This allowed you to add vector graphics to a document and also export them to PDF documents while maintaining scalable images.

Exporting SVG Images

In an upcoming version of TX Text Control (32.0) we will introduce the export of document pages as SVG images. The GetImage TX Text Control .NET Server for ASP.NET
TXTextControl Namespace
Page Class
GetImage Method
Gets an image of the page's contents.
method will get a new implementation that returns the page as a base64 encoded string in the SVG format.


As with the other implementations, the PageContent TX Text Control .NET Server for ASP.NET
TXTextControl Namespace
TXTextControl Enumerations Enumerations
PageContent Enumeration Enumeration
Defines the contents of a page's image returned from the Page.GetImage method.
parameter defines the content to be returned by the method. For example, you can specify whether to include headers and footers, or the background.

The second parameter specifies the resolution of the embedded bitmap images. Since SVG is a vector graphic, pixel-based images are embedded. Depending on the application, the required resolution can be defined.

Rendering Pages as SVGs

The following ASP.NET Core controller code loads a document into TX Text Control and exports and returns the first page as an SVG image.


In the view, the returned SVG image is rendered in an <img> HTML tag.


The SVG representation is rendered in the browser:

SVG export by TX Text Control


When you zoom into the page, the advantage of SVG is immediately apparent. Vector graphics do not blur when scaled:

SVG export by TX Text Control

Document Viewer and Editor

The Document Editor and Document Viewer use this new technology to render documents, adding significant value to these components. For the Document Viewer, all pages need to be rendered only once for each zoom factor, saving processing power and increasing overall performance.

Stay tuned for more!