Skip to main content Skip to complementary content

Image quality

You can change the image quality of Qlik Sense and QlikView objects by adjusting their dots per inch (DPI) in your published reports. This means you could create a PowerPoint report with high-quality images that will look good on a large screen during a presentation. After the presentation, you could share a second version with lower-quality images (and a smaller file size) via email.

Changes in image quality take effect after you distribute your report to the NewsStand, hub, folder or other destination. In the NewsStand, the image quality of a report is displayed in a column on the right. Published reports export all images as PNG, regardless of source.

There are some limitations:

  • QlikView objects cannot be re-sized or given a DPI value before exporting to Qlik NPrinting. Instead, Qlik NPrinting uses an up-scaling algorithm to get a more defined image. This is not an issue with Qlik Sense objects.

  • On-Demand reports will always be set to Normal (96 DPI).
  • If you publish one report with two different image quality levels to a folder, the newer file will overwrite the older one. This can be avoided by applying a Friendly name when adding the report to a task. See: Dynamic naming of reports.
  • The following report output format combinations cannot have their quality changed:

    • Excel to TIFF
    • PixelPerfect to GIF
    • PixelPerfect to JPEG
    • PixelPerfect to PNG
    • PixelPerfect to TIFF

Set image quality

Do the following:

  1. In the main menu bar, click Tasks, and then select Publish task.
  2. Create a new publish task, or click an existing publish task to edit it.
  3. Click Reports.
  4. Use the Quality dropdown menu to select one of the following:
    1. Normal (96 DPI)
    2. High (192 DPI)
    3. Very High (384 DPI)
  5. Click Save.

Once you publish your report, you will be able to see the difference in image quality.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!