About This Release

This is the Qt Safe Renderer (QSR) 2.2.0 release. It is published in August 2026.

Qt Safe Renderer Developer Guide

Start using the release by reading the QSR developer guide. It provides instructions on installing, building, and integrating QSR into your safety-critical product.

There are the following alternatives to open the developer guide:

• Use a web browser to open the latest online documentation version: https://doc.qt.io/QtSafeRenderer/
• Install QSR and use one of the following ways to open the developer guide:
  • Use a web browser to open <QSR INSTALL DIR>/Docs/QtSafeRenderer-2.2.0/QtSafeRenderer/qtsaferenderer-index.html.
  • Open the help in the Qt Creator tool either via the mode selector or menu:
    • In the menu, select Help > Contents.
    • In the mode selector, select the Help mode button and activate the contents view.

    Qt Safe Renderer developer guide can be found under the listed Qt help topics. Contents view and the order of the help topics depend on your Qt installation.

Safety Manual

The Qt Safe Renderer Safety Manual is available via Qt's customer support. For more information, see Qt Support.

Supported Environment

Qt Safe Renderer 2.2.0 can be used with Qt 6.8.x. However, this release includes pre-built Qt Safe Renderer binaries for Qt 6.8.7. Binaries are provided for the Qt Safe Renderer Runtime component, tools, and plugins as follows:

• For QSR Runtime component, binaries are provided for QNX and host environments (Linux, macOS, and Windows).
• For QSR tools, binaries are provided for host environment (Linux, macOS, and Windows).
• For QSR plugins, binaries are provided for QNX and host environments (Linux, macOS, and Windows).

Also, the Qt Safe Renderer 2.2.0 system image, toolchain, and system root are provided for NXP i.MX 8QuadMax.

Examples still need to be built as instructed. For more information, see the Building Qt Safe Renderer topic in the developer guide.

Qt Safe Renderer 2.2.0 supports Qt Design Studio 4.2 and later.

The Qt Safe Renderer 2.2.0 functionality has been tested with the following reference hardware configurations:

• NXP i.MX 8QuadMax for Boot to Qt 6.8 + Yocto 5.0 Linux (scarthgap)
• Qualcomm Snapdragon SA8295P + QNX OS 7.1
• Qualcomm Snapdragon SA6155P + INTEGRITY 19.0.14
• Infineon Traveo T2G CYT3DL (4M LITE KIT)

However, Qt Safe Renderer 2.2.0 can be used with a wide range of target devices and operating systems as it is a safety-element out of context (SEooC). For more information, see the QSR Safety manual and the QSR architecture specification.

The requirements for the target devices and operating systems are listed in the developer guide, see https://doc.qt.io/QtSafeRenderer/qtsr-supported-environment.html#reference-target-devices.

For more information about the supported environment, see https://doc.qt.io/QtSafeRenderer/qtsr-supported-environment.html.

System Dependencies

Qt Safe Renderer system dependencies are described in the Qt Safe Renderer Architecture specification. See chapter Interfaces and Interaction with System.

Feedback of the Release

All feedback of this release is welcome. You can report bugs and change requests as instructed in Bugs and Change Requests.

Previous Qt Safe Renderer Releases

Previous Qt Safe Renderer releases can be installed via Qt Online Installer. In the Select Component page, check the Archive category and select Filter. The archived Qt Safe Renderer releases are listed under Qt Safe Renderer.

Changes to the Previous Release

New Features

QSR 2.2 provides following new features:

• Safety-critical items are supported in Qt Quick Ultralite applications.
  • See Building for Qt Quick Ultralite for build instructions.
  • Qt Safe Monitor: Qt Quick Ultralite Example on Bare-Metal Traveo II demonstrates how to integrate Qt Safe Renderer Monitor to a Qt Quick Ultralite application targeting bare-metal Infineon Traveo II environment.
  • For more information, see Getting Started with Qt Safe Renderer and Qt Quick Ultralite.
• Alpha Pixel bypass feature is available for Snapdragon Generation 4 hardware (Qualcomm Snapdragon 8295). For more information, see Alpha Pixel Bypass for Transparent Backgrounds.
• Pre-built Qt Safe Renderer binaries built with Qt 6.8.7. Binaries are provided for the Qt Safe Renderer Runtime component, tools, and plugins.

API Changes in Qt Safe Renderer Runtime Component

The release note appendix Qt_Safe_Renderer_Release_Note_Appendix_Runtime_API_Changes_2_2_0.pdf lists the API changes done to the Qt Safe Renderer Runtime Component after Qt Safe Renderer 2.1.

Bug Fixes

All bug fixes included in the release can be filtered via Qt's internal Qt Bug Tracker (https://jira.qtgroup.qt.io/). In Qt Bug Tracker, select Filters > Search for work items and type the following search string to the JQL search field:

project = "Qt Safe Renderer" AND type = Bug AND fixVersion ~ "QSR 2.2*" AND status = Closed and resolution in (Done,Fixed)

Release Content

The following chapters describe the installed Qt Safe Renderer content at a general level. Pre-built binaries, sources, examples, documentation, and tools are found under the QSR installation folder <QSR INSTALL DIR>.

Qt Safe Renderer Pre-built Binaries

The pre-built Qt Safe Renderer binaries are installed under <INSTALL DIR>/<Qt version>/<compiler>. Binaries are built with Qt 6.8.7 for Qt Safe Renderer tools and plugins.

Source Code

The QSR source code is found under the <INSTALL DIR>/Src folder as follows:

• QSR Tooling source code is installed under <INSTALL DIR>/Src/QtSafeRenderer-2.2.0
  • 3rd party software (that is, easing implementation)
  • Qt Quick plug-in
  • Safe event sender plug-in
  • Safe RCC tool
  • Safe Config tool
  • QSR Layout generator tool
  • Manual tests
  • Automated unit tests and integration tests
• QSR Runtime source code is installed under <INSTALL DIR>/Src/QtSafeRenderer-runtime-2.2.0
  • QSR runtime component. For more information, see the QSR Runtime API reference in the Qt Safe Renderer module documentation.
  • Adaptations. For more information, see Supported Adaptations.
  • calcCRC library
  • Event Sender
  • Automated unit tests and integration tests

Tools

The QSR tools are found under the <INSTALL DIR>/Tools/QSR-2.2.0 folder:

• qtsafelayouttool binary
• qtsafercctool binary
• qtsafeconfigtool binary

For more information about the QSR Tools, see Safety Tools.

Examples

The QSR example applications are found under the <INSTALL DIR>/Examples folder. For building the examples, see the instructions in the developer guide: Qt Safe Renderer Examples.

Documentation

The QSR documentation is found under the <INSTALL DIR>/Docs/QtSafeRenderer-2.2.0 folder:

• Architecture design specification
• Certification document
• Release note and its appendices
• Developer guide (open qtsaferenderer-index.html with your browser)
• SW unit design specification
• Verification report with appendices
• Verification specification with appendices

System Requirements

Linux, Windows, and macOS are supported as development platforms.

The target device must support hardware layers because Qt Safe Renderer is the overlay on top of the non-safe UI.

The target device must support display output CRC checking if you are using an external monitor component that makes it possible to run Qt Safe Renderer on the QM hardware.

The operating system of the embedded platform must fulfill the following requirements:

• Provides a way to set up the graphics overlays.
• Supports multiple processes and memory protection between the processes. For example, QNX has a microkernel architecture that prevents processes from interfering with each other. On hypervisor architectures, the non-safe main UI can run on the virtual operating system while the safety-critical content is rendered in the real-time operating system.
• All the tools that are part of producing the Qt Safe Renderer runtime binary must be certified according to the application target safety integrity level (SIL or ASIL) based on the appropriate functional safety standard.

Certification Information

The Qt Safe Renderer (QSR) 2.2.0 release is certified with the SEBS-A.113256/17 V3.0 certificate by TÜV NORD. The QSR 2.2.0 release meets the requirements listed in the following standards:

• IEC 61508:2010; Part 3; Section 7.4.4; Qualified up to SIL 3
• ISO 26262:2018; Part 8; Section 11; Part 6; Qualified up to ASIL D
• EN 50128:2011; 6.7.4; Qualified up to SIL 4
• ISO 25119-3 AMD 1:2020 Qualified up to AgPL e

QSR 2.2.0 can also be used as a software supporting tool in a software safety lifecycle according to IEC 62304:2015; Section C.7.

The certification document is part of the installed QSR content as described in Documentation.

The information on which parts of the standard are not applicable for Qt Safe Renderer can be found from the release note appendix "Statement of Compliance".

The certification report will be provided for Qt Safe Renderer customers by a request.

Known Issues

There are no known safety-critical issues.

In Qt's internal Qt Bug Tracker (https://jira.qtgroup.qt.io/jira), you can filter bugs that have been reported for the QSR 2.2.0 release but the QSR development team has postponed the fix in some later QSR release. In Qt Bug Tracker, select Filters > Search for work items and type the following search string to the JQL search field:

project = QSR AND issuetype = Bug AND affectedVersion ~ "QSR 2.2*" and resolution = Unresolved

QSR 2.2 FAQs can be found in the developer guide: Qt Safe Renderer FAQ.

Backward Compatibility

QML Files with Safety-Critical Elements

Backwards compatibility between the Qt Safe Renderer versions is not guaranteed.

Bitmaps

The bitmap format was changed from a 32-bit ARGB format to a premultiplied 32-bit ARGB format in QSR 1.2. Thus, the bitmaps from previous Qt Safe Renderer releases are incompatible with Qt Safe Renderer releases from QSR 2.0 onward. The bitmaps from QSR 1.2 are compatible with the QSR releases from QSR 2.0 onward.

Appendices

Qt_Safe_Renderer_Release_Note_Appendix_Statement_of_Compliance_2_2_0.pdf defines the QSR 2.2 compliance with the related standards.

Qt_Safe_Renderer_Release_Note_Appendix_Runtime_API_Changes_2_2_0.pdf lists the QSR 2.2 Runtime component API changes done after QSR 2.1 release.

Sign-off

Qt_Safe_Renderer_Note_2_2_0.pdf is available in the installed Qt Safe Renderer 2.2 documentation. It is electronically signed off by persons responsible for the release.