# printInBackground: print quality

**URL:** <https://pdfjs.community/t/printinbackground-print-quality/530>\
**Category:** Technical Support\
**Created:** [February 22, 2021, 9:08am UTC](https://pdfjs.community/t/printinbackground-print-quality/530 "2021-02-22T09:08:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![torloneg](https://avatars.discourse-cdn.com/v4/letter/t/7bcc69/32.png) [@torloneg](https://pdfjs.community/u/torloneg)\
**Post date:** [February 22, 2021, 9:08am UTC](https://pdfjs.community/t/printinbackground-print-quality/530/1 "2021-02-22T09:08:25Z")

</div>

**PDF.js Express Version**

| UI version | “7.2.0” |
| --- | --- |
| Core version | “7.2.2” |
| Build | “MS8xMi8yMDIxfDcxODAxYzM3NA==” |
| WebViewer Server | false |
| Full API | false |

**Detailed description of issue**  
Hi  
i am using the print function **instance.printInBackground** but in the browser preview this always has a low quality. I entered the call **instance.setPrintQuality(10);** both before instance.printInBackground and inside

WebViewer (…)  
.then (function (instance) {  
instance.setPrintQuality (2);  
});

but without success.

Strangely, if I open the print panel, select the HIGH quality, I make the preview then also in my function it is kept high.  
It appears that the printInBackground function takes the quality from the panel

**Expected behaviour**  
high quality print

**Does your issue happen with every document, or just one?**  
every document

**Code snippet**  
instance.setPrintQuality(10);  
instance.printInBackground({  
pagesToPrint: arrayPages,  
includeComments:false,  
includeAnnotations: false,  
onProgress: function(pageNumber, img) {},  
});

---

<div class="post-metadata">

**Author:** ![Logan](https://yyz1.discourse-cdn.com/flex031/user_avatar/pdfjs.community/logan/32/13_2.png) [@Logan](https://pdfjs.community/u/Logan)\
**Post date:** [February 22, 2021, 10:58pm UTC](https://pdfjs.community/t/printinbackground-print-quality/530/2 "2021-02-22T22:58:07Z")

</div>

Hey there!

This is a known issue and will be fixed in 7.3 which will be released very soon.

Keep an eye on #announcements for an announcement.

Thanks!  
Logan