Our website uses cookies to enhance your browsing experience.
Accept
to the top
>
>
Quick start
menu mobile close menu
Analyzing projects
Additional information
toggle menu Contents

Quick start

Aug 26 2026

PVS-Studio Atlas Viewer

Atlas Viewer is an edition of PVS-Studio Atlas that provides a cross-platform desktop utility for viewing and marking results produced by the PVS-Studio static analyzer.

How to install

The distribution files for the utility are available for download on the Download PVS-Studio page.

The table below lists the available distributions and how to install them:

Format

System and package manager

Installation method

.exe

Windows, x64

Run the installer

.dmg

macOS, Apple Silicon

Drag to Applications

.AppImage

Linux, x64

Drag to a directory

.deb

Linux, x64

dpkg, apt

.rpm

Linux, x64

rpm, dnf, yum, zypper

.pacman

Linux, x64

pacman

.tar.xz

Linux, x64

Extract to a directory

Supported report formats

Atlas Viewer only supports importing PVS-Studio reports in the following formats:

  • .json — the current report format;
  • .plog — a previous report format;
  • .pvsmap — a binary report containing warnings, result markup, and (optionally) source code.

Interface

Report

The Report section interface is divided into several functional areas:

  • navigation bar
  • source code pane
  • warning view pane
  • markup panel.

The left panel (Workspace) is s used to work with project files on disk, or with files packaged inside a .pvsmap report. The Workspace usually matches the project directory. To load a project, click Open on the toolbar and specify its path, then select the desired analyzer report from the list of files that appears. When a "raw" analyzer report is saved as .pvsmap, or an existing .pvsmap file is opened, the panel switches from Workspace view to the PVS-Studio Map content browser.

On launch, the last used Workspace or the PVS-Studio Map browser automatically reopens, allowing work to continue without interruption or additional configuration.

The source code can be viewed in the central pane. Clicking an analyzer warning automatically navigates to the corresponding line in the source code file.

The Markup Panel on the right is used for marking up warnings: assigning a new severity level to a warning, selecting one of the available statuses, or leaving a comment.

The warnings issued by the analyzer can be viewed on the bottom pane, with each line representing a separate warning. The warning view pane supports column sorting and multiple filter options.

The warning view pane enables saving a "raw" analyzer report in the .pvsmap format. The file can contain warnings, markup, and, if necessary, source files.

Available options for saving the report:

  • Save with Source Files. The directory specified as SourceTreeRoot will be packaged into a .pvsmap file, along with the source files for any file extensions PVS-Studio supports.
  • Save Only Warnings. Suited to sharing a report with markup but no source files. SourceTreeRoot still needs to be configured, though, so file paths in the report are handled correctly and do not expose paths specific to a particular computer.
  • Save view to CSV. Saves the configured table view as a CSV report for sharing analysis results with users who do not have any PVS-Studio tools installed.

Statistics

The Statistics section provides information about the full contents of the uploaded report and the progress of warning markup.

Its main element is a table that organizes data by warning category. For each category, it displays the number of diagnostic rules and their distribution by status. The section also makes it possible to generate and download the final markup report.

Settings

The following options are available in the Settings section:

  • Settings File: serves a debugging purpose, in case previously saved settings are unexpectedly lost.
  • Username: used to specify a name when marking up warnings and commenting on analysis results.
  • SourceTreeRoot: the path to the project directory; required to resolve correct paths to source code files.
  • Use Workspace as SourceTreeRoot: if analyzer reports are always stored in the project directory, this box can be checked to use Workspace as SourceTreeRoot and access files via a single path. Otherwise, use SourceTreeRoot for the project directory and Workspace for the directory containing the analyzer reports.
  • Theme: dark, light, and system.
  • Language: English.