What's New

What's New 2026 Q2

Telerik Reporting Entity Framework Core Data Source

Developers working with Entity Framework Core no longer need workarounds to connect their domain data to Telerik Reporting. A new dedicated EF Core Data Source component lets teams expose any .NET DbContextdirectly to report authors in the Standalone and Web Report Designers, complete with a guided wizard, live data preview, parameterized queries, and Shared Data Source reuse.

See Telerik Reporting Entity Framework Core Data Source Documentation

Telerik Reporting Specify Table of Contents Levels

The Table of Contents in Telerik Reporting now gives report authors more control over how content appears in the TOC by allowing explicit TOC levels for supported sections, groups, and items. This makes it easier to promote or demote entries, align TOC depth with the logical structure of a document, and keep navigation consistent across differently structured reports and Report Books, while still preserving the existing TOC styling and automatic behavior when no explicit level is set. The result — report authors gain the flexibility to shape TOC structure around business semantics rather than working around the constraints of the report hierarchy.

See the Telerik Reporting Specify Table of Contents Levels Documentation

Telerik Reporting Native Blazor Report Viewer

Until now, Blazor developers who needed lifecycle event hooks — such as reacting to a drill-through action, intercepting print, or customizing an outgoing email — had to compromise their architecture and fall back to the jQuery wrapper viewer. The Native Blazor Report Viewer now exposes the complete set of applicable events, from page render and error to interactive actions, tooltips, and send-email flows, all with strongly-typed EventArgsand support for cancellation and field mutation. The result — teams using the Native Blazor component can build fully reactive, event-driven reporting experiences without ever touching a jQuery dependency. 

See the Telerik Reporting Native Blazor Report Viewer Documentation

Telerik Reporting Out-of-the-Box Firebird Support for .NET

Connecting a SqlDataSource to a Firebird database previously required knowing undocumented Telerik Reporting internals and manually registering the ADO.NET factory at application startup. Firebird is now pre-registered in the Reporting engine alongside PostgreSQL and SQLite — install the FirebirdSql.Data.FirebirdClient NuGet package, configure a connection string, and the provider appears automatically in the SqlDataSource wizard and at runtime. 

Telerik Reporting Rendering Engine Performance Improvements

The Telerik Reporting rendering engine receives targeted performance optimizations for PDF and HTML output, delivering significantly faster cold-start rendering times and lower memory consumption across typical report workloads. Improvements include smarter initialization, reduced intermediate allocations, and more efficient memory management — with no changes required to existing report definitions or application code.

Telerik Reporting .NET 11 Preview Compatibility

Telerik Reporting MaxiCode Barcode Support

Telerik Reporting CSP-Compliant HTML5 Report Viewer

Embedding a report viewer in a CSP-protected application previously forced developers to weaken their defenses with unsafe-inline and unsafe-eval — effectively nullifying the XSS protection CSP is designed to provide. The HTML5 Report Viewer is being refactored for compatibility with strict Content Security Policy configurations, eliminating the need for unsafe-inline and unsafe-eval in the script-src directive for the viewer component itself. This allows developers to embed Telerik Reporting in tightly controlled web applications — including those subject to PCI-DSS, SOC 2, or internal enterprise compliance policies — without relaxing the CSP protections that guard against cross-site scripting attacks. Note that the rendered report content still requires accommodations for inline styles produced by the report.

Integrated AI Chat in Telerik and Kendo UI Documentation

Telerik and Kendo UI documentation pages now support an integrated AI Chat, allowing you to easily ask questions and receive instant, context-aware answers directly within the page. The assistant helps you quickly locate relevant information, understand features, and explore related topics without interrupting your workflow. By combining search and conversational guidance, it streamlines navigation and improves productivity when working with components and APIs.

What's New 2026 Q1

Inline Image Support in HtmlTextBox

The HtmlTextBox now supports inline images via the <img> tag, allowing report authors to embed static or data-driven images directly within HTML-formatted content. This improves layout flexibility, reduces the need for separate image elements, and ensures consistent rendering across supported export formats. The result - report authors can create richer, more compact report layouts with fewer visual elements to manage.

Repeating Table Group Headers

Table groups now support repeat-on-every-page behavior in Report Server–hosted reports. This gives report authors finer control over long tables, improving readability and helping meet common reporting and compliance requirements.

Unicode Bidirectional (BiDi) Text Layout Support

With this release Telerik Reporting includes Unicode Bidirectional (BiDi) text layout support in its Skia-based rendering engine. This ensures correct visual ordering of mixed RTL and LTR text, improving readability and accessibility for multilingual reports across major rendering formats and platforms. Multilingual reports now display correctly and consistently for global audiences. 

Improved Serialization for .NET

Resource serialization for .NET has been improved when serving reports to report viewers and designer tools. The new implementation replaces Newtonsoft.Json with the built-in System.Text.Json, resulting in better performance and a simplified deployment experience with fewer external dependencies. Developers benefit from faster report delivery and easier setup with fewer moving parts. 

The only remaining usage of Newtonsoft.Json is in the WebReportDesigner backend REST service, where it is required for specific resource serialization scenarios. This dependency is not used for the WebReportDesigner client–server communication, which now fully relies on System.Text.Json.